Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations derfloh on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

PDC Emulator will not reference external time source

Status
Not open for further replies.

rblissbrown

IS-IT--Management
Aug 15, 2008
1
US
We have a new PDC emulator in our environment (total of 12 DCs). I have read everything I can find on time sync issues and cannot resolve our issue. I followed the MS KB article on removing the time source when I demoted the former PDC-E, and when I do the w32tm /monitor, I see that all of the DCs are referencing the new PDC-E. My problem is that the PDC-E will not recognize the time source I enter, it always comes back with RefID: 'LOCL' [76.79.67.76].
I have verified that the GPOs for time are set to Not configured.
I have unregistered and registered w32time.dll.
I have tried using our internal time source (CISCO switch) that all other systems use as the time source.
I have tried using an external time source (several different ones recommended).
I have configured in the registry and on the command line.
When I do a net time /querysntp is reports correctly, but when I do the w32tm /monitor is always shows the PDC-E referencing the local address.
I have researched this for hours with no success. I found one thread that someone was having the same issue but there was no resolution. I need to get this resolved because our Windows servers keep getting out of time with the Unix servers causing issues when we try to troubleshoot application problems that are distributed.
 
According to MS, the W32Time service is version 3 compliant, but I have had very consistent success by downleveling a cisco device to version 1 and sync'ing time from it.

On one of your secondary switches, add the "version 1" parameter to your ntp server line. Then configure your Windows box to update from that switch. Since the cisco device acts as both a client and a server this should cause you no issues.

If you are still not successful, then I suggest finding 3rd party NTP server to install on your DC.

PSC

Governments and corporations need people like you and me. We are samurai. The keyboard cowboys. And all those other people out there who have no idea what's going on are the cattle. Mooo! --Mr. The Plague, from the movie "Hackers
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top