M. Giertzsch wrote: > The servers configuration is: > restrict default notrap nomodify nopeer noquery ---------------------------------------------^^^^^^^ > restrict 127.0.0.1 > driftfile /var/status/ntp.drift > pidfile /var/run/ntpd.pid > server 127.127.1.1 > fudge 127.127.1.1 stratum 7
Isn't the lack of any other restrict statements going to disallow query from the clients? > The clients configuration is: > restrict default notrap nomodify nopeer noquery > restrict 127.0.0.1 > driftfile /var/status/ntp.drift > pidfile /var/run/ntpd.pid > server 10.9.94.165 iburst > server 127.127.1.1 > fudge 127.127.1.1 stratum 13 > > > To run into the problem that the client is not syncing to the server I > --> stopped the NTP service on both client and server > --> changed the time on the client back to january of 1975 That is a big jump, (you only get that chance once before panic with ntpd -g), some embedded systems use a hard coded min date, or check the date / times stamps on some files, and if the clock does not appear to be set, set to that discovered date / time, before running NTPd -g. > --> started the NTP service on the client > --> started the NTP service on the server a little later -- E-Mail Sent to this address <blackl...@anitech-systems.com> will be added to the BlackLists. _______________________________________________ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
