Win 2003 Server time advancing 1 hour

[ourtechguy]

I am somewhat new to win2003 server. We are having a strange problem with two servers and many (but not all) clients where the clock is advancing 1 hour. This just started happening yesterday: 4/1/08. We have three servers: domain controller, terminal services, and application. All running win2003 server SP2 with the DST patch applied. All patches are up to date. All clients are running XP SP2, DST patch applied, all patches up to date.

The time on the domain controller is correct. The time on the terminal services and application servers "jumps" ahead one hour. The same on some of the clients. If I adjust the time on any of them, they will jump ahead again. On the servers I have unchecked the box "Automatically adjust clock for daylight saving changes". This seems to keep the clock stable at the "correct time". I've done the same thing on the clients, although it seems to work on some and not others.

I have verified that all servers and clients are looking at the domain controller to their time.

I've had a tech from our networking company look at this. Everyone is baffled. His theory is maybe the bios clock is incorrect.

Has anyone seen this before? I would appreciate any help or suggestions on this one.

Regards.

 

[Cstorms]

I would maybe think its to do with DST patches as time change would have originally happend this last weekend as opposed to three weeks ago. Maybe they werent patched and are now thinking its time to go ahead?

Cory

 

[theravager]

use net time to work out where they are syncing from.

But yes i agree with the above posted, dst patches most likely

 

[ourtechguy]

All DST patches are up to date. Ran net time /querysntp, verified time being pulled from PDC. One thing I have noticed, every time the time advances 1 hour, I get a message in the event log: "Time provider NtpClient: The response received from the domain controller is missing the signature. The response may have been tampered with and will be ignored.

Any ideas??

Thanks.

 

[ourtechguy]

Cory and theravager,

You were right, it was a DST patch issue. <insert egg on face here>. I thought I had checked all three servers, but must have only checked two. Went back and checked the DC, somehow autoupdate got shut off. Found a whole list of updates, pulled them down, sure enough one of them was a "later" DST patch. Installed all updates, rebooted all servers, so far so good!

Thanks for the suggestions!!!

 

[Cstorms]

Cool, good to hear.

Stars are fun (shameless, i know.)

Cory

 

[Davetoo]

pathetic actually...

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

 

[Cstorms]

Woh, sorry kitty.. didnt mean to get your fuzz ruffled.

Cory

 

[Roadki11]

i would like to point out auto update for windows patches on a server is a terrible idea!



RoadKi11

"This apparent fear reaction is typical, rather than try to solve technical problems technically, policy solutions are often chosen." - Fred Cohen