If the following provides some clue to any one. As for the question if the server is jumping or the client is jumping, i also have a fedora12 linux machine on the same subnet getting NTP time for the same server as this windows 7 machine. The fedora machine sync's to submsec and stays there with slight variations but pretty solid overall.
Gautam $ ntpq -pnc rv remote refid st t when poll reach delay offset jitter ============================================================================== *192.168.214.3 192.168.35.253 2 u 1 32 377 0.060 138.779 23.994 associd=0 status=0613 leap_none, sync_ntp, 1 event, spike_detect, version="ntpd 4.2.7p98-o Dec 20 9:19:18.70 (UTC-00:00) 2010 (1)", processor="x86", system="Windows", leap=00, stratum=3, precision=-10, rootdelay=0.091, rootdisp=179.010, refid=192.168.214.3, reftime=d11169fb.a790a9bb Thu, Feb 24 2011 18:36:27.654, clock=d1116a1e.8acb1056 Thu, Feb 24 2011 18:37:02.542, peer=17943, tc=5, mintc=3, offset=95.446, frequency=-325.007, sys_jitter=28.860, clk_jitter=27.862, clk_wander=3.082 _______________________________________________ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions