Contents
How to troubleshoot Samba AD DC troubleshooting?
1. During samba-tool domain join, specify the –dns-backend=NONE command line option. 2. Perform a samba-tool drs replicate of the DC=ForestDnsZones and DC=DomainDnsZones partitions with the options –local –full-sync .
How to join a samba DC to an existing Active Directory?
To join the domain samdom.example.com as a domain controller (DC) that additionally acts as a DNS server using the Samba internal DNS: There are three authentication methods you can use, Username & Password or two kerberos methods (the kerberos methods depend on running kinit as an admin user). Or: Or:
Why does Samba not find DC by hostname?
So now the client finds the DC by hostname just fine, and it even finds the hostname and IP, but it can’t find the DC software running, even though Samba says it’s there. This sounds like a DNS problem. I’m assuming the hosts file you showed is on the server?
When trying to open a network public Samba share, I kept getting this error: Network Error: Windows cannot access \\\\hostname. Check the spelling of the name. Otherwise there might be a problem with your network. To try and identity and resolve network problems, click Diagnose. Running net use in Windows Command Prompt brought up another error.
Can a samba domain controller support network browsing?
Samba Domain Controller do not support network browsing, and thus no nmbd processes are listed. All samba, smbd, and winbindd processes must be child processes of one samba process. If you do not see a process structure as displayed:
Why does Samba not support legacy DNS zones?
If the domain has been migrated from Windows 2000 or 2003 (including R2 variants and possibly 2008 non-R2), the DNS zones may not have been migrated correctly. Legacy DNS zone locations are not supported in Samba, which only supports fully replicated AD DNS zones (ForestDnsZones, DomainDnsZones).
Can you run ldapcmp on Samba AD DC?
Optionally, you can now run samba-tool ldapcmp in order to verify that the databases are consistent (noting attributes msDs-masteredBy, msDS-NC-Replica-Locations, msDS-hasMasterNCs have been changed). For some more detail in regards to issues with domains migrated from Windows 2003 R2 or earlier: