[ntp:questions] Re: ??-Ntp sets time to year 2036

David L. Mills mills at udel.edu
Tue Sep 16 15:47:53 UTC 2003


Steve,

As it says in rfc-1305, a NTP timestamp of all zeros simply means the
time has not yet been set or is unavailable. The fact this particular
value is interpreted as the epoch of the next NTP era instead of the
current one is an artifact of implementation and should be ignored.

Dave

swidmer wrote:
> 
> Ihave seen in some case that NTP can and will reset a computers time to the
> year 2036.  This seems to be the case when a machne senses a NTP time packet
> that contain the time 00000000.00000000.  This has seems to happen more
> often on machines listening for NTP time broadcasts, but it also happens to
> machines using SNTP TCP requests.
> 
> Has anyone else seen this happen before?  What can I do to avoid this
> situation while still using NTP?
> 
> Oh one other thing to note, this problem generally happens when a network
> segement can no longer talk or listen to signals from other NTP Servers.
> 
> Thanks,
> Steve



More information about the questions mailing list