Failed to create a transport component

Need help with FileZilla Client? Something does not work as expected? In this forum you may find an answer.

Moderator: Project members

Post Reply
Message
Author
MattO
500 Command not understood
Posts: 4
Joined: 2018-08-10 16:26
First name: MATT
Last name: OSTRANDER

Failed to create a transport component

#1 Post by MattO » 2018-08-10 16:33

Trying to setup a new SFTP connection and I get the following error:

Status: Connecting to -----------------...
Response: fzSftp started, protocol_version=8
Command: open "-----------@-------------" 22
Error: Server sent disconnect message
Error: type 2 (protocol error):
Error: "Failed to create a transport component! com/jcraft/jzlib/ZStream [java.lang.NoClassDefFoundError]"
Error: Could not connect to server

A SFTP connection to a different server is working OK.

I do not know the server type.

User avatar
botg
Site Admin
Posts: 35566
Joined: 2004-02-23 20:49
First name: Tim
Last name: Kosse

Re: Failed to create a transport component

#2 Post by botg » 2018-08-10 16:37

Something wrong with the server. Please contact your server administrator or server hosting provider for assistance.

MattO
500 Command not understood
Posts: 4
Joined: 2018-08-10 16:26
First name: MATT
Last name: OSTRANDER

Re: Failed to create a transport component

#3 Post by MattO » 2018-08-10 17:05

It works with another SFTP client (built into our operations system).

Tried WinSCP - it connected OK.
Listed this server and protocol information:
Session protocol SSH-2
SSH implementation Maverick_SSHD
Encryption algorithm aes
Compression No
File transfer protocol SFTP-4
The server supports these SFTP extensions: newline="\n"

User avatar
botg
Site Admin
Posts: 35566
Joined: 2004-02-23 20:49
First name: Tim
Last name: Kosse

Re: Failed to create a transport component

#4 Post by botg » 2018-08-10 18:18

Does your other client negotiate the same features?

MattO
500 Command not understood
Posts: 4
Joined: 2018-08-10 16:26
First name: MATT
Last name: OSTRANDER

Re: Failed to create a transport component

#5 Post by MattO » 2018-08-10 18:35

