• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 297
  • Last Modified:

windows time sync

Windows 2003 domain, multiple DC's over several locations. XP clients.  Overall everything works globally, but we have one strange problem at just one location.  The XP clients drift off on their time by 5-10 seconds.  All DC's and servers have the correct time (including the local DC and multiple servers at that location), but for some reason the XP clients don't sync correctly.

To add to the confusion, they do sync on reboot (with a correct sync message in event viewer) but they quickly get back off track starting just minutes later.

I am totally confused. I have tried all of the w32tm commands to get it to sync, resync, point directly to the local DC to get time, among other things, but no luck.  Normally this is not important, but this client has a business need to have everything be in sync at this location, and it is not.

Any ideas would be greatly appreciated! This issue is driving me nuts.

Thanks!
0
bta-guy
Asked:
bta-guy
1 Solution
 
random_ruCommented:
Are the systems going off of sync the same make and model? How are they different from the systems working properly?
Time synchronization at a reboot makes sense as clients may sync with the server; the time issue could be caused by CMOS batteries going out, or motherboards.

 Have those systems ever had any issues before? Is it possible to isolate the problem by taking one of the problematic systems off of the net, disconnecting peripherals and monitoring the time. If that does not make a difference, make sure to update the BIOS, drivers, and deploy Windows updates (going along with the company policy of course). If the issue still persists, try looking at Windows: monitoring in the Safe Mode, and startup services restrictions via msconfig.

These steps should definitely isolate and narrow down, if not resolve the issue altogether.
0
 
bta-guyAuthor Commented:
Thanks for your help. You get the points because you were the only one to respond! The issue turned out to be a known problem with the Siemen's hardware running XP Pro in a domain.  Thanks for your response though, much appreciated. your ideas actually helped me through another very loosely related issue with another client.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Get your problem seen by more experts

Be seen. Boost your question’s priority for more expert views and faster solutions

Tackle projects and never again get stuck behind a technical roadblock.
Join Now