Bad Synchronization with NTP 4.2.7p285 under Windows 7



Hi all

I built NTP 4.2.7p285 with Visual Studio 2010 and I'm trying to synchronize my Win7 box to some public time servers.

It works really bad. The offset jumps around like crazy (-0.559s ... 0.174s) and quite often it loses all its servers (all entries are white in NTP Time Server Monitor).

I'm not experienced with NTP so maybe it's just the configuration I use which is bad.

I start the ntpd with the following command line:

C:\Program Files (x86)\ntp-dev-4.2.7p285 build\bin\ntpd.exe -U 3 -M -g
-c "C:\Program Files (x86)\ntp-dev-4.2.7p285 build\etc\ntp.conf"
-f "C:\Program Files (x86)\ntp-dev-4.2.7p285 build\etc\ntp.drift"
-l "C:\Program Files (x86)\ntp-dev-4.2.7p285 build\etc\ntp.log"
-s "C:\Program Files (x86)\ntp-dev-4.2.7p285 build\stats"

Below you can also find my ntp.conf, and some lines of ntp.log and peerstats. Does anyone have an idea on what's wrong here??

Cheers,
Robert

-- ntp.conf -----------------------------------

server 0.ch.pool.ntp.org iburst
server 1.ch.pool.ntp.org iburst
server 2.ch.pool.ntp.org iburst
server 3.ch.pool.ntp.org iburst

enable stats
statistics loopstats peerstats clockstats

logconfig =clockall +syncall +sysall

-- ntp.log ------------------------------------

