[ntp:questions] synchronization distance

David Woolley david at ex.djwhome.demon.invalid
Sat Dec 4 14:24:25 UTC 2010

David L. Mills wrote:
> BlackList,
> I say again with considerable emphasis: this is a Microsoft product, not 
> the NTPv4 distribution that leaves here. What you see is what you get, 

But it is often NTPv4 reference version that is used as the client and 
fails to synchronize because the root dispersion is too high.

Corporate politics are such that it is difficult to get a Unix system, 
or even Windows running the reference version, near the root of the time 
distribution  tree.  People deeper in the tree then see the effects, 
even if they are using the reference implementation.

> warts and all. I doubt it has anything to do with root distance, or any 
> other public specification, but that doesn't make any difference if the 
> customer is satisfied with the performance. Just don't compare it with 
> anything in the NTP distribution, documentation or specification.
> Dave
> E-Mail Sent to this address will be added to the BlackLists wrote:
>> David L. Mills wrote:
>>> I had no idea somebody would try to configure current
>>> NTPv4 with a poll interval of a week.
>>> The current maximum allowed is 36 h.
>> <http://technet.microsoft.com/en-us/library/cc773263%28WS.10%29.aspx>
>> <BlockQuote>
>> SpecialPollInterval
>> This entry specifies the special poll interval in seconds
>>  for manual peers. ...
>> The default value on stand-alone clients and servers is 604,800.
>> </BlockQuote>
>> {7 days}

More information about the questions mailing list