All,
One of the computers on my network runs Windows Embedded Standard and is running the meinberg NTP client and gets its time directly from a GPS clock. The service is set to run automatically and when it restarts it is very close to the GPS clock/"correct" time. However, the next day I notice that it is off by more than an hour! I restarted the NTP client service again, and again the time is good. This time I ran ntpstatus and outputted the results to a log so I could watch them over time, and here is what I am seeing: the offset
field kinda goes back and forth for a few hours around the range ~ [-30, 20000]. The offset will grow and then it will shrink again. However, after some handful of hours, the offset just starts to grow, and it doesn't stop. Almost exactly 24 hours after I had started the logging, I am now reading an offset of 3,729,xxx. I'm not sure what units those are, but my clock was off by about an hour. I restarted the NTP client service, and sure enough the clock corrected itself. Any input on how to debug or narrow down this issue would be much appreciated. We have several other machines that run the same client connected to the same clock without any issue. Our only option in the config file is the ip of the gps clock and the iburst
option, which was the standard when we installed it.