Newly installed domain controller cannot contact global catalog server
Posted on 2008-10-03
I just installed a second DC in a subdomain of an existing Server 2008 domain. However, I'm getting errors for AD Domain Services and DNS Server on the new domain, and I can't seem to do things I want to do (like create a new DNS zone and delegation). I'm getting an error saying that AD DS (on the new server) is not able to contact the global catalog server. I've tried the following troubleshooting steps (from MS help):
1. Checked network connectivity of DC reporting the error: It's OK, and both DCs can ping each other by IP address or hostname. (One thing I noted, though, is that when pinging by hostname, the address that is returned is an IPv6 address instead of the IPv4 address that I have configured for the server. Could that be related to the problem?)
2. Tested connectivity from new DC to global catalog server using this command: nltest /server:newServer /dsgetdc:mydomain.com. This returns an "ERROR NO SUCH DOMAIN" error.
3. Ensured that my main DC is in fact configured as a global catalog server and that the NTDS service is running. This checked out OK.
4. Tried to test connectivity from the new server to the GC server by right-clicking the server name in Active Directory Users and Computers, clicking Change Domain Controller, and then typing in the GC server's IP address and port (e.g., 192.168.0.211:3268). This failed, as the server status is listed as Unavailable.
I'm at my wit's end, and this is time critical, so any help would be greatly appreciated!