# ntpdate pool.ntp.org 2 Mar 23:10:23 ntpdate: no server suitable for synchronization foundShoot. What now? The cause would seem to be that the timeout is set too low. Quoting from the ntpdate manpage:
The [timeout] value is is rounded to a multiple of 0.2 seconds. The default is 1 second, a value suitable for polling across a LAN.Bingo! As the Internet is no LAN, timeout is to be expected. The solution: extend the timeout value to, say, four seconds:
# ntpdate -t 4 pool.ntp.org 2 Mar 23:16:08 ntpdate: adjust time server 220.127.116.11 offset 0.236161 secWish all IT-related problems were this simple.