Ntpdate and ntptrace are over TCP connections.
Normal ntpd traffic is over UDP connections, I believe.
Check your firewall.
Run ntpdc and enter dmpeer
>dmpeer
remote local st poll reach delay offset disp
=======================================================================
.adsl-65-70-149- 65.70.149.211 3 1024 377 0.00063 0.002982 0.01868
*adsl-65-70-149- 65.70.149.211 2 1024 377 0.00192 0.000956 0.01485
should show you the some server connect info
reach is octal 8 bits which represent connection over the last 8 attempts,
i.e., 377 means connected all eight times, 003 means just connected last two
times, etc.
send the dmpeer output, and I'll try to give you a hand...
-Jeff
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Cc: [EMAIL PROTECTED]
Subject: Re: ntpd not keeping time
# ntptrace clock.psu.edu
otc2.psu.edu: stratum 2, offset -529.277338, synch distance 0.06970
ntptrace (and ntpdate) work fine, but ntpd still doesn't sync time. I
previously had a very restrictive firewall ruleset on the box, but I've
relaxed it quite a bit and still nothing. :(
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
