A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.

0 votes
asked Oct 13, 2011 by IgorJ (200 points)
edited Jul 4, 2012

Could you please also comment this exception? The strange thing is that the exception will be thrown exactly after 10 Seconds. The error occurs only on several Windows 7 x64 computers and not always but only time to time. Thanks in advance.

2011-10-13 12:39:59.545 ERROR Sftp(1) Info: Rebex.Net.ProxySocketException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. ---> Rebex.Net.ProxySocketException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. ---> System.Net.Sockets.SocketException: Ein Verbindungsversuch ist fehlgeschlagen, da die Gegenstelle nach einer bestimmten Zeitspanne nicht richtig reagiert hat, oder die hergestellte Verbindung war fehlerhaft, da der verbundene Host nicht reagiert hat 192.168.6.33:22
   bei System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
   bei System.Net.Sockets.Socket.Connect(EndPoint remoteEP)
   bei wWGvS.BnRMAeZ.kRCyw(String , IPAddress , Int32 )
   --- Ende der internen Ausnahmestapelüberwachung ---
   bei wWGvS.BnRMAeZ.kRCyw(String , IPAddress , Int32 )
   --- Ende der internen Ausnahmestapelüberwachung ---
   bei wWGvS.BnRMAeZ.YqGDG(IAsyncResult , String )
   bei wWGvS.BnRMAeZ.cCoahHZ(IAsyncResult , Int32 )
   bei Rebex.Net.ProxySocket.Connect(String serverName, Int32 serverPort)
   bei Rebex.Net.Sftp.Connect(String serverName, Int32 serverPort, SshParameters parameters)

1 Answer

0 votes
answered Oct 14, 2011 by Lukas Pokorny (95,290 points)
edited Jul 4, 2012

This exception is thrown when the a connection attempt times out at the TCP stack level. Check out its entry at WinSock Error Reference page for possible reasons and suggestions.

Additionally, you might want to check the answer to another forum post that explains why this times out sooner than specified by Sftp object's Timeout value.

...