EldoS | Feel safer!

Software components for data protection, secure storage and transfer

I have a problem with SSH or SFTP connection. Can you help? (page 1)

First | 1 | 2 | Last | All

Common SSH/SFTP problems and the ways of their resolution

There are a big number of SSH/SFTP servers available worldwide. Several platforms, dozens of vendors, hundreds of product versions. The complexity of SSH protocol leads to various interoperability issues between different products. Fortunately, most of such issues occurring between BizCrypto and third-party SSH software can be easily solved with proper adjustment of the component’s properties. The typical steps to be performed when the component does not do its job for you are considered below.

1.The goal of the very first step is identification of the reason that causes the component to fail. Most of the problems occurring during the conversation between client and server are reported to event log as errors or warnings. Please do the following to get the detailed execution trace in a file: (BizCrypto for BizTalk) set TraceMode property to Debug, TraceToEventLog to No, TraceToFile to Yes, and make TraceFilename point to the location you wish to have the trace in. (BizCrypto for MSSQL) Configure SSIS logging provider as described in the article. (BizCrypto for WWF) Add the FileTrace activity to the very start of your workflow, set its TraceLevelValue to Debug and make FilePath property point to the location you wish to have the trace in.

2.Once the log file is ready, let’s try to investigate the data it contains. Open the log file with some text viewer (Notepad is okay) and scroll to the very end of the log. It is likely that there will be one or several lines reporting certain negotiation problem. The problem can be reported explicitly (“Trusted keys file not found”) or indirectly via some error code (“SSH error 109”). The list of SSH/SFTP error codes along with the corresponding descriptions is available below:

SSH error codes (reported during negotiation process)
1The server has provided a non-conformant SSH identification line. Please re-check that you have specified the correct server port value (22 in most cases).
2The server does not support SSHv2
3-6, 11Rare protocol errors. If such error is reported, please follow the instructions described below (step 3).
7, 8The sets of the cryptographic algorithms supported by client and server do not intersect. Please follow the instructions described below (step 3).
102Failed to set up SFTP subsystem (no SFTP support on server?).
103Key exchange failed. Please follow the instructions described below (step 3).
105, 106Invalid MAC. Please follow the instructions described below (step 3).
109Failed to verify host key. Please re-check that the public key of the server is available at the location pointed to by the TrustedKeysFile property. You can also try setting TrustAllKeys to true for diagnostics purposes.
114, 115Client authentication failed. Please re-check that the provided username and password are correct (or that the private key is available and the key passphrase is correct in case of public key authentication).
SFTP error codes (reported for active SFTP connections)
2No such file
3Permission denied
4General failure
10No such path
11File already exists
12Write protect
14, 15No space available or quota exceeded
17Lock conflict
20Invalid filename
100Unsupported SFTP version
First | 1 | 2 | Last | All

Return to the list


Back to top

As of July 15, 2016 EldoS business operates as a division of /n software, inc. For more information, please read the announcement.

Got it!