On 2005-11-10, Harlan Stenn <[EMAIL PROTECTED]> wrote: > You did not follow the instructions about "restrict" statements.
<snip: logging, drift file and stats> | # You do need to talk to an NTP server or two (or three). | server ntp.your-provider.example That server does not exist.... | server vega.cbk.poznan.pl | server info.cyf-kr.edu.pl | server ntp.certum.pl | server tick.fh-augsburg.de | server ntp.globe.cz If you append 'iburst' to each of your server lines ntpd will synchronize to one of your remote time servers in 15-30 seconds. Without 'iburst' you'll have to wait ~8 minutes. Your omission of iburst and the 'ntpq -p' billboard only showing a reach of 77 suggest that you didn't give ntpd enough time to synchronize. | restrict default kod notrap nomodify nopeer noquery | restrict 127.0.0.1 nomodify These restrictions are not blocking NTP packets from your remote time-servers. If you want to review your default restriction please see http://ntp.isc.org/Support/AccessRestrictions -- Steve Kostecke <[EMAIL PROTECTED]> NTP Public Services Project - http://ntp.isc.org/ _______________________________________________ questions mailing list [email protected] https://lists.ntp.isc.org/mailman/listinfo/questions
