[ntp:questions] ntpdate refusing ntp.nmi.nl

Danny Mayer mayer at ntp.isc.org
Thu Jan 8 22:31:07 UTC 2009


Heiko Gerstung wrote:
> Folkert van Heusden schrieb:
>> Hi,
>>
>> It seems the Dutch NMi organisation (which is the time reference for the
>> Netherlands) has an NTP-service as well. Now I tried retrieving the time
>> with ntpdate (just to see if it was reachable) but ntpdate refuses it.
>> Using the regular ntp daemon works fine. Could someone enlighten me why
>> it is refused? I mean: "has gone too long without sync" seems a little
>> odd as it is supposed to be connected to real atomic clocks.
>>
>> folkert at belle:~/bin$ /usr/sbin/ntpdate -d -q -u -t 1 -p 4 ntp.nmi.nl
>>  7 Jan 17:49:01 ntpdate[22293]: ntpdate 4.2.4p4 at 1.1520-o Wed Jul 16 12:36:25 UTC 2008 (1)
>> transmit(134.221.205.12)
>> receive(134.221.205.12)
>> transmit(134.221.205.12)
>> receive(134.221.205.12)
>> transmit(134.221.205.12)
>> receive(134.221.205.12)
>> transmit(134.221.205.12)
>> receive(134.221.205.12)
>> transmit(134.221.205.12)
>> 134.221.205.12: Server dropped: Server has gone too long without sync
>> server 134.221.205.12, port 123
>> stratum 1, precision -18, leap 00, trust 000
>> refid [IRIG], delay 0.03783, dispersion 0.00012
>> transmitted 4, in filter 4
>> reference time:    cd0c473b.73087696  Mon, Jan  5 2009  9:45:47.449
>> originate timestamp: cd0f5b7d.d6ff250b  Wed, Jan  7 2009 17:49:01.839
>> transmit timestamp:  cd0f5b7d.cf7e90ff  Wed, Jan  7 2009 17:49:01.810
>> filter delay:  0.03938  0.03787  0.03879  0.03783
>>          0.00000  0.00000  0.00000  0.00000
>> filter offset: 0.023514 0.023034 0.023029 0.023167
>>          0.000000 0.000000 0.000000 0.000000
>> delay 0.03783, dispersion 0.00012
>> offset 0.023167
>>
>>  7 Jan 17:49:01 ntpdate[22293]: no server suitable for synchronization found
>>
>> ( http://nmi.nl/index.php?pageId=1215&lg=nl )
> 
> A wireshark capture shows that it sends a bogu reftime ...
> Reference Clock Update Time: Jan  5, 2009 08:45:47,4493 UTC
> Originate Time Stamp: Jan  8, 2009 10:15:39,0507 UTC
> Receive Time Stamp: Jan  8, 2009 10:15:39,0375 UTC
> Transmit Time Stamp: Jan  8, 2009 10:15:39,0376 UTC

Is there a KISS code associated with this? This looks like what Dave
implemented for telling clients to go away.

Danny



More information about the questions mailing list