gbusenberg at yahoo.com gbusenberg at yahoo.com
Wed Nov 14 21:40:11 UTC 2012

They HP DL 380 G7 Servers.  Sorry for the typo.  No virtual machines are being used.  Each Windows 2008 Server has dedicated hardware and is almost idle in terms of load. Yesterday after making the changes of getting rid of the tinker and server & fudge everything seemed better however after it ran for about 18 hours, I am back to about 250ms offsets in ntpq -p.

I will try the suggestions that Charles made and then if that doesn't work, I will try the latest binaries that David suggested.

server iburst minpoll 5 maxpoll 5
broadcastdelay 0.000800  ## in seconds 

I want to give some more detals on my setup just to make sure there is nothing important that I have not shared:

My small network of 8 Windows 2008 Servers & Windows 7 PCs are all on the same 1gbps LAN. is one of my servers and syncs time with  ntpq -p is shown below for

     remote           refid      st t when poll reach   delay   offset  jitter
*    2 u  407  512  377    0.051  119.693  37.748 only supports NTP Version 3.  On, I have my ntp.conf file set as follows

driftfile "C:\Program Files (x86)\NTP\etc\ntp.drift"
server version 3 iburst minpoll 4

I can understand that I would have a hard time keeping good NTP time with since this server doesn't support NTPV4.  The thing I don't understand is why all of my other servers that get their NTP time from using NTPV4 are unable to keep a low offset after the NTP Service has been running for about a day.

Below ntpq -p from my server which gets time from  I see there is a lot of Jitter.  Is the offset of 259ms. 

     remote           refid      st t when poll reach   delay   offset  jitter
*       3 u 1006 1024   77    0.043  -259.69 165.850

driftfile "C:\Program Files (x86)\NTP\etc\ntp.drift"
server iburst minpoll 4

My machines are in a Windows 2008 Domain.  There are no firewalls and all firewalls on the Windows Servers is disabled.  I have verified on all machines that the Windows Time Service is disabled so I am only using the "Network Time Protocol Daemon".

I went through the install guide for windows at:


Greate guide.  Wish the Meinberg site had a link to this (Or maybe it doesn and I just missed it).  Everything looks good on my end except I left the default of installing in Program Files as opposed to C:\Tools which I don't think is my issue.  I will try the steps to upgrade the binaries to 4.2.7p285 in the Guide. Also, I checked Event Viewer on a couple of servers and there are no errors for NTP.

More information about the questions mailing list