[ntp:questions] Re: Why do clients reject win 2003 ntp server?

David L. Mills mills at udel.edu
Fri Jul 1 00:20:01 UTC 2005


Danny,

Look at the rootdispersion 10230.255 ms. The client thinks the server 
has not seen its own server for over a week, assuming the server has 
calculated correctly. The client is just reacting to what it is told and 
gets cranky if its server has lost juice for couple of days.

Dave

Danny Mayer wrote:
> weage98 at yahoo.com wrote:
> 
>> I've been having problems on and off with ntpd not syncing to a Windows
>> 2003 server. Here is the config file:
>>
> Is W2K3 running ntp or w32time? If the latter, we can't tell you since
> it's know to be broken from a protocol point of view. If you are running
> ntpd on it then you need to tell us how it's set up, whether or not it
> has an authorative source of time (use ntpq -p -c rv W2k3.servername)
> and whether you have punch a hole in the firewall to allow NTP packets
> to and from the server.
> 
> Danny
> 
>> server warad01.global.arup.com
>> driftfile /etc/ntp/drift
>> broadcastdelay 0.008
>> keys /etc/ntp/keys
>>
>> Here is ntpq output:
>>
>> ntpq> pe
>> remote refid st t when poll reach delay offset
>> jitter
>> ============================================================================== 
>>
>> 10.164.10.1 10.3.10.3 2 u 2 64 377 0.352 3363.48
>> 2.525
>>
>> ntpq> as
>> ind assID status conf reach auth condition last_event cnt
>> ===========================================================
>> 1 9924 9034 yes yes none reject reachable 3
>>
>> ntpq> rv 9924
>> status=9034 reach, conf, 3 events, event_reach,
>> srcadr=10.164.10.1, srcport=123, dstadr=10.164.1.5, dstport=123,
>> leap=00, stratum=2, precision=-6, rootdelay=125.000,
>> rootdispersion=10230.255, refid=10.3.10.3, reach=377, unreach=0,
>> hmode=3, pmode=4, hpoll=6, ppoll=9, flash=00 ok, keyid=0,
>> offset=3363.480, delay=0.352, dispersion=16.518, jitter=2.525,
>> reftime=c66e6ac8.44bf4956 Thu, Jun 30 2005 8:57:44.268,
>> org=c66e754d.a8d7dccb Thu, Jun 30 2005 9:42:37.659,
>> rec=c66e754a.4bd66277 Thu, Jun 30 2005 9:42:34.296,
>> xmt=c66e754a.4bbf50e3 Thu, Jun 30 2005 9:42:34.295,
>> filtdelay= 0.35 0.30 0.36 0.36 0.35 0.37 0.36
>> 0.35,
>> filtoffset= 3363.48 3366.00 3368.44 3370.91 3373.33 3375.71 3362.51
>> 3364.98,
>> filtdisp= 15.63 16.62 17.60 18.57 19.53 20.49 21.44
>> 22.41
>> ntpq>
>>
>> There are no errors or warnings in the syslog. This client has been up
>> for about ten days. None of the "reject" reasons seem to apply except
>> for maybe "outrageous synchronization distance", which does not seem to
>> be described anywhere in the documentation.
>>
>> Any solutions to this?
>>
>> _______________________________________________
>> questions mailing list
>> questions at lists.ntp.isc.org
>> https://lists.ntp.isc.org/mailman/listinfo/questions
>>
> 
> 
> _______________________________________________
> questions mailing list
> questions at lists.ntp.isc.org
> https://lists.ntp.isc.org/mailman/listinfo/questions
> 




More information about the questions mailing list