also sprach Rick Francis (on Wed, 17 Jan 2001 06:33:51PM -0600):
had this same error message...resolved by having to re-add the udp 123 port allowance in the routers acl. ntp requires both tcp and udp on port 123.
i had udp only in the first place so now i added tcp for 123 as well, but that does not solve the problem. check out the debug output: root@fishbowl:/home/madduck # ntpdate -d albatross 19 Jan 00:46:58 ntpdate[12420]: ntpdate 4.0.99f Sat Jul 29 13:00:15 GMT 2000 (1) transmit(192.168.14.1) receive(192.168.14.1) transmit(192.168.14.1) receive(192.168.14.1) transmit(192.168.14.1) receive(192.168.14.1) transmit(192.168.14.1) receive(192.168.14.1) transmit(192.168.14.1) server 192.168.14.1, port 123 stratum 16, precision -17, leap 11, trust 000 refid [0.0.0.0], delay 0.02615, dispersion 0.00000 transmitted 4, in filter 4 reference time: 00000000.00000000 Thu, Feb 7 2036 7:28:16.000 originate timestamp: be11fe8f.b33c8000 Fri, Jan 19 2001 0:45:19.700 transmit timestamp: be11fef2.81275ee9 Fri, Jan 19 2001 0:46:58.504 filter delay: 0.02628 0.02617 0.02615 0.02615 0.00000 0.00000 0.00000 0.00000 filter offset: -98.8046 -98.8047 -98.8047 -98.8047 0.000000 0.000000 0.000000 0.000000 delay 0.02615, dispersion 0.00000 offset -98.804723 19 Jan 00:46:58 ntpdate[12420]: no server suitable for synchronization found root@fishbowl:/home/madduck # [greetings from the heart of the sun]# echo madduck@!#:1:s@\@@@.net -- "i believe that the moment is near when by a procedure of active paranoiac thought, it will be possible to systematize confusion and contribute to the total discrediting of the world of reality." -- salvador dali