Warning: DcGetDcName(TIME_SERVER) call failed, error 1355

H2Omike
H2Omike used Ask the Experts™
on
Running dcdiag on a windows 2003 native AD domain.. Simple, one domain, one forest, three domain controllers all of them GCs.  

Every AD server returns this error:  DC1 is not advertising as a time server.

And this:
Starting test: FsmoCheck
         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.

I have done all of this:
http://ben.goodacre.name/tech/Domain_Controller_is_not_advertising_as_a_time_server_Error_in_dcdiag_(Windows)

Netdom query pdc runs fine on all of the servers, returns the correct pdc emulator.  Everything seems to be fine except that error in dcdiag and Event ID: 14 is in one AD server's log multiple times:  The time provider NtpClient was unable to find a domain controller to use as a time source. NtpClient will try again in 240 minutes.

This server is on a different subnet than the other two.  I just ran w32tm on the other AD server (non pdc emulator) and it returned 'the computer did not resync because no time data was available' and logged an event id: 14 in the system log.  

This one has me stumped.. any ideas how to fix this?  I want to upgrade the domain to AD 2008, but am afraid to with this happening.  
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
H2OmikeIT Manager

Author

Commented:
http://forums.techarena.in/active-directory/32759.htm

This seems to have helped.  Now when I run dcdiag /e the only error I get is  DC1 is not advertising as a time server.  DC1 is the pdc emulator, the other two AD servers are now sychronizing (either with the pdc or with time.windows.com) and they are advertising as a valid time server.  I've changed DC1's announceflags registry setting to a, 5, 10.. and run w32tm /config /update afterward each change, but to no avail.
Justin OwensITIL Problem Manager
Commented:
Can you move your FSMO PDC Emulator role to a different DC?
H2OmikeIT Manager

Author

Commented:
Yes, just did.  Netdom query pdc now returns the new pdc emulator.  dcdiag /e now has just the one error, that the original pdc emulator is still not advertising as a time server.  
Success in ‘20 With a Profitable Pricing Strategy

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!

Justin OwensITIL Problem Manager

Commented:
It won't any more.  If you move the PDC emulator role the new FSMO role server should be the one advertising.  What error is left?
H2OmikeIT Manager

Author

Commented:
DC1 was the original pdc emulator, DC2 is the new pdc emulator.  The error left in dcdiag is:

Warning: DC1 is not advertising as a time server.
DC1 failed test advertising.
Commented:
The error related due to time sync issue.

Please check port 123 tcp as well as UDP has been opened on DC for inbound & outbound connection in firewall.

Please check below link & reply also enable debug logging for further analysis:

http://support.microsoft.com/kb/816042/en-us    How to configure an authoritative time server in Windows Server

http://support.microsoft.com/kb/816043/en-us    How to turn on debug logging in the Windows Time Service


Good link  

http://www.experts-exchange.com/Operating_Systems/Windows_Server_2003/Q_20973984.html
H2OmikeIT Manager

Author

Commented:
Thanks for the answers.  This did it!  Wow.. spent a good portion of this week trying to fix this and looked at that thread but not close enough I guess.  -Mike

ok !!! I solved this !!!! heheh I sorted it out.. i know i cant get any points now.. but here goes... I had SAME isses.. your note to look in the domain controller policy led me to pick through it to find what the REAL problem was and not just to delete the policy.... soo here it is...

go to ..

computer settings --> administrative templates --> system --> windows time service

and configure the obvious settings there! By default i guess sp1 or something disabled this for me as i never had an issue until then! I would set up the server and the policy was blocking it all the long!!! All i did was tell the policy to allow ntp to run as a server on my PDC and rebooted, and oila! I passed all tests now from dcdiag, nltest etc !!!! :) I hope this helps someone still! :)

-Noel
Pete LongTechnical Consultant

Commented:
I had the same problem! and a similar solution

Windows - Error 'A Good Time server could not be located'

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