Strange problem with workstations

[amn0270]

My customer runs a PDC running 2000 server with AD. What has suddenly
started happening is the 2000 Pro workstations clocks are jumping
ahead one hour. When I go and change them to the correct time, soon
after they automatically jump again. Also I can induce this
immediately by running the command w32tm /resync. Obviously they
normally sync themselves with the PDC but what makes no sense is the
time on the server is set correctly as is the time zone and the DST so
I cannot figure out how they can be getting the wrong time. I cannot
imagine where else they are syncing their clock information from. What
else could cause this. The Windows Time service is running on all the
workstations as well as the PDC.

Thanks in advance,
Adam

 

[Herb Martin]

My customer runs a PDC running 2000 server with AD. What has suddenly
started happening is the 2000 Pro workstations clocks are jumping
ahead one hour.

The time zone was wrong (or DST probably due to the fact it is happening
this week right after the change) and not the time.

You are INCORRECTLY changing the time and the DC is telling them
to put it back correctly.

Since you have 2000 you must manually update the time zone info
and get the time correct on the DC.

Domain computers will then set their time and if you have the time
zone correct it will display correctly.

If you cannot get them to display correctly then do NOT change the
time -- but just change the time zone to make them LOOK correct.

 

[amn0270]

I just tested a theory. If I set the PDC's clock an hour behind, when
I run the w32tm /resync command on the workstation it then sets the
clock correctly though its now 1 hour ahead of the PDC. Its like what
the PDC's clock is visually displaying is not what the PDC's Windows
Time service is actually seeing.

 

[amn0270]

Actually the Time zone setting on the workstations and the server are
all correct. It is Eastern Time. And the DST box is checked on all as
well. So that cannot be it. What else should I look at.

 

[Herb Martin]

I just tested a theory. If I set the PDC's clock an hour behind, when
I run the w32tm /resync command on the workstation it then sets the
clock correctly though its now 1 hour ahead of the PDC. Its like what
the PDC's clock is visually displaying is not what the PDC's Windows
Time service is actually seeing.

You have a problem with the NEW DST displaying incorrectly -- perhaps
on the DC.

Win2000 requires manual updates of the DST settings -- changing the
registry.

 

[Kurt]

Actually the Time zone setting on the workstations and the server are
all correct. It is Eastern Time. And the DST box is checked on all as
well. So that cannot be it. What else should I look at.

DST Started 4 weeks early this year. Windows 2000 computers were not
patched my MS because they are out of the full support cycle. They don't
know that DST has started. If you did not patch them manually, you WILL
have time problems, this year and every year after. Have you patched
your windows 2000 computers?

...kurt

 

[Herb Martin]

DST Started 4 weeks early this year. Windows 2000 computers were not
patched my MS because they are out of the full support cycle. They don't
know that DST has started. If you did not patch them manually, you WILL
have time problems, this year and every year after. Have you patched your
windows 2000 computers?

Twice a year. It ends late (November instead of October) also.

 

[Richard Mueller [MVP]]

You have a problem with the NEW DST displaying incorrectly -- perhaps
on the DC.

Win2000 requires manual updates of the DST settings -- changing the
registry.

I suggest using the utility TZEdit.exe to fix W2k computers. Download from
Microsoft Download web site. Select your time zone, then click "Edit". Set
Daylight Savings Time "Start Day" to second Sunday in March at 2:00 am and
"Last Day" to first Sunday in November at 2:00 am. Otherwise you will have
to manually adjust 4 times per year. See this link:

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

For older clients, like Windows 98 and Windows 95, see this link for info on
creating a reg file to update the settings in the registry manually:

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

TZEdit was slick, but I had to run it on each computer. Using kb 914387 I
was able to create a reg file to fix Win9x clients. I'll know for sure in
April if it worked as expected.