Greetings, Corinna Vinschen! > However, even with this fix, you might not get EHOSTUNREACH either. In > my testing, the error returned by the underlying Winsock getsockopt > function is not WSAEHOSTUNREACH, but WSAETIMEDOUT. This will be > translated into ETIMEDOUT == "Connection timed out".
To clarify, and what I think is important to understand, is that the "Host unreachable" error status could only be triggered by the parent router returning an explicit "not reachable" reply to a connection attempt. But since this reply is an ICMP message, many poorly configured intermediate routers, like home firewalls, could block it and you will get the WSATIMEDOUT for no apparent answer from the remote host in time. -- WBR, Andrey Repin (anrdae...@freemail.ru) 05.09.2011, <08:04> Sorry for my terrible english... -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
