Date: Mon, 5 May 1997 10:42:45 -0500 From: Dan Nelson <dnelson@emsphone.com> To: Brandon Gillespie <brandon@cold.org> Cc: questions@FreeBSD.ORG Subject: Re: 'ntpdate' time server Message-ID: <19970505104245.08667@dan.emsphone.com> In-Reply-To: <Pine.NEB.3.95.970505090555.8080A-100000@cold.org>; from "Brandon Gillespie" on Mon, May 05, 1997 at 09:08:15AM -0600 References: <19970505002129.62030@dan.emsphone.com> <Pine.NEB.3.95.970505090555.8080A-100000@cold.org>
next in thread | previous in thread | raw e-mail | index | archive | help
In the last episode (May 5), Brandon Gillespie said: > Well, I tried that, and it didn't work (even from two boxes on the > same network), so I'm assuming I didn't configure xntpd right. > Basically, I had it configured and running on Box A, on the same > network as Box B (both FreeBSD), but running ntpdate on Box B and > pointing it to Box A just errors out with 'no server suitable for > synchronization found' even though xntpd is running on that box (if > you try and run ntpdate on the box while xntpd is running it whines > about an ntp server already running). I just tested this, and ntpdate will not synch to an xntpd that was just started (i.e. one that has not synchronized itself yet). Run "ntpq -c peers box-a". If none of the servers has a "*" next to it, xntpd doesn't trust any of its servers yet. It takes about 5 minutes for xntpd to pick a server to synch to. If xntpd on box-a is running and is synched to another server, then you should look at the connection between box-a and box-b. Try running (on box-b) "ntpdate -d box-a" and see if packets are being exchanged. -Dan Nelson dnelson@emsphone.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19970505104245.08667>