DST Yes /no /maybe


Y

YorS

OK last month I did the DST stuff (I thought).
But this morning my XP machines are not handing this thing too well.
I have a few machines that are correct, I have a few machines that are 1
hour behind, I have a few machines that are 1 hour ahead and I have one
machine that is Two hours behind.

I logon as admin reset the time and on the next logon the time changes
again. Even if I set it NOT to adjust for DST it still does.
We get time info from the server (Win2k DC) during logon. All the Win2k Pros
are fine even the one 95 workstation is fine.

Now last Friday I made a point of checking All my Machines in anticipation
of the Old DST. All my machines were the same. Same SPs, same patches, same
Time Zone settings (2nd Sun of Mar and 1st sun of Nov). Used the TZEdit and
ALL machines were the same.

So why are my machines showing different times? It would make more sense if
they were all out in the same way.
Where does XP get this info and how do I correct?
 
Ad

Advertisements

Y

YorS

Yes it is...I double checked everything last Friday and I have checked all
the servers Twice this morning.
 
F

Frankster

Check that the problem workstations are set to automatically correct for
DST.

-Frank
 
Y

YorS

I have done that, infact ever tried telling it NOT to Auto Adjust. Does not
work any better.
I would prefer if it if it would leave the clock alone. I can not even
Manually set the time with out the O/S trying to "Help" me. At this point I
could do with out the "Help", Thank you very much.
 
Ad

Advertisements

Y

YorS

Yes, The logon script is set to...
synchronizes workstation clock with server
Why would this be wrong? If the WSs are more then 15 minutes out they have
problems and on a few machines the clock drifts so that after a while their
clock is too far out. That is what it is for, isn't it?
 
F

Frankster

Depends on how you are doing it. If you are using "net time /set", that is a
legacy NetBIOS setting that will be overridden by the new (with W2K)
built-in SNTP automatic time sync.

The point is that everything from the W2K and later era supports automatic
time sync with the Domain Controller and no manual (or login script) is
needed. My guess is that this logon script is complicating your
troubleshooting. Or worse, causing the problem, if set to sync with a less
than adequately configured machine.

-Frank
 
Y

YorS

Well on the one hand I have got things going better.
I used IntelliAdmin. I had to first uninstall the TimeZone Patch and then
install again. I noted it kept telling me that the ALASKA time zone was
incorrect, not sure why that matters as we are no where near Alaska. Where
as our Time zone (Eastern) showed OK. I had used TzEdit before but only
edited the Eastern Zone as it was the only one needed, or so I thought.
Well, Now my XPs are correct. How ever, am I going to have more problems
this fall?

And we are using "SETTIME" within a KIX script to sync the WSs with a Win2k
DC. Which the IntelliAdmin showed as fine. What do you mean by: "a less than
adequately configured machine." ?????
 
Ad

Advertisements

Ad

Advertisements

F

Frankster

Does SETTIME use SNTP or NetBios?

One reason you might want other time zones coded correctly is if you receive
mail from them. Mail is based on UTC corrected to the local time zone. There
are other resons it is good to have all time zones configured correctly. Not
only your own.

-Frank
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

DST Issues w/ XP Pro & Outlook 9
Daylight savings patch 8
Windows "Time" Problem 12
DST Updates - fun, fun 17
not changing time 2
SP3 and DST 3
Can't change time zone 8
DST Confusion 4

Top