I’m wondering if anyone found a resolution for this issue? The Java client is baked into a software product called Brocade Network Advisor so I can’t change it, but I did upgrade it to the latest version 14.3.1 with no change. The client in question is identifying as the same Java SFTP client as the original poster. I hate to bring up this super old issue, but I’m having the same problem. :CONNECT – Channel Request: ‘subsystem’, Recipient Channel: 1104, Subsystem Name: ‘sftp’, Reply: true :CONNECT – Channel Request: ‘subsystem’, Recipient Channel: 1088, Subsystem Name: ‘sftp’, Reply: true : INFO – DH Key sizes: Server Public ‘1024’, Private ‘1023’, Client Public ‘1024’ :CONNECT – Disconnect reason: The user disconnected the application :CONNECT – Channel Request: ‘subsystem’, Recipient Channel: 1072, Subsystem Name: ‘sftp’, Reply: true :CONNECT – Channel Request: ‘subsystem’, Recipient Channel: 1056, Subsystem Name: ‘sftp’, Reply: true : SYSTEM – Channel Open: ‘session’, Sender Channel: 0, Init Window Size: 131070, Max Packet Size: 34000 :CONNECT – Native user ‘********’ authenticated : INFO – DH Key sizes: Server Public ‘1022’, Private ‘1023’, Client Public ‘1024’ :CONNECT – Incorrect password for user ‘********’ :CONNECT – Kex: ‘diffie-hellman-group1-sha1’ Host Key: ‘ssh-rsa’ C2S : ‘aes128-cbc, hmac-sha1, none’ S2C : ‘aes128-cbc, hmac-sha1, none’ :CONNECT – Key Exchange Algorithm Negotiation Success: Proceeding with key exchange :CONNECT – The client closed the connection :CONNECT – SSH FTP Connection request accepted from *.*.*.* :CONNECT – Incoming connection request on interface 18 at *.*.*.* What can I do to fix this? Can I roll back to 4.0.0.8? Is there a patch or setting that I’m missing? The same client connects to the 4.0.0.8 server and has no issues. I have used a small stand alone SFTP server to verify that the issue is with Cerberus and not the client. The client constantly connects and disconnects and is unable to transfer files. The client on the other end is an automated system so changing that is not an option. It seems like there is a client incompatibility. The second is v4.0.2.2 and we’re having trouble.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |