DCdialog error - AD does not show up after PDC was shut down

al4629740
al4629740 used Ask the Experts™
on
I have 2012 server that replaced a 2003 server on my domain.  The FSMO roles have been transferred and DC promoted.  When the old 2003 PDC is off the 2012 server has issues with AD.  I can't access it when the old server is shutdown.  However when I run dcdialog, I get errors below.  how do I fix the errors?

 Warning: DcGetDcName(GC_SERVER_REQUIRED) call failed, error 1355
 A Global Catalog Server could not be located - All GC's are down.
 Warning: DcGetDcName(TIME_SERVER) call failed, error 1355
 A Time Server could not be located.
 The server holding the PDC role is down.
 Warning: DcGetDcName(GOOD_TIME_SERVER_PREFERRED) call failed, error 1355
 A Good Time Server could not be located.
 Warning: DcGetDcName(KDC_REQUIRED) call failed, error 1355
 A KDC could not be located - All the KDCs are down.
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Systems Engineer
Commented:
First thing I would do is turn the old server back on and get it on the network.  The FSMO Roles have not been properly transferred to the new server.  That is what this error is stating:

The server holding the PDC role is down.

After the old DC is on, run the following command as a domain admin:

netdom query fsmo

Open in new window


This will tell you what server has the FSMOs.  There are 5 FSMOs that need to be transferred to the new server before you can properly decommision a DC.

Transfer Role commands:
- https://support.microsoft.com/en-us/kb/255504

If you must perform the transfer from the old server:
- https://support.microsoft.com/en-us/kb/324801

Then you will need to do the following:


Warning: DcGetDcName(GC_SERVER_REQUIRED) call failed, error 1355
 A Global Catalog Server could not be located - All GC's are down.
1. Setup/enable the new DC as a Global Catalog Server (GC)
Link:  https://technet.microsoft.com/en-us/library/cc758330%28v=ws.10%29.aspx


Warning: DcGetDcName(TIME_SERVER) call failed, error 1355
 A Time Server could not be located.
2. Setup the server that holds the PDC role as a Time Server.
Link:  https://technet.microsoft.com/de-de/library/cc794937%28v=ws.10%29.aspx

Fix the first 3 issue and the KDC can be checked after the FSMOs are online again.

Dan

Author

Commented:
All roles are showing up correctly to the 2012 server after running the command.

I changed the GC to be on the 2012 only

After running dcdiag, I still show that all GC's are down

Author

Commented:
how do I make the 2012 the PDC?
Ensure you’re charging the right price for your IT

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden using our free interactive tool and use it to determine the right price for your IT services. Start calculating Now!

Matt DaviesSenior Support Engineer

Commented:
Check DNS records for the new server and ensure the correct server is referenced in the _msdcs section

see DNS for Active Directory

Author

Commented:
What am I looking for in terms of reference?  There are a number of objects
Matt DaviesSenior Support Engineer

Commented:
I would (myself) start by looking for entries that reference your old server these should be duplicated by entries referencing the new server. If these new references do not exist then you have found your problem.

see

DNS AD Zone error

for help

Author

Commented:
ensure the correct server is referenced in the _msdcs section

How do I do this in DNS

error.jpg

Author

Commented:
The AD is showing up now after applying the initial suggestions above.

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial