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

Antonio Marcheselli puppa at me.la
Tue May 20 22:53:24 UTC 2014


Apologies, I sent a reply to your personal email by mistake - 
Thunderbird has it as default.

Hi Harlan,

Version is 4.2.4p (yes, I know. It's the same version I've been talking 
about and I cannot upgrade it unfortunately).

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

(hopefully it will be better aligned on your news reader!)

The same 130.88.200.4 works from other networks.

If I keep pinging different pools, I can find another NTP server which 
replies.

Question: if I use the pools and for some reason the current server is 
not reachable, when the server is changed will NTP update and start 
using the new server instead? Or will NTP needs to be restarted?

In other words: if my server boots up when a non-reachable server is 
linked, will it keep the same unreachable one till next reboot?

Thank you!


On 17/05/2014 00:37, Harlan Stenn wrote:
> What version(s) of ntp?
>
> What is the output of 'ntpq -p' on one of these machines when you are
> seeing the problem?
>



More information about the questions mailing list