"had to sync with an NTP server every couple of minutes to "workaround" it."
This is NOT how you would do it.. This is not how ntp is designed to work. You don't skew time every couple of minutes to a good source. You let ntp running on your box do what its designed to do, and that is adjust your local clock to run in sync with your known good source.
So I have a box on my local network that syncs with stratum 1 and 2 servers. it will pick the best one.
remote refid st t when poll reach delay offset jitter
+ntp-1.gw.illino 126.96.36.199 2 u 153 1024 377 40.708 -3.994 3.666
-ntp.mya.org 188.8.131.52 2 u 1020 1024 377 21.956 -8.355 16.117
-cloud.hostmist. 184.108.40.206 2 u 212 1024 377 14.443 -10.510 4.463
+ntp.your.org .CDMA. 1 u 55 1024 377 36.940 -4.481 3.222
+saturn.netwrx1. .PPS. 1 u 940 1024 377 42.876 -5.447 3.414
*nist.netservice .ACTS. 1 u 363 1024 377 20.677 -0.521 3.316
* is the one it is currently using.
Those offsets are in milliseconds. currently from that the box is off 0.000521 seconds from that nist server.
I then use this box as my timesource for all other boxes on my network, while also letting people that are using pool.ntp.org to use my server as their timesource. Both IPv4 and IPv6
So here is graph of pool.ntp.org monitoring my server - you will see I had some internet issues earlier in the week. and a blip earlier today. But the green line is offset from their server checking time on my server compared to theirs. That scale on left is milliseconds. Notice it doing a cyclic sort of thing between. And your talking tiny ms offsets here
I have better logs on the box itself, but a bit difficult to get to here from work. So these will work as my examples. See the top entry there is that is .004 of a second off from their server.
ntp running on my server will adjust the local clock to run either slower or faster as it checks on the ntp servers you point it to, to work towards keeping better time. If you just adjust the clock every couple of minutes - it does nothing to help your local clock run better.
You can grab a windows version of ntp herehttp://www.meinberg....lish/sw/ntp.htm
Nice easy to understand instructions, even has a nice windows install and gui to make adjustments to your config. its got a monitoring tool there as wellhttp://www.meinberg....ver-monitor.htm
if you want to update the version of ntp from the 4.2.4p8 they provide you can grab it herehttp://www.davehart.net/ntp/win/x86/
He has windows compiles for versions current and going way back. current version is 4.2.7p295 2012/08/11 davehart has http://www.davehart....win-x86-bin.zip
which is pretty close to current available.
You can get lists of servers here - pick a few close to you that are listed as open to the public, some want you to email them, etc.http://support.ntp.o...mOneTimeServers
Or you could just point to pool.ntp.org -- which uses servers like mine as source.
But again I would not suggest you setup a skew every couple of minutes -- setup up ntp, grab a port from above and use it vs the very limited tool that comes with windows.
Ntp will start of talking to the servers ever 64 seconds or so, and then that will increase in length - you can adjust these min and max poll times.. I think I have mine hard coded to 1024 max currently because I was having some issues where it would just drift and was looking into that so I hard coded max poll. 1024 seconds is 17 some minutes.
NTP is one of my fav play protocols - like DNS, so happy to help you get your box running with NTP correctly if you want, just ask.. PM me if you want. Happy to help!