28 Jun 09:00:55 ntpd[7968]: ntpd 4.2.7p285@xxxxxxxx Jun 22 16:14:40.96 (UTC+02:00) 2012 (1)
28 Jun 09:00:55 ntpd[7968]: Raised to realtime priority class
28 Jun 09:00:55 ntpd[7968]: Clock interrupt period 15.600 msec
28 Jun 09:00:55 ntpd[7968]: Performance counter frequency 3.118 MHz
28 Jun 09:00:55 ntpd[7968]: MM timer resolution: 1..1000000 msec, set to 1 msec
28 Jun 09:00:55 ntpd[7968]: Windows clock precision 1.000 msec, min. slew 6.410 ppm/s
28 Jun 09:00:55 ntpd[7968]: using Windows clock directly
28 Jun 09:00:55 ntpd[7968]: proto: precision = 1000.000 usec (-10)
28 Jun 09:00:55 ntpd[7968]: proto: fuzz beneath 0.098 usec
28 Jun 09:00:55 ntpd[7968]: Listen and drop on 0 v4wildcard 0.0.0.0:123
28 Jun 09:00:55 ntpd[7968]: Listen and drop on 1 v6wildcard [::]:123
28 Jun 09:00:55 ntpd[7968]: Listen normally on 2 Local Area Connection 2 [fe80::9c44:e23f:6d0:6bbf%15]:123
28 Jun 09:00:55 ntpd[7968]: Listen normally on 3 Local Area Connection 2 192.168.0.100:123
28 Jun 09:00:55 ntpd[7968]: Listen normally on 4 Local Area Connection [fe80::c480:b27f:5fc5:928%12]:123
28 Jun 09:00:55 ntpd[7968]: Listen normally on 5 Local Area Connection 152.96.201.188:123
28 Jun 09:00:55 ntpd[7968]: Listen normally on 6 Loopback Pseudo-Interface 1 [::1]:123
28 Jun 09:00:55 ntpd[7968]: Listen normally on 7 Loopback Pseudo-Interface 1 127.0.0.1:123
28 Jun 09:00:55 ntpd[7968]: Listen normally on 8 6TO4 Adapter [2002:9860:c9bc::9860:c9bc]:123
28 Jun 09:00:55 ntpd[7968]: peers refreshed
28 Jun 09:00:55 ntpd[7968]: 0.0.0.0 c012 02 freq_set ntpd 0.000 PPM
28 Jun 09:00:55 ntpd[7968]: 0.0.0.0 c011 01 freq_not_set
28 Jun 09:00:55 ntpd[7968]: 0.0.0.0 c016 06 restart
28 Jun 09:00:55 ntpd[7968]: DNS 0.ch.pool.ntp.org -> 212.101.0.10
28 Jun 09:00:56 ntpd[7968]: DNS 1.ch.pool.ntp.org -> 81.94.123.17
28 Jun 09:00:56 ntpd[7968]: DNS 2.ch.pool.ntp.org -> 192.33.96.102
28 Jun 09:00:56 ntpd[7968]: DNS 3.ch.pool.ntp.org -> 217.147.208.1
28 Jun 09:01:02 ntpd[7968]: 0.0.0.0 c614 04 freq_mode
28 Jun 09:06:34 ntpd[7968]: 0.0.0.0 0612 02 freq_set ntpd 506.206 PPM
28 Jun 09:06:34 ntpd[7968]: 0.0.0.0 061c 0c clock_step +0.168060 s
28 Jun 09:06:34 ntpd[7968]: 0.0.0.0 0615 05 clock_sync
28 Jun 09:06:34 ntpd[7968]: frequency error 506 PPM exceeds tolerance 500 PPM
28 Jun 09:06:35 ntpd[7968]: 0.0.0.0 c618 08 no_sys_peer
28 Jun 09:06:56 ntpd[7968]: 0.0.0.0 c613 03 spike_detect +0.163921 s
28 Jun 09:09:01 ntpd[7968]: 0.0.0.0 c615 05 clock_sync
28 Jun 09:22:17 ntpd[7968]: 0.0.0.0 0613 03 spike_detect -0.194519 s
28 Jun 09:27:02 ntpd[7968]: 0.0.0.0 061c 0c clock_step -0.291333 s
28 Jun 09:27:02 ntpd[7968]: 0.0.0.0 0615 05 clock_sync
28 Jun 09:27:03 ntpd[7968]: 0.0.0.0 c618 08 no_sys_peer
28 Jun 09:32:50 ntpd[7968]: 0.0.0.0 0613 03 spike_detect -0.151563 s
28 Jun 09:36:08 ntpd[7968]: 0.0.0.0 061c 0c clock_step -0.199364 s
28 Jun 09:36:08 ntpd[7968]: 0.0.0.0 0615 05 clock_sync
28 Jun 09:36:10 ntpd[7968]: 0.0.0.0 c618 08 no_sys_peer
28 Jun 09:38:59 ntpd[7968]: 0.0.0.0 c613 03 spike_detect -0.191208 s
28 Jun 09:46:28 ntpd[7968]: 0.0.0.0 c61c 0c clock_step -0.246502 s
28 Jun 09:46:28 ntpd[7968]: 0.0.0.0 c615 05 clock_sync
28 Jun 09:46:30 ntpd[7968]: 0.0.0.0 c618 08 no_sys_peer
28 Jun 09:49:20 ntpd[7968]: 0.0.0.0 c613 03 spike_detect -0.182278 s
28 Jun 09:52:27 ntpd[7968]: 0.0.0.0 c61c 0c clock_step -0.276819 s
28 Jun 09:52:27 ntpd[7968]: 0.0.0.0 c615 05 clock_sync
28 Jun 09:52:28 ntpd[7968]: 0.0.0.0 c618 08 no_sys_peer
28 Jun 09:55:33 ntpd[7968]: Detected positive leap second announcement for 2012-07-01 00:00:00 UTC
28 Jun 09:57:36 ntpd[7968]: 0.0.0.0 0613 03 spike_detect -0.162238 s
28 Jun 10:00:46 ntpd[7968]: 0.0.0.0 061c 0c clock_step -0.215302 s
28 Jun 10:00:46 ntpd[7968]: 0.0.0.0 0615 05 clock_sync
28 Jun 10:00:47 ntpd[7968]: Leap second announcement disarmed
28 Jun 10:00:47 ntpd[7968]: 0.0.0.0 c618 08 no_sys_peer
28 Jun 10:00:54 ntpd[7968]: Unable to remove prior drift file C:\Program Files (x86)\ntp-dev-4.2.7p285 build\etc\ntp.drift, No such file or directory
28 Jun 10:29:10 ntpd[7968]: 0.0.0.0 0613 03 spike_detect -0.166497 s
28 Jun 10:35:47 ntpd[7968]: 0.0.0.0 061c 0c clock_step -0.478724 s
28 Jun 10:35:46 ntpd[7968]: 0.0.0.0 0615 05 clock_sync
28 Jun 10:35:47 ntpd[7968]: 0.0.0.0 c618 08 no_sys_peer
28 Jun 10:35:54 ntpd[7968]: 0.0.0.0 c613 03 spike_detect -0.190668 s
28 Jun 10:49:19 ntpd[7968]: 0.0.0.0 c61c 0c clock_step -0.275107 s
28 Jun 10:49:19 ntpd[7968]: 0.0.0.0 c615 05 clock_sync
28 Jun 10:49:20 ntpd[7968]: 0.0.0.0 c618 08 no_sys_peer
28 Jun 10:49:26 ntpd[7968]: 0.0.0.0 c613 03 spike_detect -0.286189 s
28 Jun 11:04:42 ntpd[7968]: 0.0.0.0 c61c 0c clock_step -0.306810 s
28 Jun 11:04:41 ntpd[7968]: 0.0.0.0 c615 05 clock_sync
28 Jun 11:04:42 ntpd[7968]: 0.0.0.0 c618 08 no_sys_peer
28 Jun 11:04:48 ntpd[7968]: 0.0.0.0 c613 03 spike_detect -0.235016 s
28 Jun 11:13:30 ntpd[7968]: 0.0.0.0 c61c 0c clock_step -0.264298 s
28 Jun 11:13:30 ntpd[7968]: 0.0.0.0 c615 05 clock_sync
28 Jun 11:13:31 ntpd[7968]: 0.0.0.0 c618 08 no_sys_peer
28 Jun 11:31:17 ntpd[7968]: 0.0.0.0 0613 03 spike_detect -0.177049 s
28 Jun 11:35:55 ntpd[7968]: 0.0.0.0 061c 0c clock_step -0.273984 s
28 Jun 11:35:55 ntpd[7968]: 0.0.0.0 0615 05 clock_sync
28 Jun 11:35:56 ntpd[7968]: 0.0.0.0 c618 08 no_sys_peer
28 Jun 11:36:03 ntpd[7968]: 0.0.0.0 c613 03 spike_detect -0.381124 s
28 Jun 11:49:22 ntpd[7968]: 0.0.0.0 c61c 0c clock_step -0.400168 s
28 Jun 11:49:22 ntpd[7968]: 0.0.0.0 c615 05 clock_sync

