[ntp:questions] [Q] Why do many time servers time out on queries from ntpq -p?

Maurice Volaski mvolaski at aecom.yu.edu
Wed Apr 9 18:59:43 UTC 2008


I've been trying the peers command in ntpq on a number of time 
servers and finding that for as many that do respond, there are about 
an equal number that do not. An example of a failing response is:

ntpq> host sundial.columbia.edu
current host set to hickory.cc.columbia.edu
ntpq> peers
hickory.cc.columbia.edu: timed out, nothing received
***Request timed out

I can reproduce identical successes and failures from 3 computers 
running different OSs on independent networks.

These I've tried work just fine:
timex.cs.columbia.edu
time.euro.apple.com
lain.ziaspace.com
ntp.nblug.org
ntp1.cs.wisc.edu
clock1.unc.edu

But these time out:
sundial.columbia.edu
time.apple.com
morose.quex.org
ntp.sycharlutheran.org
ntp.bytestacker.com
ntp1.kansas.net

All of the above were tested and gave the same results on
kennedy1.aecom.yu.edu (Linux with ntpq 4.2.4p4 at 1.1520-o)
fluxsoft.com (FreeBSD with ntpq 4.2.0-a)
ool-45766590.dyn.optonline.net (Mac OS X with ntpq 4.1.1 at .786)
-- 

Maurice Volaski, mvolaski at aecom.yu.edu
Computing Support, Rose F. Kennedy Center
Albert Einstein College of Medicine of Yeshiva University



More information about the questions mailing list