Networks

Ask something
Discussion Locked

Network Time Protocol Is 3 Minutes Fast

0 helpful
3 replies

by artcabot

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

This is totally crazy, but here it is...
We have NTP running via Timesync.nlm (v5.15) and it reports a time that's exactly 3 minutes LATER than the time reported by the same source (NIST or USNO) when viewed via a browser. It appears that the "browser" source is correct because it matches radio/TV stations,etc. Also, when using Polygon's "Cadence" product on another server, NTP reports the same "later" time.

3 replies

by estebandelatorre

Double check your "Daylight saving time offset" under servman / Server parameters / time.

You may have entered into the daylight saving period and the current offset may be
-3 minutes. Correct the offset or disable the daylight saving.

edt@bancobgn.com

by artcabot

Just for everyone's information: We discovered in an obscure TechNote that a Reference Time Server has to have at least one Primary Time Server in its Configured Sources list or else it can't set itself. We added one, then unloaded/reloaded Timesync.NLM and it began issuing large offsets where before they were coming up 0. Rather than wait, we then issued a - 3:00 time adjustment and, within 1 10-minute cycle, it was in sync and stayed that way. Maybe our experience will help someone else.

This discussion is closed to new replies.