and so on ...

-- peerstats.20120628 ----------------

56106 25256.800 81.94.123.17 9024 0.008403623 0.002967139 7.937989257 0.000976563
56106 25258.799 217.147.208.1 9024 0.008597311 0.001987354 7.937988773 0.000976563
56106 25258.799 192.33.96.102 9024 0.009049007 0.001893090 7.937989249 0.000976563
56106 25258.800 81.94.123.17 9024 0.008356312 0.002927523 3.938241385 0.000976563
56106 25259.799 212.101.0.10 9024 0.009206733 0.001947270 7.937989250 0.000976563
56106 25260.801 217.147.208.1 9024 0.008223812 0.001987134 3.938240659 0.000976563
56106 25260.801 192.33.96.102 9024 0.008460775 0.001903957 3.938241374 0.000976563
56106 25260.801 81.94.123.17 9024 0.008537569 0.001966781 1.938371192 0.000976563
56106 25261.799 212.101.0.10 9024 0.008486491 0.001773759 3.938241373 0.000976563
56106 25262.798 217.147.208.1 9024 0.008652889 0.000986062 1.938370345 0.000976563
56106 25262.799 192.33.96.102 9024 0.008473345 0.001930785 1.938371186 0.000976563
56106 25262.799 81.94.123.17 9024 0.008480687 0.001823934 0.938437970 0.000976563
56106 25263.801 212.101.0.10 9024 0.008390895 0.000976563 1.938371179 0.000976563
56106 25264.800 217.147.208.1 9024 0.007331464 0.001983084 0.938437071 0.001175418
56106 25264.800 192.33.96.102 9024 0.007612639 0.001939772 0.938437968 0.001083713
56106 25264.800 81.94.123.17 963a 0.007590401 0.001970550 0.438472297 0.000976563
56106 25265.799 212.101.0.10 9024 0.007455416 0.000976563 0.938437957 0.001291685
56106 25266.801 217.147.208.1 9024 0.006375798 0.001987139 0.438471371 0.001900573
56106 25266.801 192.33.96.102 9024 0.006617675 0.001918425 0.438472296 0.001853501
56106 25266.801 81.94.123.17 963a 0.006668371 0.001969018 0.188489929 0.001642484
56106 25267.800 212.101.0.10 9424 0.006758156 0.000976563 0.438472283 0.001741744
56106 25268.800 217.147.208.1 9424 0.005900546 0.000987590 0.188488982 0.002122211
56106 25268.801 192.33.96.102 9424 0.005674375 0.001921249 0.188489928 0.002515276
56106 25269.803 212.101.0.10 9424 0.005305206 0.001976914 0.188489923 0.002884386
56106 25322.804 81.94.123.17 963a 0.002656444 0.001967984 0.063897652 0.005392393
56106 25325.804 217.147.208.1 9424 0.002525926 0.001987261 0.063904084 0.005101799
56106 25325.804 192.33.96.102 9424 0.002837960 0.001919133 0.063905034 0.004951090
56106 25326.805 212.101.0.10 9424 0.002887388 0.001843444 0.063905030 0.004886516
56106 25389.800 81.94.123.17 963a 0.161779370 0.001967958 0.001686650 0.154550064
56106 25392.802 217.147.208.1 9424 0.161670906 0.001986930 0.001689389 0.154882819
56106 25394.799 212.101.0.10 9424 0.162431575 0.000976563 0.001697773 0.155517725
56106 25394.800 192.33.96.102 963a 0.162020425 0.001922485 0.001705223 0.155072541
56106 25457.798 81.94.123.17 943a 0.164359837 0.002970862 0.001832790 0.145658058
56106 25461.798 217.147.208.1 9424 0.164977319 0.001984258 0.001841090 0.146737109
56106 25462.795 212.101.0.10 9424 0.165505755 0.000979924 0.001838278 0.147182704
56106 25463.796 192.33.96.102 943a 0.165124091 0.001938673 0.001849423 0.146768829
56106 25526.793 81.94.123.17 961a 0.167992256 0.001941924 0.001911360 0.136283116
56106 25529.792 217.147.208.1 9424 0.167796836 0.001986909 0.001907535 0.136645026
56106 25530.794 192.33.96.102 941a 0.168100321 0.001917569 0.001904676 0.136828032
56106 25531.792 212.101.0.10 9424 0.168253748 0.001959960 0.001914046 0.137025947
56106 25594.790 81.94.123.17 961a 0.340641221 0.002932076 0.001941249 0.277720156
56106 25595.956 212.101.0.10 9014 0.173964105 0.001851411 7.937989249 0.000976563
56106 25595.956 217.147.208.1 9014 0.173669688 0.001987915 7.937988773 0.000976563
56106 25597.957 212.101.0.10 9014 0.173456192 0.000976563 3.938241367 0.000976563
56106 25597.957 217.147.208.1 9014 0.172604705 0.001987670 3.938240659 0.001064982
56106 25597.957 192.33.96.102 9024 0.173009219 0.001913913 7.937989249 0.000976563
56106 25598.957 81.94.123.17 9024 0.172420670 0.001966686 7.937989250 0.000976563
56106 25599.959 212.101.0.10 9014 0.172017767 0.001967352 1.938371183 0.001711330
56106 25599.959 217.147.208.1 9014 0.171671660 0.001989429 1.938370353 0.001559277

