DST on client PC's 1 hour ahead of server (updates done late)

[Guest]

I have a server (Win2k3 SBS) that is a domain controller and exchange server.
I failed to apply the DST patches until after the DST kicked in. I have
since completed successfully the patches and the time on the server is
correct. However this seems to have caused problems on the client PC's(XP
Pro SP2). All of the client PC's that have the KB931866 patch installed are
now 1 hour AHEAD!!! When I UNCHECK the "Automatically Adjust for DST" in the
Time\Date Properties the time is correct? Also, if I UNINSTALL the patch the
time is correct? I have tried manually resetting the time on the client PC's
but after about 15 minutes it jumps AHEAD an hour. I tried manually setting
it back 2 hours but that didn't work neither did changing the time in the
BIOS. I even went as far as disconnecting from the domain, rebooting the PC,
changing the bios date to BEFORE DST kicked in, booting up into the local PC
not the domain and applying the patch. When I reboot after that after
connecting the ethernet cable and booting into the domain, the time adjusts
again 1 hour AHEAD!!!! This is very frustrating. Any suggestions will be
greatly appreciated.

 

[Brian Gideon]

I have a server (Win2k3 SBS) that is a domain controller and exchange server.
I failed to apply the DST patches until after the DST kicked in. I have
since completed successfully the patches and the time on the server is
correct. However this seems to have caused problems on the client PC's(XP
Pro SP2). All of the client PC's that have the KB931866 patch installed are
now 1 hour AHEAD!!! When I UNCHECK the "Automatically Adjust for DST" in the
Time\Date Properties the time is correct? Also, if I UNINSTALL the patch the
time is correct? I have tried manually resetting the time on the client PC's
but after about 15 minutes it jumps AHEAD an hour. I tried manually setting
it back 2 hours but that didn't work neither did changing the time in the
BIOS. I even went as far as disconnecting from the domain, rebooting the PC,
changing the bios date to BEFORE DST kicked in, booting up into the local PC
not the domain and applying the patch. When I reboot after that after
connecting the ethernet cable and booting into the domain, the time adjusts
again 1 hour AHEAD!!!! This is very frustrating. Any suggestions will be
greatly appreciated.

I don't see how this relates specifically to .NET. You might get a
better response in a more appropriate forum.

Anyway, are you absolutely sure that both the time and the time zone
on the DC are correct? The Windows Time service will try to
synchronize the pc's clock to the DC. If the time zone is incorrect
on the DC then the Windows Time service may read an incorrect UTC
value from it.

 

[Guest]

I don't see how this relates specifically to .NET. You might get a
better response in a more appropriate forum.

Anyway, are you absolutely sure that both the time and the time zone
on the DC are correct? The Windows Time service will try to
synchronize the pc's clock to the DC. If the time zone is incorrect
on the DC then the Windows Time service may read an incorrect UTC
value from it.

What forum would you suggest? I selected General and I have no idea where
that goes?

The time and the time zone on DC are correct. However I do notice that the
time zone is Pacific US & Canada;Tiajuana, whereras the time zone on the
clients that have the KB931866 patch applied are using the Pacific US &
Canada time zone. the Pacific Tiajuana time zone is separate. When i
uninstall the patch, the time zone description is in line with the DC.

Please forward this to the appropriate group or let me know how or if I can
do that.

Thanks
Gil