Daniel Havey <[email protected]> wrote: > Did you mean between my testbed and ntp.aero.org/dns.aero.org (the servers in > my ntp.conf file)? There could be a firewall there but then I shouldn't be > able to do this: > [dha...@node0 ~]$ sudo ntpdate ntp.aero.org > 16 Sep 11:31:08 ntpdate[13121]: adjust time server 130.221.24.100 offset > 0.017606 sec > > I don't think it is a firewall issue.
When you do "ntpdate" it sends from a high port number to port 123 on the timeserver, and the timeserver replies from port 123 to your high port number. When you use "ntpd" it sends from port 123 to port 123 on your timeserver, which replies back to port 123. When your firewall or some other firewall in your network blocks traffic to port 123 or to all low portnumbers, you will find that ntpdate works ok but ntpd won't. _______________________________________________ questions mailing list [email protected] http://lists.ntp.org/listinfo/questions
