[ntp:questions] NTP servers not accessible on some networks

Harlan Stenn stenn at ntp.org
Wed May 21 01:18:30 UTC 2014


Antonio Marcheselli writes:
> When running ntpq -p I've got this
> 
> xxxxxxx-2:/etc# ntpq -p
>       remote           refid      st t when poll reach   delay   offset 
>   jitter
> =============================================================================
> =
>   130.88.200.4    .INIT.          16 u    -   64    0    0.000    0.000 
>    0.000
> 
>   xxxxxxx-2:/etc# ntpdate 130.88.200.4
> 20 May 23:30:11 ntpdate[16690]: no server suitable for synchronization found

ntpdate might have -d and/or -v options that would say a bit more about
what is going on.

The two things I notice are that in the above information the stratum of
130.88.200.4 is 16, which means "unsynchronized".  The reach value is 0,
which means the server has not responded to any requests.  If the client
machine has never connected to 200.4, the stratum 16 may simply be the
default value until a packet is received.

H


More information about the questions mailing list