This is the log from that system:
TN[CommOut-1]<2018-08-10 09:50:55.102> <8> Using ssh_version: SSH-2.0-JSCH-0.1.28
TN[CommOut-1]<2018-08-10 09:50:55.102> <8> Using useknownhosts: true
TN[CommOut-1]<2018-08-10 09:50:55.102> <8> Using timeout: 0
TN[CommOut-1]<2018-08-10 09:50:55.102> <8> Using StrictHostKeyChecking: no
TN[Thread-28]<2018-08-10 09:50:55.102> <1> Connecting to ---server--- port 22
TN[Thread-28]<2018-08-10 09:50:55.149> <1> Connection established
TN[Thread-28]<2018-08-10 09:50:55.18> <1> Remote version string: SSH-2.0-Maverick_SSHD
TN[Thread-28]<2018-08-10 09:50:55.18> <1> Local version string: SSH-2.0-JSCH-0.1.28
TN[Thread-28]<2018-08-10 09:50:55.18> <1> CheckCiphers: aes256-ctr,aes192-ctr,aes128-ctr,aes256-cbc,aes192-cbc,aes128-cbc,3des-ctr,arcfour,arcfour128,arcfour256
TN[Thread-28]<2018-08-10 09:50:55.18> <1> CheckKexes: diffie-hellman-group14-sha1
TN[Thread-28]<2018-08-10 09:50:55.211> <1> SSH_MSG_KEXINIT sent
TN[Thread-28]<2018-08-10 09:50:55.211> <1> SSH_MSG_KEXINIT received
TN[Thread-28]<2018-08-10 09:50:55.211> <1> kex: server: diffie-hellman-group1-sha1,diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521
TN[Thread-28]<2018-08-10 09:50:55.211> <1> kex: server: ssh-dss,ssh-rsa
TN[Thread-28]<2018-08-10 09:50:55.211> <1> kex: server: aes256-ctr,aes192-ctr,aes128-ctr,aes256-cbc,aes192-cbc,aes128-cbc,aes256-gcm@openssh.com,aes128-gcm@openssh.com,blowfish-cbc,3des-cbc,arcfour256
TN[Thread-28]<2018-08-10 09:50:55.211> <1> kex: server: aes256-ctr,aes192-ctr,aes128-ctr,aes256-cbc,aes192-cbc,aes128-cbc,aes256-gcm@openssh.com,aes128-gcm@openssh.com,blowfish-cbc,3des-cbc,arcfour256
TN[Thread-28]<2018-08-10 09:50:55.211> <1> kex: server: hmac-sha2-512,hmac-sha2-256,hmac-sha1,hmac-sha1-96,hmac-md5,hmac-md5-96
TN[Thread-28]<2018-08-10 09:50:55.211> <1> kex: server: hmac-sha2-512,hmac-sha2-256,hmac-sha1,hmac-sha1-96,hmac-md5,hmac-md5-96
TN[Thread-28]<2018-08-10 09:50:55.211> <1> kex: server: none,zlib
TN[Thread-28]<2018-08-10 09:50:55.211> <1> kex: server: none,zlib
TN[Thread-28]<2018-08-10 09:50:55.211> <1> kex: server:
TN[Thread-28]<2018-08-10 09:50:55.211> <1> kex: server:
TN[Thread-28]<2018-08-10 09:50:55.211> <1> kex: client: diffie-hellman-group1-sha1,diffie-hellman-group14-sha1,diffie-hellman-group-exchange-sha1
TN[Thread-28]<2018-08-10 09:50:55.211> <1> kex: client: ssh-rsa,ssh-dss
TN[Thread-28]<2018-08-10 09:50:55.211> <1> kex: client: aes128-ctr,aes128-cbc,3des-ctr,3des-cbc,blowfish-cbc,aes192-cbc,aes256-cbc
TN[Thread-28]<2018-08-10 09:50:55.211> <1> kex: client: aes128-ctr,aes128-cbc,3des-ctr,3des-cbc,blowfish-cbc,aes192-cbc,aes256-cbc
TN[Thread-28]<2018-08-10 09:50:55.211> <1> kex: client: hmac-md5,hmac-sha1,hmac-sha2-256,hmac-sha1-96,hmac-md5-96
TN[Thread-28]<2018-08-10 09:50:55.211> <1> kex: client: hmac-md5,hmac-sha1,hmac-sha2-256,hmac-sha1-96,hmac-md5-96
TN[Thread-28]<2018-08-10 09:50:55.211> <1> kex: client: none
TN[Thread-28]<2018-08-10 09:50:55.211> <1> kex: client: none
TN[Thread-28]<2018-08-10 09:50:55.211> <1> kex: client:
TN[Thread-28]<2018-08-10 09:50:55.211> <1> kex: client:
TN[Thread-28]<2018-08-10 09:50:55.211> <1> kex: server->client aes128-ctr hmac-md5 none
TN[Thread-28]<2018-08-10 09:50:55.211> <1> kex: client->server aes128-ctr hmac-md5 none
TN[Thread-28]<2018-08-10 09:50:55.211> <1> SSH_MSG_KEXDH_INIT sent
TN[Thread-28]<2018-08-10 09:50:55.211> <1> expecting SSH_MSG_KEXDH_REPLY
TN[Thread-28]<2018-08-10 09:50:55.258> <1> ssh_rsa_verify: signature true
TN[Thread-28]<2018-08-10 09:50:55.258> <1> Host ---server--- is known and mathces the RSA host key
TN[Thread-28]<2018-08-10 09:50:55.258> <1> SSH_MSG_NEWKEYS sent
TN[Thread-28]<2018-08-10 09:50:55.258> <1> SSH_MSG_NEWKEYS received
TN[Thread-28]<2018-08-10 09:50:55.258> <1> SSH_MSG_SERVICE_REQUEST sent
TN[Thread-28]<2018-08-10 09:50:55.29> <1> SSH_MSG_SERVICE_ACCEPT received
TN[Thread-28]<2018-08-10 09:50:55.336> <1> Authentications that can continue: publickey,keyboard-interactive,password
TN[Thread-28]<2018-08-10 09:50:55.336> <1> Next authentication method: publickey
TN[Thread-28]<2018-08-10 09:50:55.336> <1> Authentications that can continue: keyboard-interactive,password
TN[Thread-28]<2018-08-10 09:50:55.336> <1> Next authentication method: keyboard-interactive
TN[Thread-28]<2018-08-10 09:50:55.415> <1> Authentication succeeded (keyboard-interactive).
TN[CommOut-1]<2018-08-10 09:50:55.602> <1> END PROCESSING OUTBOUND MESSAGE

User avatar
botg
Site Admin
Posts: 35566
Joined: 2004-02-23 20:49
First name: Tim
Last name: Kosse

Re: Failed to create a transport component

#6 Post by botg » 2018-08-10 19:35

What about server-side logs?

MattO
500 Command not understood
Posts: 4
Joined: 2018-08-10 16:26
First name: MATT
Last name: OSTRANDER

Re: Failed to create a transport component

#7 Post by MattO » 2018-08-10 19:38

Not my server.
Since it does work withing our operations software, it not likely that we will get any help from them.

User avatar
botg
Site Admin
Posts: 35566
Joined: 2004-02-23 20:49
First name: Tim
Last name: Kosse

Re: Failed to create a transport component

#8 Post by botg » 2018-08-10 20:48

All I know is that it's a server-side issue. The server itself says it's a server-side issue.

Post Reply