The time I set doesn't stay set

  • Thread starter Thread starter James W. Long
  • Start date Start date
J

James W. Long

Hi all

I have a win2k client in a domain.
it should synchronize with the win2k3 dc time but its not.

the time is an hour less since the dst time change a few weeks ago,
and no matter how I reset the time, its not correct.
every reboot it goes back or just does not change at all.

only unless I shove it in a different time zone, then its ok.

I did a net time /domain:mydomain /set,
I've stopped and restarted the time service
and I've done a w32time -s,

but it still puts the time an hour back.

I looked on windowsupdate for a fix (there was one for xp),
no such thing available for win2k.

any body know how to fix this?

Thank you in advance

James
 
Hi all

I have a win2k client in a domain.
it should synchronize with the win2k3 dc time but its not.

the time is an hour less since the dst time change a few weeks ago,
and no matter how I reset the time, its not correct.
every reboot it goes back or just does not change at all.

only unless I shove it in a different time zone, then its ok.

I did a net time /domain:mydomain /set,
I've stopped and restarted the time service
and I've done a w32time -s,

but it still puts the time an hour back.
Click to expand...

If you are using a 'Internet Based' Anatomically Correct (Syncronized)
Server to control the Clock Settings of your Networked Computers -
you must 'disable' (de-select) the "Daylight Savings Time" option -
for all computers that connect to this Service.

The OUTPUT from these Clock'd Servers are 'Anatomically Correct' to
within 15 seconds - and do not take into consideration that your
Windows computer has been set to 'accommodate' for "Daylight Savings
Time" MODE.

:-)
 
Back
Top