Results 1 to 2 of 2
[COLOR="Red"]Hello all
I've been trying to resolve the above issue on my Red hatLinux enterprise edition.
I have 3 linux machines, with one running the NTP daemon (/etc/init.d/ntpd).
The other ...
- 02-05-2009 #1Just Joined!
- Join Date
- Feb 2009
- Posts
- 3
Ntp
[COLOR="Red"]Hello all
I've been trying to resolve the above issue on my Red hatLinux enterprise edition.
I have 3 linux machines, with one running the NTP daemon (/etc/init.d/ntpd).
The other 2 are just updating its time using ntpdate command. details are
written below:
192.168.30.30 (with ntpd)
192.168.29.30 (using ntpdate)
192.168.25.30 (using ntpdate)
the 29.30 and 25.30 machines are behind the same router that is connected to
30.30 on a separate router via serial (1T). all of them can ping each
other. no firewall is enabled on the network. in fact, when a router is
setup as ntp server, all of them can sync with its clock. i even tried
synching 29.30 and 25.30 to a public time server and it worked. i just
cannot figure out why it cannot synch with my 30.30.
30.30 has /etc/ntp.conf as follows:
------------------------------------
restrict default ignore
restrict 127.0.0.1
restrict 192.168.0.0 mask 255.255.255.0 notrust nomodify notrap
server 127.127.1.0 # local clock
fudge 127.127.1.0 stratum 10
driftfile /etc/ntp/drift
broadcastdelay 0.008
authenticate yes
keys /etc/ntp/keys
29.30 and 25.30 has /etc/ntp.conf as follows:
----------------------------------------------
restrict default ignore
restrict 127.0.0.1
server 192.168.30.30
driftfile /etc/ntp/drift
broadcastdelay 0.008
authenticate yes
keys /etc/ntp/keys
when i run ntpdate from 29.30 and 25.30, server is not replying back. i see
the requests though using tcpdump on 30.30.
8 Nov 11:03:38 ntpdate[22288]: ntpdate 4.1.1c-rc1 at 1.836 Thu Feb 13 12:17:20
EST
2003 (1)
transmit(192.168.30.30)
transmit(192.168.30.30)
transmit(192.168.30.30)
transmit(192.168.30.30)
transmit(192.168.30.30)
192.168.30.30: Server dropped: no data
server 192.168.30.30, port 123
stratum 0, precision 0, leap 00, trust 000
refid [0.0.0.0], delay 0.00000, dispersion 64.00000
transmitted 4, in filter 4
reference time: 00000000.00000000 Thu, Feb 7 2036 1:28:16.000
originate timestamp: 00000000.00000000 Thu, Feb 7 2036 1:28:16.000
transmit timestamp: c53a1778.ce842741 Mon, Nov 8 2004 11:04:08.806
filter delay: 0.00000 0.00000 0.00000 0.00000
0.00000 0.00000 0.00000 0.00000
filter offset: 0.000000 0.000000 0.000000 0.000000
0.000000 0.000000 0.000000 0.000000
delay 0.00000, dispersion 64.00000
offset 0.000000
8 Nov 11:04:18 ntpdate[22288]: no server suitable for synchronization found
- 02-07-2009 #2
Take a look at this SITE


Reply With Quote
