[lug] ntp woes again

[Nate Duehr]

Look for firewall rules blocking the NTP port (123).  

Also try another site, like time-a.nist.gov or time-b.nist.gov (Stratum
1) or the numerous Stratum 2 sites... 

tcpdump may be handy or turning on iptables/ipchains drop logging...

Nate, nate at natetech.com

On Tue, 2002-04-23 at 22:34, Michael J. Hammel wrote:
> I installed the April KRUD edition today.  After putting all my firewall
> configs back in place I still can't get ntpdate to work.  I had this
> problem once before and ntpdate -u fixed it.  Now, even that doesn't work.
> 
> I run this command:
> 
> ntpdate ntp2.usno.navy.mil tock.usno.navy.mil tick.usno.navy.mil
> 
> and get back:
> 
> 23 Apr 23:33:20 ntpdate[3028]: no server suitable for synchronization found
> 
> There are no messages in the log files (/var/log/messages).  Is there a way
> to debug this?  Isn't ntpdate a preferred method for setting my system
> time?  If this is a firewall issue, shouldn't I be getting messages about
> rejected packets in /var/log/messages?
> -- 
> Michael J. Hammel                               The Graphics Muse 
> mjhammel at graphics-muse.org                      http://www.graphics-muse.com
> ------------------------------------------------------------------------------
> Technical writing requires as much imagination as fiction, since engineers
> often know less about what they've created than the writer. 
>     -- Michael J.  Hammel
> _______________________________________________
> Web Page:  http://lug.boulder.co.us
> Mailing List: http://lists.lug.boulder.co.us/mailman/listinfo/lug
> Join us on IRC: lug.boulder.co.us port=6667 channel=#colug
-- 
Nate Duehr, nate at natetech.com