and so on ...
.



Relevant Pages

  • Re: Not being able to sync the embedded target (client) with the host (server)
    ... I solved it by using busybox's ntp for the time being. ... server 0.pool.ntp.org iburst ... # restrict -6 default kod nomodify notrap nopeer noquery ...
    (comp.protocols.time.ntp)
  • Unable to synchronise meinberg ntp server to clients.
    ... I am using meinberg ntp software but i am having some small ... complications about ntp time server. ... peer ntp.a-lab.fi iburst ... restrict 127.0.0.1 ...
    (comp.protocols.time.ntp)
  • Re: broadcast client
    ... synchronizing with the same ntp server. ... ntp displined clock. ... because the drift discipline is inversely ... The reason for the backup to long poll intervals is ...
    (comp.protocols.time.ntp)
  • Re: Local (own site) NTP servers.
    ... been messing about trying to get a local GPS ... Disciplined NTP server working, ... to be able to take PPS based GPS signals, and act as a server. ... GPSDNTP server for a small low traffic LAN?.. ...
    (comp.protocols.time.ntp)
  • Re: NTPD concurrent clients limit
    ... I use my own Symmetricom gps disciplined ntp servers, my own Datum/Symmetricom gps disciplined rubidium standards for 1PPP and 10 MHz all using HP/Symmetricom gps antennas and gps splitters. ... I also run the latest release of ntpd software on several HP/Compaq Servers. ... Is this packet also implemented in a "canned" or hardware only ntp server? ... NTP is designed to work with poll intervals between 64 seconds and 1024 ...
    (comp.protocols.time.ntp)