The window size, on the other hand, is larger when WinSCP is talking to the remote server, than when ST is trying to send files.Īre connecting to the exact same service, or are the sessions to a different ones? Can the remote server handle such packet size? What is the exact build of ST that you are running – please check $FILEDRIVEHOME/conf/versions.txt file for the exact string.Īlso, please note that Cerberus SFTP is not among the tested and supported SSH servers for Server Initiated Transfer in ST, so this might be an incompatibility issue. The same is the situation with the packet size – the one with the ST is double the value of the one with the WinSCP. What is seems is that the remote server provides one type of key when ST is talking to it, and another when WinSCP is talking to it. Thank you for contacting Axway Global Support.Īt first glance, not only the ciphers are different, but also a few other critical things: Can you tell me if Cerberus can handle the packet size sent by ST (Tumbleweed)? I can confirm both WinSCP and Tumbleweed connect to the same Cerbrus server in this case. I did contact Axway and they replied with the following. Sorry for the delay getting back on this. WinSCP – Kex: ‘diffie-hellman-group-exchange-sha1’ Host Key: ‘ssh-rsa’ C2S : ‘aes256-cbc, hmac-sha1, none’ S2C : ‘aes256-cbc, hmac-sha1, none’īut then I have seen other forum posts of log files with successful 3des-cbc connections.Īny ideas? Are there any know compatibility issues with Cerberus and Tumbleweed? Tumbleweed – Kex: ‘diffie-hellman-group1-sha1’ Host Key: ‘ssh-rsa’ C2S : ‘3des-cbc, hmac-md5, none’ S2C : ‘3des-cbc, hmac-md5, none’ The only obvious difference I can see is the Key Exchange : SYSTEM – Handle ‘/’ closedīoth are Tumbleweed and WinSCP servers are on the internal network so there should be no firewall issues. :COMMAND – Opening directory handle to ‘/’ :CONNECT – Channel Request: ‘subsystem’, Recipient Channel: 32, Subsystem Name: ‘sftp’, Reply: true :CONNECT – Channel Request: ‘ Recipient Channel: 32, Subsystem Name: ”, Reply: false :CONNECT – Channel Open: ‘session’, Sender Channel: 256, Init Window Size: 2147483647, Max Packet Size: 16384 : INFO – DH Key sizes: Server Public ‘2046’, Private ‘2047’, Client Public ‘2047’ :CONNECT – Kex: ‘diffie-hellman-group-exchange-sha1’ Host Key: ‘ssh-rsa’ C2S : ‘aes256-cbc, hmac-sha1, none’ S2C : ‘aes256-cbc, hmac-sha1, none’ : INFO – Client Identification: SSH-2.0-WinSCP_release_4.3.5 :CONNECT – SSH FTP connection request accepted from 10.11.50.65 :CONNECT – Connection timed out – Shutting down connection… :CONNECT – Channel Open: ‘session’, Sender Channel: 0, Init Window Size: 131072, Max Packet Size: 32768 :CONNECT – Native user ‘Test’ authenticated
:CONNECT – Authenticating password for user ‘Test’ : INFO – DH Key sizes: Server Public ‘1024’, Private ‘1023’, Client Public ‘1021’ :CONNECT – Kex: ‘diffie-hellman-group1-sha1’ Host Key: ‘ssh-rsa’ C2S : ‘3des-cbc, hmac-md5, none’ S2C : ‘3des-cbc, hmac-md5, none’ :CONNECT – Algorithm negotiation complete: Proceeding with key exchange : INFO – Client Identification: SSH-2.0-1.0 :CONNECT – SSH FTP connection request accepted from 10.4.110.10 :CONNECT – Incoming connection request on SSH interface 2 at 10.11.7.8 you’ll see that the connect times out after 2 mins I’ve configured Tumbleweed to pull from the Cerberus server but it just hangs showing “processing”.Ĭerberus SFTP log shows the following. I’m trying to connect to a Cerberus SFTP server on my local LAN via Tumbleweed/Axway secure transport server.