• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Trouble with windows time service

I'm not sure if anyone here can help me with this but I'm stumped at the moment. I'm having trouble getting my windows 2000 and XP pro clients to update their clocks since the time change happened last weekend. The system time on the primary and backup domain controllers are correct and have Atomic Clock Sync running on them, both are running windows server 2003. I've tried running w32tm /resync at the command prompt on the clients to no avail. w32tm /monitor shows that the clients are communicating with both domain controllers. Is there something I'm overlooking here that could be preventing the Windows time service from syncing properly with the domain controllers?
 
AnalogX's Atomic Time Sync (if that's what you're referring to) is not functioning correctly since the new DST. I wrote the guy an email about it. I'm constantly getting a time sync that's one hour off with it since the time change. I don't know that he will update it or not; still waiting on a response.
 
Slikkster, thanks for the help. Apparently the problem was actually the WSUS server not pushing an update out to the clients that was needed to resolve the change in daylight savings time that happened this year..
 
Back
Top