On Mon, Nov 17, 2003 at 10:15:01PM -0500, Kwan Lowe wrote:
>
> > I have a machine at work which is periodically connected to the internet
> > via dial-up. One of its functions when it comes up is to check the
> > internet timeservers and reset its system clock. I'd like to use this
> > machine as a reference clock for the other machines on the lan, perhaps
> > having them query it once a day to reset their clocks. Otherwise, the
> > system clocks seem to slip quite a bit.
> >
> > My question is: what program (hopefully one that comes with Debian) can
> > be run as a daemon on the server to make it appear to be a time server
> > to the rest of the lan? Note: I don't need a program that _asks_ what
> > the time is. ntp and ntpdate do that. I need a program that will _serve_
> > up the time to other machines on the lan. Any takers?
> >
>
> ntpd is the server portion. In some older distros it may be called xntpd.
> Configuration info can be found here:
>
> http://www.siliconvalleyccie.com/linux-hn/ntp.htm
>
> If you install the standard ntp package the ntpd should be part of it. It
> should also install some extensive docs in html format.
Well, this works per the website at home, but not at work. At home, I
get a proper response from ntpdate -qd rocky, where rocky is the local
time server being syncronized with the internet timeservers.
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?
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 - 17:58:21 EDT