On Oct 17, 2006, at 3:25 PM, Roberto C. Sanchez wrote:
On Mon, Oct 16, 2006 at 08:02:12PM -0300, Henrique de Moraes Holschuh wrote:Do you mean to add them as servers that each queries. So, on server1, IAny NTP drift above half a second means something is completely broken, so *none* of your client machines are working fine. The two servers seem to work right. Make sure to also configure the two servers to *peer* eachother, btw.would put server2 as one of its servers and vice versa?
Not exactly... Let your two servers be "s1" and "s2". On "s1", replace "server s2" in the ntp.conf file, with "peer s2". And vice versa, in server "s2" put "peer s1".
That will cause each of them to treat each other symmetrically as coequals.
The details are all in /usr/share/doc/ntp-doc/html/ . In particular, look in "assoc.htl#symact" for a discussion of the difference between "peer" and "server".
Are your NTP servers configured to allow the other client machines (the two desktops and the laptop) to establish a client relationship with them? Whatdoes ntpq -p outputs on the client machines?$ ntpq -premote refid st t when poll reach delay offset jitter ====================================================================== ======== yauco.connexer. .INIT. 16 u - 1024 0 0.000 0.000 4000.00 maracaibo.conne .INIT. 16 u - 1024 0 0.000 0.000 4000.00Those are my two ntp server.
Your clients are not connecting with your servers. The "reach" column is an 8-bit map with a 1 bit for each successful transaction with that server (or peer), and a 0 bit for each unsuccessful attempt at a transaction. So "reach=0" means that the client has not yet succeeded in getting an answer from the server in the last eight trys. Do you have any "restrict" lines in your ntp.conf files (client or server)? If you do, make sure they are doing what you want them to do.
The details are all in /usr/share/doc/ntp-doc/html/ . In particular, read "accopt.html" for explanation of access control options.
Rick