View Full Version : problems with my ntp server

15th January 2007, 06:41 PM
I am trying to set up a NTP for my network. However, when I go to my winxp client to sync to my ntp box I get a error. I am not sure what I am doing wrong.

My NTP server is
My network is

Here is my config:
# Permit time synchronization with our time source, but do not
# permit the source to query or modify the service on this system.
restrict default kod nomodify notrap nopeer 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.

# -- CLIENT NETWORK -------
restrict mask nomodify notrap

# Use public servers from the pool.ntp.org project.
# Please consider joining the pool (http://www.pool.ntp.org/join.html).
server time-a.timefreq.bldrdoc.gov
server lain.ziaspace.com
#multicastclient # listen on default
restrict time-a.timefreq.bldrdoc.gov mask nomodify notrap noquery
restrict ntp0.sjbcom.com mask nomodify notrap noquery

# Undisciplined Local Clock. This is a fake driver intended for backup
# and when no outside source of synchronized time is available.
server # local clock
fudge 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

# 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.
keys /etc/ntp/keys


# ntpq -p
remote refid st t when poll reach delay offset jitter
================================================== ============================
*time-A.timefreq .ACTS. 1 u - 64 377 107.771 4.932 24.218
+lain.ziaspace.c 2 u 1 64 377 68.789 -18.547 16.318
LOCAL(0) LOCAL(0) 10 l 1 64 377 0.000 0.000 0.002

15th January 2007, 07:11 PM
My network is

# -- CLIENT NETWORK -------
restrict mask nomodify notrap

One of these is wrong.
Have you opened port UDP:123 in the Fedora firewall?

15th January 2007, 07:22 PM
Sorry forget the 1
My network is

15th January 2007, 07:23 PM
My firewall is not running