We just had a summer daylight change in US. and pc's on my network are behaving strange, some of them change time and some didn't.
My network: 2 locations both in Midwest, same time zone. Location 1: 120 pcs (windows xp & windows 200) , with 1 Active Direcotry Domain Controller on Windows 2003 Standard. A couple of windows 2000 servers (they up to date) the rest of the servers are Xen or Debian machines (all up to date) , Second location connected through OpenVPN link all pc's are running fine - but they are all connecting to our AD domain controller. Locaiton 2: 10 pcs, and a shared LAN NAS. Both of the routers/firewalls in both locations are pFsense boxes with ntp service running - but it's up to date.
Tried all the usual suspects:
- I have all the latest updates installed
- restarted them
- domain controller is running fine
- most computers are running fine
- I have only one domain controller on my network
- also my firewall serves as ntp server (pfsense) but it's up to date.
- all of the linux machines are fine since they are querying firewall / router for the time.
about 1/3 of my pcs are 1 hour behind. If I change them manually they just change back ( the way domain pc's are supposed to).
I've tried everything but I can't think of anything else to try.
Make sure that your win2k boxes really really have the fix on them if I'm remembering correctly the hotfix was only available for extended support customers and everyone else had to do it manually with these instructions
The command 'w32tm' is very useful for figuring this kind of thing out. It's the Windows time management tool.
Run that on an affected machine and it'll tell you what it sees for time-sources. If it shows that the DCs its pulling time from have a minimal offset, and yet the station is still an hour behind, chances are real good that the local timezone files haven't been updated with the DST updates. If it shows one of your DCs as way out of sync with the others, that's where you want to focus your effort.
Time synchronization has nothing to do with time zones. Windows time synchronization and internal time is always UTC.
Check the following registry key on the clients that aren't updating to ensure they have the correct registry values. You can compare it to a computer that has the correct time zone.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Time Zones\