Software

Ask something
Question Locked

Clock randomly changing on random systems

0 helpful
8 replies

by brian 1 view

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I have approx. 80 to 90 systems in many different office locations. The PC's are all Dell Optiplex GX 320, 330, or 360 models. The clock randomly resets itself back exactly 1 hour on random PC's. The systems are not running through a domain, however they are all connected to the same network. All settings are the same (IE clock sync and Daylight savings time check box is unchecked), except for the service packs, some are SP2 and some SP3 (Windows XP). I have checked the BIOS to see if it has an option for the clock to adjust for daylight savings time so I could disable it, however it does not. Does anybody have any ideas as to why they are doing this.

8 replies

by patb071

Are all the machines running SP3 changing the time correctly and not SP2? the daylight savings time changed a week earlier last year, so next week you should see all the times to be the same.

by brian

Quite literally, random machines, some running SP3, some SP2, some GX320's, some GX330's, and some GX360's....as I said...quite random, with no ryme or reason for it.

by bapster

Good Point, prior to SP3, and when daylight savings (date was changed) we had to apply a patch to our machines in order for them to work properly during the DST switch over/and back.

by brian

Yes, however was it a microsoft patch, and as well, if SP3 has the patch built in, shouldn't the SP3 machines not be affected (though they are)?

by balge

maybe, if they were getting their time from an unpatched machine?
why not update all the machines to the same point ?
cheers

by brian

As I was searching through the many different possibilities, I found that each system that was having this issue was auto syncing to server: time-b.timefreq.bldrdoc.gov

I changed the auto sync to time.nist.gov and the problem seems to have resolved.... it is strange as to what was going on, but it seems to be working!

This discussion is closed to new replies.