Daylight Savings 2007 - Problems

[Tecknomage]

Anyone noted problems with the new DLS? Even with the WinXP DLS
update installed.

At work, where we connect via a domain, our desktops keep jumping 1hr
ahead of the correct DLS time. The Win2k server itself keeps the
correct DLS.

At work I have a utility that syncs with atomic clocks via internet,
the WinXP Network Time is not available via a domain, the tab is not
there and this is "normal" situation according to MS KB.

I found out that all the atomic clocks were off by an hour, they are
_not_ on the new DLS setting!

Then I though about it, the atomic clocks are sync to GMT and use the
standard GMT-offset to calculate your local time; and GMT does not use
USofA mandated DLS. Thanks CongrAss!

 

[Guest]

I am a novice about this and what you guys are saying is over my head, but -
maybe you can help a novie! I set my time to current time. Now I can't get
into many of my sites as it gives me a page about settings cookies to be
allowes. Internet Options/tools/etc. I do that, but still it wont' take the
cookies. I went through it with HP and they said all the same tings, and
nothing. I even did a system restore to earlier date of last week - still no
go. So....you guys have any suggestions for a personal use, home based PC
simpleton as to how to fix this and set it to allow cookies? It was working
fine on Sat andth en on Sun started this - I am assuming the time change made
a mess of things.
Any suggestions?
Cheri

 

[Tom wilson]

Here, for a change, I get to issue the classic response you'll find
everywhere:

I have the same problem. Haved you managed to figure it out?

Our clocks are showing anything within a range of 3 hours. On Sunday
my workstation was behind an hour. I did the XP patch and patched all
the servers. The time showed correct. Yesterday, about 11am, half
the clocks in the building jumped ahead an hour. Now some are behind,
some are on time and some an hour ahead. We're getting "Time mismatch
between the client and server" all over the place. It's a freaking
horror show.

And on top of that, Microsoft's DST page is such a nightmare its a
screaming laugh riot. The exchange upgrade paper is 30 freaking pages
long. And it links to a bunch of other 30 page documents. One thing
I'll give Microsoft credit for is yet another good reason to switch to
Linux.

 

[jt3]

It sounds as if your computer did not 'take' the DST patch (my notes tell me
the *last* one was KB931836, but there were, I think, 2 previous versions).
Suggest that you look at MS KB 914387, or perhaps better, at:
http://www.uic.edu/depts/accc/systems/daylight/windows.html
which in addition to describing how to do it, provides the link to
TZEDIT.EXE for downloading. Using this manual TZEDIT method should ensure
that the change is made as necessary.

Hope this helps,
Joe

 

[Tecknomage]

By the way, a fix that works is to download SymmTime and use it, and
it's freeware. Download link in sidebar of....

http://www.ntp-systems.com/

Notes:

Install it for All Users
To have start at boot, copy the link to All Users Startup folder
I kept the clock for GMT and added a clock set to my local zone
Set sync for every 5min
Finally, hid the app so icon appears only in the Taskbar Tray


This took care of problems at work.


But this does still leave the question of what caused the problem in
the first place.

 

[Tecknomage]

It sounds as if your computer did not 'take' the DST patch (my notes tell me
the *last* one was KB931836, but there were, I think, 2 previous versions).

The KB number is NOT a version number. KB = Knowledge Base. It's
referring to a KB article and when MS changes one, they change the
number. Dumb, really DUMB. Updates should have a constant number and
just a title reference to the KB article. Even worst, the title of
the update = "Update for Windows XP" along with many others of the
exact same title. The only way to actually see what the update is for
is to open [X] the description.

 

[Guest]

Again, you guys are way over my head. I went back and just turned the clock
back to the way it was and it fixed my problem. Granted, my problem is not
huge as it is not a work or business thing, just home stuff. however, I don't
have a clue as to what ya'll mean BUT....why not just wait until the time
would have changed come April like every other year and then let the
computers catch up then? So I'm off time for a month, I have my watch! Is
there anything wrong with that that would hurt the computer in any way?
Cheri

 

[Guest]

Well, you guys are still way over my head! But... I did go back and just
turned the clock on the pc back to the time it was and now my problem is
fixed. So...would it stand to reason that once April comes around and the
usual day hits, it will automatically change and be okay, until Sept when it
changes again?
Cheri

It sounds as if your computer did not 'take' the DST patch (my notes tell me
the *last* one was KB931836, but there were, I think, 2 previous versions).

The KB number is NOT a version number. KB = Knowledge Base. It's
referring to a KB article and when MS changes one, they change the
number. Dumb, really DUMB. Updates should have a constant number and
just a title reference to the KB article. Even worst, the title of
the update = "Update for Windows XP" along with many others of the
exact same title. The only way to actually see what the update is for
is to open [X] the description.

