Connection Attempt failed when trying to connect to MFT
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 4.4k
- Forks
- 993
- Avg merge
- 9d 21h
- Merged PRs (30d)
- 1
Description
Hi Team,
We are receiving two errors at irregular intervals from SFTP Baseclient.connect method while connecting to MFT server:
"System.Net.Sockets.SocketException: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"
":Renci.SshNet.Common.SshConnectionException:InnerException:System.Net.Sockets.SocketException (0x80004005): An existing connection was forcibly closed by the remote host
at System.Net.Sockets.Socket.Receive(Byte[] buffer, Int32 offset, Int32 size, SocketFlags socketFlags)
at Renci.SshNet.Abstractions.SocketAbstraction.Read(Socket socket, Byte[] buffer, Int32 offset, Int32 size, TimeSpan timeout)
at Renci.SshNet.Session.TrySocketRead(Byte[] buffer, Int32 offset, Int32 length)
at Renci.SshNet.Session.ReceiveMessage()
at Renci.SshNet.Session.MessageListener():Message:An existing connection was forcibly closed by the remote host"
We have increased the Connection Timeout to 50 secs as well. using stable version: 2016.1.0
Please help to resolve the issues.
Thanks,
Haritha
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the SFTP Baseclient.connect path and trace the reported SocketException and SshConnectionException stack frames through the connection flow. Reproduce the intermittent failure against the MFT server with the 50-second timeout, then document a reliable cause and verify that the connection no longer fails unexpectedly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100