According to MS's documentation, running XP machines on an AD domain should
make all the machines sync their clocks to, well, SOMETHING. It's not
entirely clear what that something is; "Windows Time service that is
available on domain controllers".
Well we are on a AD domain, and every one of our machines has a different
time. The deviation is not TOO bad, with a delta of about two minutes and the
majority of them all reading the same thing. However the actual time is not
accurate at all, my machine is in the mode and says 10:10 as I write this,
but
www.time.gov states it is actually 10:14.
This is acceptable. I assume the fact that they are all slow by four minutes
is due to the AD server being off my four minutes. But which server? Can I
tell which server my machine is getting its information from?
And the scatter of several minutes between machines is equally unacceptable.
I find it difficult to believe that the internal clocks are THAT poor that
they could loose this much accuracy over the normal polling period, but I
can't find out what the polling period is!
Can someone help me out here? Is there any way to debug and/or fix this?
Anyone have any experience with atomic clock cards?
Maury
Similar Threads