Suggest that you look at MS KB 914387, or perhaps better, at:
http://www.uic.edu/depts/accc/systems/daylight/windows.html
which in addition to describing how to do it, provides the link to
TZEDIT.EXE for downloading. Using this manual TZEDIT method should ensure
that the change is made as necessary.

Hope this helps,
Joe

 

[Tecknomage]

Well, you guys are still way over my head! But... I did go back and just
turned the clock on the pc back to the time it was and now my problem is
fixed. So...would it stand to reason that once April comes around and the
usual day hits, it will automatically change and be okay, until Sept when it
changes again?
Cheri

Note the date DLS ends also changed with the law. If you have not
applied the update you will have to manually change again. But if you
don't mind....

MS has a DLS "help" page
http://support.microsoft.com/gp/cp_dst

It sounds as if your computer did not 'take' the DST patch (my notes tell me
the *last* one was KB931836, but there were, I think, 2 previous versions).

The KB number is NOT a version number. KB = Knowledge Base. It's
referring to a KB article and when MS changes one, they change the
number. Dumb, really DUMB. Updates should have a constant number and
just a title reference to the KB article. Even worst, the title of
the update = "Update for Windows XP" along with many others of the
exact same title. The only way to actually see what the update is for
is to open [X] the description.

Suggest that you look at MS KB 914387, or perhaps better, at:
http://www.uic.edu/depts/accc/systems/daylight/windows.html
which in addition to describing how to do it, provides the link to
TZEDIT.EXE for downloading. Using this manual TZEDIT method should ensure
that the change is made as necessary.

Hope this helps,
Joe

I am a novice about this and what you guys are saying is over my head,
but -
maybe you can help a novie! I set my time to current time. Now I can't
get
into many of my sites as it gives me a page about settings cookies to be
allowes. Internet Options/tools/etc. I do that, but still it wont' take
the
cookies. I went through it with HP and they said all the same tings, and
nothing. I even did a system restore to earlier date of last week - still
no
go. So....you guys have any suggestions for a personal use, home based
PC
simpleton as to how to fix this and set it to allow cookies? It was
working
fine on Sat andth en on Sun started this - I am assuming the time change
made
a mess of things.
Any suggestions?
Cheri
:

Here, for a change, I get to issue the classic response you'll find
everywhere:

I have the same problem. Haved you managed to figure it out?

Our clocks are showing anything within a range of 3 hours. On Sunday
my workstation was behind an hour. I did the XP patch and patched all
the servers. The time showed correct. Yesterday, about 11am, half
the clocks in the building jumped ahead an hour. Now some are behind,
some are on time and some an hour ahead. We're getting "Time mismatch
between the client and server" all over the place. It's a freaking
horror show.

And on top of that, Microsoft's DST page is such a nightmare its a
screaming laugh riot. The exchange upgrade paper is 30 freaking pages
long. And it links to a bunch of other 30 page documents. One thing
I'll give Microsoft credit for is yet another good reason to switch to
Linux.





Anyone noted problems with the new DLS? Even with the WinXP DLS
update installed.

At work, where we connect via a domain, our desktops keep jumping 1hr
ahead of the correct DLS time. The Win2k server itself keeps the
correct DLS.

At work I have a utility that syncs with atomic clocks via internet,
the WinXP Network Time is not available via a domain, the tab is not
there and this is "normal" situation according to MS KB.

I found out that all the atomic clocks were off by an hour, they are
_not_ on the new DLS setting!

Then I though about it, the atomic clocks are sync to GMT and use the
standard GMT-offset to calculate your local time; and GMT does not use
USofA mandated DLS. Thanks CongrAss!

 

[jt3]

It rather depends upon how often you end up needing to repeat the
change--roughly, I'd guess, everytime you sync with a time server, since the
OS keeps time in terms of UTC (used to be called Greenwich Time), and, if
you still have the old DST settings in operation, then it'll be OK in April,
but will revert to Standard Time early in the fall.

Hth,
Joe

 

[Guest]

Found actual solution:

The problem was with our Win2k Server that we use for domain logon to WinXP
desktops.

The answer turned out to be in "Windows 2000 Resource Kit Tools for
administrative tasks"
http://support.microsoft.com/kb/927229

Do a find for TZEDIT, and you get a download lin
http://download.microsoft.com/download/5/8/a/58a208b7-7dc7-4bc7-8357-28e29cdac52f/TZEDIT.exe

The problem is the Win2k Server DLS start/stop dates for our time zone were
wrong. Still had the pre-change dates. So every time our desktops sync'd to
the server it would tell the desktops DLS had not started yet.

Used TZEdit to correct the DLS start/stop dates for our time zone on the
server, and our problem is gone.

Many thanks to Google and tech sites it refereed me to.

 

[jt3]

Good to hear that you've worked it all out

Joe