After reading further, we've retired ntpdate from this network. Our issue may have been the order in which we ran ntpdate and xntpd within /etc/rc.conf ; subsequently (post reboot) immediately trying to run 'ntpdate xxx.xxx.x.x' would fail (as we posted on http://188.8.131.52/freebsd/ntpd/ntpd_issue-1.txt).
We're not going to break it again in order to find out what went wrong. We are now 'ntpdate' *free*. We invite any and everyone else to do the same -- voluntarily retire 'ntpdate'. Thanks for your feedback. ----- Original Message ----- From: "Lowell Gilbert" <[EMAIL PROTECTED]> To: "nw1" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Thursday, October 09, 2003 8:52 AM Subject: Re: 4.8-RELEASE-p13 -and- ntpd > "nw1" <[EMAIL PROTECTED]> writes: > > > Our ntpd host syncs with the external public servers, but our local clients, using ntpdate > > to sync with the ntpd host (on the same sub-net), fails. Using ntpdate from the > > same > > local clients to any external public time-server works without problems. > > > > The details are posted at: http://184.108.40.206/freebsd/ntpd/ntpd_issue-1.txt > > I don't see anyting wrong there. > > The next step is to see whether the packets are hitting the wire, and > whether responses get back. You'll need to sniff the link. > _______________________________________________ > [EMAIL PROTECTED] mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > _______________________________________________ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"