[ntp:questions] Unable to synchronise meinberg ntp server to clients.
Samuel Nyarko
sknnyy2005 at gmail.com
Mon Sep 19 10:55:07 UTC 2011
On Sep 15, 6:30 pm, Dave Hart <h... at ntp.org> wrote:
> Samuel,
>
> Please try commenting out all "restrict" lines in ntp.conf and repeat
> your test. There's a good chance that will fix things, and you can
> iterate over restrict changes to isolate what's breaking. If removing
> restrict lines doesn't solve your problem, please post "ntpq -crv -p"
> output, and describe the clients having trouble in more detail. If
> the clients are using ntpd, on a client try:
>
> ntpq -p
>
> Note which line of output lists the server the client isn't using, and
> assuming it's the first, include output of
>
> ntpq -crv -p -c "rv &1"
>
> on the client. If the server was the third line, change the command
> to use "&3".
>
> Cheers,
> Dave Have
Hello
I have commented out all the restrict lines but the NTP output is the
same.
# NTP Network Time Protocol
# **** ATTENTION ****: *You have to restart the NTP service when you
change this file to activate the changes*
# PLEASE CHECK THIS FILE CAREFULLY AND MODIFY IT IF REQUIRED
# Configuration File created by Windows Binary Distribution Installer
Rev.: 1.26 mbg
# please check http://www.ntp.org for additional documentation and
background information
# Use drift file
# your local system clock, should be used as a backup
# (this is only useful if you need to distribute time no matter how
good or bad it is)
server 127.127.1.1
# but it operates at a high stratum level to let the clients know and
force them to
# use any other timesource they may have.
fudge 127.127.1.1 stratum 12
#driftfile /etc/ntp.drift
driftfile "C:\Program Files\NTP\etc\ntp.drift"
multicastclient 224.0.1.1
broadcastdelay 0.008
broadcastclient
peer 192.168.3.189
# Use a NTP server from the ntp pool project (see http://www.pool.ntp.org)
server ns1.savonia.fi
server ntp.a-lab.fi iburst
# allow localhost
#restrict 127.0.0.1
#restrict 192.168.3.189
# Please note that you need at least four different servers to be at
least protected against
#peer 192.168.3.189
#restrict 192.168.3.189 mask 255.255.255.255 nomodify notrap noquery
server 192.168.3.100
#restrict 192.168.3.100 mask 255.255.255.255 nomodify notrap noquery
#accept packets from
#restrict 192.168.3.100 mask 255.255.255.0 nomodify notrap
#restrict 192.168.3.101 mask 255.255.255.0 nomodify notrap
# one falseticker. If you only rely on internet time, it is highly
recommended to add
# additional servers here.
# The 'iburst' keyword speeds up initial synchronization, please check
the documentation for more details!
server 0.fi.pool.ntp.org iburst
server 1.fi.pool.ntp.org iburst
#server 2.fi.pool.ntp.org iburst
#server 1.se.pool.ntp.org iburst
#server 0.de.pool.ntp.org iburst
# End of generated ntp.conf --- Please edit this to suite your needs
###########################################################
#Section insert by NTP Time Server Monitor 30.8.2011
enable stats
statsdir "C:\Program Files\NTP\etc\"
statistics loopstats
###########################################################
NTP output.
State Remote Refid Stratum Type When Poll Reach Delay Offset Jitter
LOCAL(1) LOCL 12 Local clock 46 64 377 0.000 0.000 0.001
192.168.3.189 INIT 16 Unicast server 1035d 64 000 0.000 0.000
0.000
+ 193.167.78.100 194.100.2.194 2 Unicast server 42 64 377
0.303 -2.332 1.329
+ 212.213.168.140 130.149.17.8 2 Unicast server 44 64 377
15.595 -0.351 1.278
* 62.237.86.234 PPS 1 Unicast server 44 64 377 9.825 -1.832 1.535
- 87.108.20.69 192.36.143.150 2 Unicast server 40 64 377 6.106 6.393
2.070
More information about the questions
mailing list