Archived Forum Post

Index of archived forum posts

Question:

Unable to agree upon server-to-client compression algorithm.

Dec 19 '12 at 07:53

Hello Folks, I am trying to connect to one of the SFTP server using the chilkatnet2.0 component but I am getting the following error Connect_SFtp: DllDate: Aug 5 2012 Username: GR-IT-01:web Architecture: Little Endian; 32-bit Language: .NET 2.0 VerboseLogging: 0 SftpVersion: 0 hostname: nft.sftp.tesco.biz port: 22 ConnectTimeoutMs_1: 5000 calling ConnectSocket2 IPV6 enabled connect with NO heartbeat. connectingTo: nft.sftp.tesco.biz dnsCacheLookup: nft.sftp.tesco.biz Resolving domain name (IPV4) GetHostByNameHB_ipv4: Elapsed time: 31 millisec myIP_1: 192.168.5.155 myPort_1: 3512 connect successful (1) Established TCP/IP connection with SSH server clientIdentifier: SSH-2.0-PuTTY_Local:_May_11_2009_17:22:38 Sending client identifier... Done sending client identifier. Reading server version... initialDataFromSshServer: SSH-2.0-JSCAPE

serverVersion: SSH-2.0-JSCAPE
KeyExchangeAlgs:
  algorithm: diffie-hellman-group1-sha1
--KeyExchangeAlgs
HostKeyAlgs:
  algorithm: ssh-rsa
--HostKeyAlgs
EncCS:
  algorithm: blowfish-cbc
  algorithm: 3des-cbc
--EncCS
EncSC:
  algorithm: blowfish-cbc
  algorithm: 3des-cbc
--EncSC
MacCS:
  algorithm: hmac-sha1
  algorithm: hmac-md5
--MacCS
MacSC:
  algorithm: hmac-sha1
  algorithm: hmac-md5
--MacSC
CompCS:
  algorithm: zlib
--CompCS
CompSC:
  algorithm: zlib
--CompSC
Encryption: Blowfish
Encryption: Blowfish
MAC: HMAC-SHA1
MAC: HMAC-SHA1
Unable to agree upon server-to-client compression algorithm.
Unable to agree upon client-to-server compression algorithm.
Key Exchange: DH Group 1
Host Key Algorithm: RSA
numBits: 128
pbits: 1024
Using Oakley Group 2.
Sent e to server.
Unexpected message received.
expected: 31
msgType: 1
Failed.

--Connect_SFtp Please can someone advise? Thanks


Answer

Unfortunately, Chilkat v9.4.0 does not implement compression for the transport. This should be implemented by v9.4.2.

According to the SSH Protocol standard (RFC 4253), the following compression methods are defined:

      none     REQUIRED        no compression
      zlib     OPTIONAL        ZLIB (LZ77) compression
The standard states that a server is REQUIRED to accept the "no compression" option. A server that is configured otherwise should expect problems such as what you've encountered.


Answer

Hmm.. please can you advise by when we should be able to download the v9.4.2 ? Thanks for your reply.


Answer

Hmm.. please can you advise by when we should be able to download the v9.4.2 ? Thanks for your reply.


Answer

Maybe 3 months from now...