Harlan Stenn wrote: >>>> In article <[EMAIL PROTECTED]>, [EMAIL PROTECTED] (JCA) writes: > JCA> driftfile /etc/ntp/drift > JCA> multicastclient # listen on default 224.0.1.1 > JCA> broadcastdelay 0.008 >
Unless you know what you are doing here you should do this. > JCA> whereas when invoked from B, the command just hangs for a few seconds, > JCA> finally returning the following: > > JCA> localhost: timed out, nothing received ***Request timed out > > JCA> Can anybody give ideas so as to what is going here? Notice that I > JCA> can synchronize B with C by hand by issuing the ntpdate command in B. > > I would phrase it as you can set the time on B by running 'ntpdate C'. > > The timeout implies that ntpd is not running on B. Anything in the log? > No, that is not correct. You would get connection refused if it was not running. A timeout implies that something is bound to the port but not responding to queries on it. Danny _______________________________________________ questions mailing list [email protected] https://lists.ntp.isc.org/mailman/listinfo/questions
