Thanks for the reply.
I have a local account on the workstation, “iamroot”.
Nethserver is master.domain.lan with IP 10.1.0.1
But when I installed the AD, it seemed to generate ad.domain.lan automatically, on 10.1.0.2. The active directory module is some sort of container on master running it’s own name and IP right?
All DNS is handled by NethServer as DHCP and gateway.
When I create an account in Nethserver, it generates with the “@domain.lan” suffix that nethserver is on, but the realm seems to be ad.domain.lan.
My issue seems to be that you log in with firstname.lastname@example.org but the authentication realm uses email@example.com in the backend?
Perhaps this helps you at all:
Of course, I am stripping out the real domain name and using “domain” instead in my forum posts here for anonymity.
NetBIOS domain name: DOMAINLAN
LDAP server: 10.1.0.2
LDAP server name: nsdc-master.ad.domain.lan
Bind Path: dc=AD,dc=DOMAIN,dc=LAN
LDAP port: 389
KDC server: 10.1.0.2
Join is OK