PDC automatically setting its time ahead one hour

[Perilous1]

My Primary Domain Controller (Windows 2000 Server SP4) is self-adjusting its time to one hour ahead of what it should be within seconds of me manually correcting it. We're Mountain Daylight now (not Arizona) and regardless of which time zone I set it to or whether I check the box to account for Daylight Savings it always comes back to the same time, one hour ahead of MDT.

I've thoroughly searched for any programs that might be altering the time and I can't find a thing. The only thing I can think of is a faulty patch for Daylight Savings. But the fact that it changes within seconds of being manaully set suggests something more going on.

Any thoughts on this problem would be greatly appreciated.

 

[LWComputingMVP]

Just checking... is this by any remote chance a Virtual machine?

 

[Perilous1]

Not at all, no. I have been trying various things for the past 16 hours including monitoring packets via the firewall to determine if its attempting to sync with a time server online. So far, I've ruled that out.

Something I've noticed however is that regardless of which time zone I set it to, on the main Date/Time screen it always says it's basing its time from Mountain Daylight Savings. This leads me to believe that the registry is somehow "hardwired" to that particular time zone. Unfortunately, that doesn't really explain its insistance to be on Central Daylight's current time.

 

[Davetoo]

From command prompt enter net time /querysntp to see who it's synching with.

I'm Certifiable, not cert-ified.
It just means my answers are from experience, not a book.

 

[Perilous1]

That's a handy command to know, thanks.

The response from the PDC is that it's not currently configured to use a specific SNTP server.

 

[Davetoo]

Did you apply all of the DST changes last year?

I'm Certifiable, not cert-ified.
It just means my answers are from experience, not a book.

 

[Perilous1]

I did, yes. That is why I originally suspected a corrupted patch.

I've blocked NTP on my firewall and the time hasn't changed in the past hour. I'll continue to watch it throughout the day and if it doesn't change again we'll know it was NTP regardless of what syslog or net time /querysntp suggested.

 

[Perilous1]

Well, it's been going all day on the correct time so I am ready to call it good. I don't suppose anyone knows of a command to run on a domain workstation to indicate which DC its authenticating through? Or even better, a simple way to direct which DC I'd like it to authenticate through as a primary.

 

[itsp1965]

To verify which DC a workstation authenticates to, try clicking on Start->Run and type %logonserver% click OK. It will open an explorer view of the server you authenticate to.
As for the time issue, did you verify the Timezone settings using TZEDIT to ensure that they are correct.