Home / server / Questions / 370314
Accepted
paradroid
Asked: 2012-03-16 18:35:42 +0800 CST

Domain Controller DCdiag error - A Global Catalog Server could not be located

  • 772

I've set up a replica DC in a remote location. It's connected to the main site through a VPN connection. DCdiag passes on the primary DC, but I get the following error on the replica DC:

Running enterprise tests on : mydomain.co.uk

      Starting test: LocatorCheck

         Warning: DcGetDcName(GC_SERVER_REQUIRED) call failed, error 1355

         A Global Catalog Server could not be located - All GC's are down.

         Warning: DcGetDcName(PDC_REQUIRED) call failed, error 1355

         A Primary Domain Controller could not be located.

         The server holding the PDC role is down.

         ......................... mydomain.co.uk failed test LocatorCheck

Is it giving this error just because it is not the global catalogue server, or is there some connectivity issue where it does not think there is one at all, as the error seems to imply? If so, it seems odd, as all other tests were passed.

What do I do about this?

domain-controller active-directory windows-server-2008-r2

3 Answers

  1. Best Answer

    Check the DNS settings on your new domain controller, in 2003 and later, you should always point to 127.0.0.1, and then secondary to another domain controller or any other DNS server with that internal DNS zone available. You should then add a "forwarder" to the DNS service itself under the DNS MMC snap-in.

    • 4

  2. I have same problem on windows 2008 enterprise 32 bit server, had tried whole day, and finally i see the service one by one and started services which i think is vital and finally i restarted the Active directory services on server and my problem was solved and DNS again started working perfectly.

    • 0

  3. I had this problem after I had our physical server automatically restart for updates without shutting down our hyper-v VMs. After a night of troubleshooting, I found that going into services and restarting "Active Directory Domain Services", everything went back to normal and AD was able to sync with DNS. Note that numerous restarts did not fix this until I manually restarted the service.

    • 0