IBM Support

sftp connections fails with 'Failed to read binary packet data'

Troubleshooting


Problem

After upgrading from IBM Sterling Secure Proxy 3.4.1 to 3.4.3, incoming sftp connections fail with error 'Failed to read binary packet data'

Symptom

sftp client error:

debug1: kex: server->client aes192-cbc hmac-md5 none
debug1: kex: client->server aes192-cbc hmac-md5 none
debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<7680<8192) sent
debug1: got SSH2_MSG_KEX_DH_GEX_GROUP
debug2: bits set: 3105/6144
debug1: SSH2_MSG_KEX_DH_GEX_INIT sent
Received disconnect from 1,1,1,1: 2: Failed to read binary packet data!
Disconnected from 1.1.1.1
Connection closed

[{"Product":{"code":"SS6PNW","label":"IBM Sterling Secure Proxy"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Component":"--","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"3.4.3","Edition":"","Line of Business":{"code":"LOB77","label":"Automation Platform"}}]

Log InLog in to view more of this document

This document has the abstract of a technical article that is available to authorized users once you have logged on. Please use Log in button above to access the full document. After log in, if you do not have the right authorization for this document, there will be instructions on what to do next.

Document Information

Modified date:
17 December 2019

UID

swg21990670