[ntp:questions] Client using Meinberg NTP can't sync with ntp server problem
david-taylor at blueyonder.co.uk.invalid
Wed Jul 9 09:40:31 UTC 2014
On 09/07/2014 08:31, vothanhhung22 at gmail.com wrote:
> Hi all,
> Currently, I am working with meinberg ntp and I can't sync with ntp server. I have made rules that allow UDP port 123, turned off w32time and change to some popular ntp server but there is no luck.
> I have followed this FAQ:
> I'm using windows web server 2008 R2, Meinberg NTP version is http://www.meinbergglobal.com/english/sw/ntp.htm#ntp_stable (the spider man one)
> this is the output from ntpq -pn
> C:\Windows\system32>ntpq -pn
> remote refid st t when poll reach delay offset jitter
> *18.104.22.168 22.214.171.124 2 u - 512 17 30.634 -46.455 23.503
> this is the output from ntpq -crv
> C:\Windows\system32>ntpq -crv
> associd=0 status=0615 leap_none, sync_ntp, 1 event, clock_sync,
> version="ntpd 4.2.6p5 at 1.2349-o Jul 30 11:55:08 (UTC+02:00) 2012 (2)",
> processor="x86", system="Windows", leap=00, stratum=3, precision=-21,
> rootdelay=31.931, rootdisp=109.468, refid=126.96.36.199,
> reftime=d767610b.0bd46116 Wed, Jul 9 2014 13:34:51.046,
> clock=d7676117.210e61c3 Wed, Jul 9 2014 13:35:03.129, peer=7365, tc=9,
> mintc=3, offset=-46.455, frequency=-65.949, sys_jitter=0.000,
> clk_jitter=31.032, clk_wander=0.024
> And this is my ntp.conf file:
> server 0.hk.pool.ntp.org minpoll 9 maxpoll 11 iburst
> I am looking forward for your response.
Just a few points:
- the presence of the "*" in the output of ntpq -pn indicates sync, so
I'm unsure that the problem is.
- I recommend installing outside the \Program Files\ directory, and I'm
not sure you've done that.
- Using a single server is bad practice. Use the pool directive instead
and don't try and specify the min/max poll:
pool hk.pool.ntp.org iburst
NTP will adjust the polling as it needs to, and will try and get a
number of servers rather than just one. You should use a driftfile line
in your ntp.conf file as well.
if you have installed to C:\Tools\NTP as I recommend:
You actually seem to have made things more complex for yourself than a
default install might have done, but perhaps that is the result of
(There are some issues installing on Windows Server, of which I have no
More information about the questions