Re: [ntp:questions] synchronization distance

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, 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

Re: [ntp:questions] synchronization distance

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. SpecialPollInterval This entry specifies the special poll interval i

Re: [ntp:questions] synchronization distance

David, 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. Windows ex box at one time did use symmetric active mode in error, but I understand it now uses client mode as specified. In any case, Windows NTP (not NTPv4

Re: [ntp:questions] synchronization distance

David L. Mills wrote: I'm confused about your explanation, especially the "default configuration". The definitive explanation of synchronization distance, "default configuration" was talking about w32time. w32time can end up polling about once a week, and therefore reporting a root dispers

Re: [ntp:questions] synchronization distance

David, I'm confused about your explanation, especially the "default configuration". The definitive explanation of synchronization distance, in particular your reference more precisely to root distance, is on the page "How NTP Works" in the online documentation at ntp.org. Dave David Woolley

Re: [ntp:questions] synchronization distance

Atul Gupta wrote: Can anyone explain me what is synchronization distance in case of ntp? and what is distance exceeded problem? It's an estimate of the maximum difference between the time on the stratum zero source and the time measured by the client, consisting of components for round trip