You run DCDiag and it returns a failure that names can not be resolved.
testing server: default-first-site-name\mydomain starting test: connectivity the host 7397e120-1c8d-4f2d-b8cb-d829d16d949a._msdcs.mydomain.local could not be resolved to an ip address. check the dns server, dhcp, server name, etc although the guid dns name (7397e120-1c8d-4f2d-b8cb-d829d16d949a._msdcs.mydomain.local) couldn't be resolved, the server name (myhost.mydomain.local) resolved to the ip address (192.168.1.5) and was pingable. check that the ip address is registered correctly with the dns server. ......................... myhost failed test connectivity
This is mainly due to bad or non existent DNS records on your AD server. Here are the steps to run through to make sure your Active Directory DNS has the correct records needed to allow Active Directory to function correctly in a Windows 2003 or Windows 2008 environment.
Steps to resolve:
- Verify SRV Records
- SRV Records missing after Promo
- Verify All DC’s are point to one as “master”, Second to them self or another is better.
- Verify DHCP Client Service is running (needed for Dynamic DNS updates)
- Run at cmd prompt -> net stop netlogon && net start netlogon
- Run at CMD prompt -> netdiag /fix
- Re run at CMD prompt -> DCDiag.exe
Testing server: Default-First-Site-Name\MYDOMAIN
Starting test: Connectivity
*** Warning: could not confirm the identity of this server in
the directory versus the names returned by DNS servers.
If there are problems accessing this directory server then
you may need to check that this server is correctly registered
……………………. MYHOST passed test Connectivity