[ntp:questions] ntp clients out of sync with server

naihong at gmail.com naihong at gmail.com
Wed Oct 29 00:55:13 UTC 2008

On Oct 28, 2:38 pm, David Woolley
<da... at ex.djwhome.demon.co.uk.invalid> wrote:
> naih... at gmail.com wrote:
> > I know should appear in any clients'  configure file. But
> > without this statement, the display from ntpq -p,  only display the
> > client out of sync with server. I mean tally '*' is missing from
> In that case the server is being treated as invalid.  You will need to
> provide the output of the ntpq rv command, run against the association
> id (assoc subcommand) of the server.
The output from ntpq -c"rv":
assID=0 status=0644 leap_none, sync_ntp, 4 events, event_peer/
version="ntpd 4.2.4p5 at beijing-o Sep 01 9:15:56 (UTC+02:00) 2008
processor="unknown", system="WINDOWS/NT", leap=00, stratum=6,
precision=-20, rootdelay=0.304, rootdispersion=58.322, peer=46864,
reftime=ccb22e3c.45338a42  Tue, Oct 28 2008 17:35:08.270, poll=6,
clock=ccb22eb8.2242d2bb  Tue, Oct 28 2008 17:37:12.133, state=4,
offset=-33.131, frequency=-47.242, jitter=10.226, noise=21.119,
stability=0.104, tai=0

> If you have any w32time servers upstream of you, please note that
> w32time doesn't honour the maximum distance heuristic, so will report a
> low stratum number even when the root dispersion is impossibly high,
> because the server hasn't been synchronised for many days, e.g we have
> one in the office that is reporting stratum three, even though it has
> not been synchronised for so long that the time is almost 7 seconds out.
w32time has been disabled on all windows based computer, no matter
server or client. I have tested ntpd in pure linux environment before,
both server/client are linux, and have no internet connection. It
seems clients can find the server has untrusted time and refuse to
sync with it after running a period of time(about 1 day).
> > server, I did not know which time the client  followed.  So add
> >, just make sure the client sync to its own clock. At
> Clients are ALWAYS synchronised to their own clock (for NTPv4)!

More information about the questions mailing list