Time keeps changing to wrong time (1 hr behind) on a workstation.. help? (on domain)

[Mizugori]

I have a workstation here that always sets its time an hour behind. If I manually change the time, ten minutes later it has changed back again... I don't know where this is coming from because the server has the correct time, and before someone says this, daylight savings time is correctly set so that's not the problem. net time reveals that it is (supposedly) getting the time from the server.... ???

any help would be greatly appreciated. thanks!

 

[Nothinman]

Is the time right on the server?

 

[Mizugori]

Originally posted by: Mizugori
the server has the correct time,

 

[Nothinman]

What about the server's timezone or DST settings?

 

[Mizugori]

i appreciate your desire to help me but think about it, if the time on the server is correct (what i want it to be) then obviously it is in the right timezone and DST... also if the time on the server is not the same as the time on the workstation in question, it's pretty clear that the server is not giving the workstation the wrong time...

 

[EagleKeeper]

Set the time correctly and disconnect from the network.

That will give you a clue if the reset is internal or external.

 

[MrChad]

What does the current timezone read?

 

[armstrda]

You need the Windows patch from last year that adjusted the DST from last week to this next week.

 

[bsobel]

Originally posted by: armstrda
You need the Windows patch from last year that adjusted the DST from last week to this next week.

Bingo

 

[bruceb]

Link to the patch for DST (august 2008)

http://support.microsoft.com/kb/951072/

All you need do is select the proper version for your OS, download & install
No reboot needed

 

[stash]

Never, ever change time manually on domain-joined machines.

 

[MedicBob]

I am looking around for this solution too. 30 machines on a domain, 3 are incorrect. Servers are correct, NTP pulling correct time, and 3 of 10 identical computers are incorrect. DST patch loaded via WSUS and is installed, time zones correct on domain and clients, etc...

If I figure it out I will let you know.

 

[Chadder007]

Originally posted by: MedicBob
I am looking around for this solution too. 30 machines on a domain, 3 are incorrect. Servers are correct, NTP pulling correct time, and 3 of 10 identical computers are incorrect. DST patch loaded via WSUS and is installed, time zones correct on domain and clients, etc...

If I figure it out I will let you know.

Make sure that checkbox is checked to use DST also....
If they are Windows 2000 machines, you have to install a 3rd party patch to fix DST.

 

[MedicBob]

Originally posted by: Chadder007

Originally posted by: MedicBob
I am looking around for this solution too. 30 machines on a domain, 3 are incorrect. Servers are correct, NTP pulling correct time, and 3 of 10 identical computers are incorrect. DST patch loaded via WSUS and is installed, time zones correct on domain and clients, etc...

If I figure it out I will let you know.

Make sure that checkbox is checked to use DST also....
If they are Windows 2000 machines, you have to install a 3rd party patch to fix DST.

LOL found it... DST 2008 patch refrenced above was refused by all 3 machines. Applied patch and all is right until next year.

Thanks for the tip with 2000 though.

 

[redbeard1]

I've used this patch on all sorts of 2000 servers to get them keeping the correct time for the new DST dates.

Intelliadmin