Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Microsoft's Windows Time Service is not designed to, and does not maintain second accuracy:

What software is available for Windows servers that maintains better than 1 second accuracy across a small (same-site) set of windows servers?


locked by HopelessN00b Jan 21 '15 at 20:37

This question exists because it has historical significance, but it is not considered a good, on-topic question for this site, so please do not use it as evidence that you can ask similar questions here. This question and its answers are frozen and cannot be changed. More info: help center.

closed as off-topic by HopelessN00b Jan 21 '15 at 20:36

This question appears to be off-topic. The users who voted to close gave this specific reason:

If this question can be reworded to fit the rules in the help center, please edit the question.

Similar to, but not a duplicate of… – Adam Davis Jan 22 '10 at 15:51
What type of requirements do you have that require sub 1 second time accuracy? – joeqwerty Jan 22 '10 at 23:17
@joeqwerty - The question is due to this (minor) issue: but I'm also curious how this is handled for time critical applications in fields such as banking, trading, etc. My guess is they don't rely on windows for a time stamp - there are a variety of ways to get around this. But for sites like Stackoverflow, the cost of a 'real' time source might not be worthwhile, while a good NTPD can give you timing that's better than +/- one second. – Adam Davis Jan 25 '10 at 19:12
Thanks for the info. – joeqwerty Jan 25 '10 at 19:15

I use a Windows build of ntpd, available from Meinberg, to synchronize machines on a LAN to a central ntpd server (which in turn synchronizes to a few remote stratum 2 servers).

The ntpd documentation states the following:

It [ntpd] provides accuracies typically less than a millisecond on LANs and up to a few milliseconds on WANs.

Thanks a lot, this seems to have resolved my problem (which was a diffeent one, namely that I can't figure out how to tell w32tm to /resync even when the time is a month off). – reinierpost Jun 12 '11 at 13:02

Not the answer you're looking for? Browse other questions tagged or ask your own question.