[ntp:questions] Server and Client can't sync

Aggie c.kevin.lam at gmail.com
Tue Oct 30 23:50:02 UTC 2007

On Oct 30, 4:01 pm, da... at ex.djwhome.demon.co.uk.invalid (David
Woolley) wrote:
> In article <1193698184.474071.249... at i13g2000prf.googlegroups.com>,
> Aggie <c.kevin.... at gmail.com> wrote:
> >   To have NTPD run on VxWorks and Windows. Set VxWorks as the Server
> > couple minutes, the clock on Windows was changed to 5:15pm, Nov 21
> > 1988. I have no idea why it happened. So I looked at the timestamp
> > Reference clock update Time: Oct 29, 2007 15:17:57.08333 UTC
> > Originate Time Stamp: Oct 29, 2007 15:16:42.9551 UTC
> > Receive Time Stamp: Jan 1, 1970 00:21:26.0827 UTC
> > Transmit Time Stamp: Oct 29, 2007 15:20:30.1500 UTC
> I don't have the VxWorks knowledge (few if any on the newsgroup do) to
> understand why the receive and transmit timestamps are wildly different
> when you didn't change the clock between them, however, if you are really
> running ntpd on Windows, because the delay was huge and negative, it
> should not have stepped the time.  If it really is ntpd, maybe there is
> a bug in that it doesn't use the absolute magnitude of root distance to
> decide to reject a source.  A minus eighteen years delay really
> shouldn't be accepted!

But the weird thing is: NTPD will adjust the time on the client half
way between the server and 1970 Jan 1. For example, if the clock on my
server is in 2000, then the clock on the client will be set to 1985.
I have no idea what's going on. Any input would help.


More information about the questions mailing list