[Comm] ntp: no server suitable for synchronization found

[Eugene Prokopiev]

Здравствуйте!

Есть в сети ntp-сервер (192.168.100.1) с такой минимальной конфигурацией:

server 195.2.64.5
restrict 192.168.0.0 mask 255.255.0 notrust nomodify notrap nopeer
driftfile /var/log/ntp.drift

С другой машины (192.168.100.4) порт 123 доступен:

# nmap -sU -p 123 192.168.100.1

Starting nmap 3.55 ( http://www.insecure.org/nmap/ ) at 2006-11-07 12:10 MSK
Interesting ports on 192.168.100.1:
PORT    STATE SERVICE
123/udp open  ntp

Nmap run completed -- 1 IP address (1 host up) scanned in 12.152 seconds

Но синхронизация с 192.168.100.4 не проходит:

# ntpdate 192.168.100.1
  7 Nov 12:11:34 ntpdate[18990]: running as uid(107)/gid(36) 
euid(107)/egid(36) with cap_sys_time chrooted to /var/empty
  7 Nov 12:11:34 ntpdate[18990]: no server suitable for synchronization 
found

В tcpdump при этом вижу:

12:21:47.710113 IP 192.168.100.4.ntp > 192.168.100.1.ntp: NTPv4, Client, 
length 48
12:21:47.710376 IP 192.168.100.1.ntp > 192.168.100.4.ntp: NTPv4, Server, 
length 48
12:21:47.713238 IP 192.168.100.4.ntp > 192.168.100.1.ntp: NTPv4, Client, 
length 48
12:21:47.713441 IP 192.168.100.1.ntp > 192.168.100.4.ntp: NTPv4, Server, 
length 48
12:21:47.716313 IP 192.168.100.4.ntp > 192.168.100.1.ntp: NTPv4, Client, 
length 48
12:21:47.716502 IP 192.168.100.1.ntp > 192.168.100.4.ntp: NTPv4, Server, 
length 48
12:21:47.719331 IP 192.168.100.4.ntp > 192.168.100.1.ntp: NTPv4, Client, 
length 48
12:21:47.719521 IP 192.168.100.1.ntp > 192.168.100.4.ntp: NTPv4, Server, 
length 48

Содержимое последнего пакета в ethereal выглядит так:

Network Time Protocol
     Flags: 0x24
         00.. .... = Leap Indicator: no warning (0)
         ..10 0... = Version number: NTP Version 4 (4)
         .... .100 = Mode: server (4)
     Peer Clock Stratum: secondary reference (2)
     Peer Polling Interval: 4 (16 sec)
     Peer Clock Precision: 0,000008 sec
     Root Delay:    0,2036 sec
     Clock Dispersion:    0,0100 sec
     Reference Clock ID: 195.2.64.5
     Reference Clock Update Time: Nov  7, 2006 09:30:23,3326 UTC
     Originate Time Stamp: Nov  7, 2006 09:29:57,6338 UTC
     Receive Time Stamp: Nov  7, 2006 09:30:26,3401 UTC
     Transmit Time Stamp: Nov  7, 2006 09:30:26,3401 UTC


В чем может быть дело?

-- 
С уважением, Прокопьев Евгений