[ntp:bugs] [Bug 591] NTPDATE fails to update with error: poll(): nfound = 0, error: Success

[bugzilla at ntp.isc.org]

http://bugs.ntp.isc.org/show_bug.cgi?id=591



----------------------------------------------------------------------------
Additional Comments From mayer at ntp.org (Danny Mayer)
Submitted on 2006-04-04 02:31
Sorry, but there is no way ntp is going to know why it timed out. For example,
the server could have just dropped the packet, the router could have routed the
packet to lala land. There are so many possibilities it's not something you can
expect ntp to know. One possibility is to try using ntpq to the server from the
client and see if it returns any data.

We'd need to look at your configurations and how they're set up. Have you done a
traceroute to clock.isc.org? Have you had these systems  point to a working NTP
server on your subnet and does that work?

These kinds of questions really belong in the newsgroup cptn or the questions
mailing list. I don't think that they really belong here since it it doesn't
seem to be a ntp issue.

Danny

-- 
Danny Mayer <mayer at ntp.org>



------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.