Dew Wrobel wrote: > On Oct 5, 3:49 pm, Steve Kostecke <koste...@ntp.org> wrote: >> On 2009-10-05, Dew Wrobel <drew.wro...@gmail.com> wrote: >> >>> ntpq> pe >>> remote refid st t when poll reach delay offset jitter >>> ==================================================================== >>> ntp1.truetime.c .INIT. 16 u - 64 0 0.000 0.000 0.001 >>> zinc.ops.tns.it .INIT. 16 u - 64 0 0.000 0.000 0.001 >>> ntp2.usno.navy. .INIT. 16 u - 64 0 0.000 0.000 0.001 >> Are you using any restrict lines in your ntp.conf? If so, what are they? >> >> -- >> Steve Kostecke <koste...@ntp.org> >> NTP Public Services Project -http://support.ntp.org/ > > Not using any. > > Here is the /etc/ntp.conf being used: > > driftfile /drift/ntp.drift > > server 216.210.169.40 iburst > server 128.118.46.3 iburst > server 192.5.41.209 iburst > > I have the IP-addresses cause I wanted to rule out DNS resolution > being a problem.
What O/S? At least on BSD and Linux I've used, there is output to /var/log/messages if ntpd is having a problem. It's not a fatal problem otherwise ntpd would fail to start. I'm assuming you can make other external connections ok www, ftp etc? There are some tools with ntpd you can use, ntptrace etc. Does that work, can you traceroute to a remote server? David _______________________________________________ questions mailing list questions@lists.ntp.org https://lists.ntp.org/mailman/listinfo/questions
