Thank you Charles for the excellent lead!
I took your advice and did a "#netstat -ldp | more" and got the following lines concerning port 123 (with apologies for the formatting problems):
proto recv-Q send-Q local addr foreign addr state PID/Pgrm name
udp 0 0 192.168.1.254:123 0.0.0.0:*
1063/ntpd
udp 0 0 127.0.0.1:123 0.0.0.0:* 1063/ntpd
udp 0 0 0.0.0.0:123 0.0.0.0:* 1063/ntpd
Nothing is in the "state" column although 'LISTEN' appears with port 53, 1023, and 80.
I'm no expert but I get the idea that 'LISTEN'should have been in the 'state' column. I will start looking at the conf file and see if I missed something in the conf to enable the server function. http://groups.yahoo.com/group/wheelhorsegardentractors/links
Don't knock yourself out about the missing listen. UDP is a stateless protocol, so *NO* UDP entries in the netstat output will have anything in the "state" column. "States" only make sense for TCP.
It looks like your server is listening to the internal interface, and there are no firewall rules blocking any access from internal networks to the firewall itself, so unless you did something really wacky to the ipchains rules, that's not your problem either.
I'd make sure your windows client is actually talking NTP, rather than one of the other (typically simpler) time protocols.
-- Charles Steinkuehler [EMAIL PROTECTED]
-------------------------------------------------------
This SF.net email is sponsored by:Crypto Challenge is now open! Get cracking and register here for some mind boggling fun and the chance of winning an Apple iPod:
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en
------------------------------------------------------------------------
leaf-user mailing list: [EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-user
SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
