[ntp:questions] Not able to connect

terrypearl fastsnip-bcard at yahoo.com
Thu Nov 16 01:44:32 UTC 2006


Been trying to get my PC to connect to an internet time server via ntpd. 
No luck thus far.

OS - Linux, Fedora Core 5
Connected to internet via ethernet to Actiontec DSL ethernet hub

Have tried turning the Actiontec Firewall completely off and setting the 
Linux Firewall to allow TCP port 13.

All attempts to connect to an NTP server fail.

Any hints as to how to get ntp working and keeping the clock updated 
automatically?

The following are excerpts from the file /var/log/messages:

Nov 15 16:19:22 localhost ntpdate[2140]: can't find host time
Nov 15 16:20:06 localhost ntpdate[2140]: no server suitable for
synchronization found
Nov 15 16:20:06 localhost ntpd[2155]: ntpd 4.2.0a at 1.1196-r Thu May 11
09:19:35 EDT 2006 (1)
Nov 15 16:20:06 localhost ntpd[2155]: precision = 2.000 usec
Nov 15 16:20:06 localhost ntpd[2155]: Listening on interface wildcard,
0.0.0.0#123
Nov 15 16:20:06 localhost ntpd[2155]: Listening on interface wildcard,
::#123
Nov 15 16:20:06 localhost ntpd[2155]: Listening on interface lo,
127.0.0.1#123
Nov 15 16:20:06 localhost ntpd[2155]: Listening on interface eth0,
192.168.1.64#123
Nov 15 16:20:06 localhost ntpd[2155]: kernel time sync status 0040

Nov 15 16:20:55 localhost ntpd[2155]: frequency initialized -336.519
PPM from /var/lib/ntp/drift

Nov 15 16:22:45 localhost ntpd[2155]: getaddrinfo: "time" invalid host
address, ignored
Nov 15 16:23:45 localhost ntpd[2155]: getaddrinfo: "time" invalid host
address, ignored

Nov 15 17:08:12 localhost ntpd[2155]: ntpd exiting on signal 15
Nov 15 17:08:17 localhost ntpd_initres[2895]: parent died before we
finished, exiting
Nov 15 17:09:34 localhost ntpdate[3425]: can't find host time
Nov 15 17:10:06 localhost ntpdate[3425]: can't find host time
Nov 15 17:10:52 localhost ntpdate[3425]: no server suitable for
synchronization found
Nov 15 17:10:52 localhost ntpd[3477]: ntpd 4.2.0a at 1.1196-r Thu May 11
09:19:35 EDT 2006 (1)
Nov 15 17:10:52 localhost ntpd[3477]: precision = 2.000 usec
Nov 15 17:10:52 localhost ntpd[3477]: Listening on interface wildcard,
0.0.0.0#123
Nov 15 17:10:52 localhost ntpd[3477]: Listening on interface wildcard,
::#123
Nov 15 17:10:52 localhost ntpd[3477]: Listening on interface lo,
127.0.0.1#123
Nov 15 17:10:52 localhost ntpd[3477]: Listening on interface eth0,
192.168.1.64#123
Nov 15 17:10:52 localhost ntpd[3477]: kernel time sync status 0040


The following is the file /etc/ntp.conf file:

# Permit time synchronization with our time source, but do not
# permit the source to query or modify the service on this system.

restrict default nomodify notrap noquery

# Permit all access over the loopback interface. This could
# be tightened as well, but to do so would effect some of
# the administrative functions.
restrict 127.0.0.1


# -- CLIENT NETWORK -------
# Permit systems on this network to synchronize with this
# time service. Do not permit those systems to modify the
# configuration of this service. Also, do not use those
# systems as peers for synchronization.
# restrict 192.168.1.0 mask 255.255.255.0 nomodify notrap


# --- OUR TIMESERVERS -----
server 0.pool.ntp.org
server 1.pool.ntp.org
server 2.pool.ntp.org


# --- NTP MULTICASTCLIENT ---
#multicastclient # listen on default 224.0.1.1
# restrict 224.0.1.1 mask 255.255.255.255 nomodify notrap
# restrict 192.168.1.0 mask 255.255.255.0 nomodify notrap



# --- GENERAL CONFIGURATION ---
#
# Undisciplined Local Clock. This is a fake driver intended for backup
# and when no outside source of synchronized time is available. The
# default stratum is usually 3, but in this case we elect to use stratum
# 0. Since the server line does not have the prefer keyword, this driver
# is never used for synchronization, unless no other other
# synchronization source is available. In case the local host is
# controlled by some external source, such as an external oscillator or
# another protocol, the prefer keyword would cause the local host to
# disregard all other synchronization sources, unless the kernel
# modifications are in use and declare an unsynchronized condition.
#
fudge 127.127.1.0 stratum 10

#
# Drift file. Put this in a directory which the daemon can write to.
# No symbolic links allowed, either, since the daemon updates the file
# by creating a temporary in the same directory and then rename()'ing
# it to the file.
#
driftfile /var/lib/ntp/drift
broadcastdelay 0.008

#
# Keys file. If you want to diddle your server at run time, make a
# keys file (mode 600 for sure) and define the key number to be
# used for making requests.
#
# PLEASE DO NOT USE THE DEFAULT VALUES HERE. Pick your own, or remote
# systems might be able to reset your clock at will. Note also that
# ntpd is started with a -A flag, disabling authentication, that
# will have to be removed as well.
#
keys /etc/ntp/keys
restrict 0.pool.ntp.org mask 255.255.255.255 nomodify notrap noquery
restrict 1.pool.ntp.org mask 255.255.255.255 nomodify notrap noquery
restrict 2.pool.ntp.org mask 255.255.255.255 nomodify notrap noquery
restrict 129.6.15.28 mask 255.255.255.255 nomodify notrap noquery
restrict 129.6.15.29 mask 255.255.255.255 nomodify notrap noquery
server time
restrict time mask 255.255.255.255 nomodify notrap noquery
server time
restrict time mask 255.255.255.255 nomodify notrap noquery
server time-a.nist.gov
restrict time-a.nist.gov mask 255.255.255.255 nomodify notrap noquery
server time-b.nist.gov
restrict time-b.nist.gov mask 255.255.255.255 nomodify notrap noquery
#broadcastclient

Any Ideas on how to get ntp to connect and maintain the clock???




More information about the questions mailing list