[ntp:questions] Unable to get time from NTP server

Daniel Rudy nospam at nospam.net
Thu Mar 31 19:37:22 UTC 2005


"Brad Knowles" <brad at stop.mail-abuse.org> wrote in message 
news:mailman.8.1112279236.588.questions at lists.ntp.isc.org...
> At 2:05 PM +0000 2005-03-31, Daniel Rudy wrote:
>
>>  /etc/ntp.conf
>>  server time.windows.com
>>  server clepsydra.dec.com
>>  server bitsy.mit.edu
>>  server otc1.psu.edu
>>  server time.xmission.com
>>  server clock.via.net
>>  server clock.isc.org
>>  server ntp2.sth.netnod.se
>>  server ntp2.sp.se
>>  server nist1.aol-ca.truetime.com minpoll 8
>>  server usno.pa-x.dec.com
>
> See 
> <http://ntp.isc.org/bin/view/Support/SelectingOffsiteNTPServers#Section_5.3.4.>. 
> Also make sure that you don't list any server for which you have not been 
> given explicit authorization to use, or which is on the lists at 
> <http://ntp.isc.org/bin/view/Servers/StratumTwoTimeServers> or 
> <http://ntp.isc.org/bin/view/Servers/StratumOneTimeServers> and specified 
> as "open access".
>
> You should also take a look at 
> <http://ntp.isc.org/bin/view/Servers/NTPPoolServers> and 
> <http://ntp.isc.org/bin/view/Support/SelectingOffsiteNTPServers#Section_5.3.7.>.
>
>
> Also, you probably want to be using "iburst" on all these server 
> definitions.  See <http://ntp.isc.org/bin/view/Support/StartingNTP4> for a 
> variety of other tips on how you can get NTP to start up quickly.
>
>>  restrict 192.168.0.0 mask 255.255.255.0 notrust nomodify notrap kod
>>  restrict 127.0.0.1 mask 255.0.0.0
>
> See <http://ntp.isc.org/bin/view/Support/ConfRestrict>.  The use of 
> "notrust" means that you're requiring all the connections to be 
> cryptographically authenticated, which is probably not what you meant.
>
> -- 
> Brad Knowles, <brad at stop.mail-abuse.org>
>
> "Those who would give up essential Liberty, to purchase a little
> temporary Safety, deserve neither Liberty nor Safety."
>
>     -- Benjamin Franklin (1706-1790), reply of the Pennsylvania
>     Assembly to the Governor, November 11, 1755
>
>   SAGE member since 1995.  See <http://www.sage.org/> for more info.

That worked.  I had a number of peers who's access policy had changed. 
Also, it seems that changing notrust to nopeer seems to have corrected the 
problem.  Thanks for your help.





More information about the questions mailing list