On Thu, Nov 20, 2003 at 11:04:49PM -0500, Kwan Lowe wrote:
> > At work, when I issue the same command from a client to the LAN's
> > timeserver, I get a message to the effect that there is no legitimate
> > timeserver there. Oddly enough, I get the whole dialog back and forth
> > that you'd normally see from issuing an ntpdate -qd command, but it
> > still says the server isn't legitimate. I checked that the firewall on
> > the timeserver is letting things through (it is), and the OUTPUT chain
> > of iptables just lets things through. Even without the -q qualifier, my
> > client machine will not recognize the local timeserver, and the ntp.conf
> > file is virtually identical with the one on the website (except for
> > local IPs, netmasks and internet timeservers). And yes, the ntp daemon
> > is running and has been restarted several times.
> >
> > Anyone have any ideas why the local machine won't recognize the local
> > timeserver at work, but will at home?
>
> How about the firewall on the client machine? It will also need the ntp
> ports opened. Some distros will punch a hole explicitly, some won't. Can
> you try temporarily dropping the local firewall completely just to test?
>
None such on the client. No need. When you run ntpdate -d, you can see
what appears to be a dialog that happens between the server and client,
and at the end is the time difference between the two machines (implying
two-way communications). And yet the client says there is no
authoritative server on the server end.
Paul
-----------------------------------------------------------------------
This list is provided as an unmoderated internet service by Networked
Knowledge Systems (NKS). Views and opinions expressed in messages
posted are those of the author and do not necessarily reflect the
official policy or position of NKS or any of its employees.
This archive was generated by hypermail 2.1.3 : Fri Aug 01 2014 - 18:01:31 EDT