search for: oidldapd

...rver role: ROLE_DOMAIN_MEMBER Press enter to see a dump of your service definitions So Samba in principle is working, I can access my shares, read files, etc. but the AD servers are still seeing my Linux servers as domain controllers. We tried blocking external incoming ports 389 and 636 (local oidldapd service), so the AD server doesn't think it's a domain controller, but when I authenticate and connect, it's still showing as a domain controller. Has anyone else encountered this and found a resolution to the domain controller issue? Thanks in advance, Albert.