Troubleshooting domain joins of Windows clients


A Windows client does not join the domain correctly.


Problems during domain joining can have different causes:
####1. Incorrect DNS configuration / DNS entries
The Windows client should use a UCS domain controller as its DNS server. No servers should be defined in the DNS SRV records which no longer exist or which are currently shut down. This can be checked as follows:

host -al $(dnsdomainname) | grep " SRV "

####2.Incorrect time setting on Windows client

The Windows client should display the same time as is set on the UCS domain controllers. Attention should also be paid to the time zone.

####3.The following message may appear following a successful domain join:

Changing the Primary Domain DNS name of this computer to "" failed. The name will  remain "domain.local".
The error was: The specified server cannot perform the required operation.

In this case, the domain has been joined successfully but the Windows client could not register its IP address on its host name in the DNS. This can have different reasons. If the system is running Windows 7 and exclusively uses Ipv6, should be consulted. As standard, Windows clients attempt to register their IP address with the DNS server after every system start. This procedure can also be triggered by a Windows administrator manually in the Windows command line with:

ipconfig /registerdns

Alternatively, the DNS entries can be edited via the DNS module of the Univention Management Console.
Should these points not be successful, the debug level of the Samba service can be increased and the log output checked for further errors:

ucr set samba/debug/level=4
/etc/init.d/samba4 restart
less /var/log/samba/log.samba