[ntp:questions] Re: ntpdate[7170]: no server suitable for synchronization found

Richard B. Gilbert rgilbert88 at comcast.net
Mon Sep 26 11:30:56 UTC 2005


Danny Mayer wrote:

> Muthu wrote:
>
>> It looks as if  192.168.0.25 is unsynchronized.   NTP does not allow 
>> you to ask any random machine for the time, machines selected as 
>> servers must KNOW what time it is.
>
>
> The server you are requesting time from must first itself be 
> synchronized before it responds with usable packets otherwise it's 
> just polluting the requestors with bad data. The best defense is to 
> use ntpd which will weed out those servers providing bad time.
>
>> You need to use a server that is synchronized, directly or indirectly 
>> to NIST or other National Standards Laboratory.
>
>
> That's an unwarranted assumption. NTP imposes no such requirement for 
> synchronization to any operating standards body.
>

NTP does not impose the requirement but if you want the correct UTC 
time, it's a requirement.  If you don't want the correct time, you can 
synch to your old tall case clock for all anybody cares.   It's 
generally easier to use a server that is synchronized to the NTP net or 
to a hardware reference clock.




More information about the questions mailing list