• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1853
  • Last Modified:

Does anyone know the cause for ssh error "Warning: child process (/usr/local/bin/ssh2) exited with code 66."?

We're receiving the following error message after we successfully connect to the remote host via sftp and then attempt to get a file:

Disconnected; protocol error (Protocol error: packet too long: 40580.).
Warning: child process (/usr/local/bin/ssh2) exited with code 66.

We are able to pick up files from this site.  In this particular case, the, if it matters, file size we're attempting to pick up is 1760153 bytes.  Does anyone know what the above error might be caused by and how to resolve it?

Thanks in advance.
0
ts01206
Asked:
ts01206
  • 4
  • 3
1 Solution
 
woolmilkporcCommented:
Hi,
what are the ssh protocol versions configured in your sshd_config (server) and on the client side?
Make sure clients and server use the same version (1/2)
On the client side, you can try to force a protocol version by either issuing 'ssh -1 ...' or 'ssh -2 ...'
Which one works (if any)?
Take care that the working version is allowed on both sides ('Protocol' keyword in the config files)
wmp
0
 
ts01206Author Commented:
I'll find out on the versions.  In the meantime, if we're sftp'ing into the box, we can't specify ssh -1 or -2, correct?
0
 
woolmilkporcCommented:
Hi,
at least you can specify 'sftp -1' to force protocol version 1. '-2' is not possible, afaik.
And when you have sftp, you do have ssh, too. So you could try the 'ssh' part nevertheless (just to test).
wmp
 
0
Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

 
ts01206Author Commented:
Ok.  If we use sftp userid@server to connect with, how do you then specify ssh -1 or -2?  In this case, isn't ssh already in use once we connect?  ssh is called by sftp, right?  Also, if this matters, we have exchanged ssh keys and they are in place.
0
 
woolmilkporcCommented:
As I wrote above, try sftp -1 userid@server
0
 
ts01206Author Commented:
Ok.  Turns out there was an incompatible version of sftp running on the server we were connecting to.  A patch was applied to sftp and all is well again.  I do appreciate the responses I got from you, wollmilkporc.  Thanks for your help.
0
 
ts01206Author Commented:
Thanks again.
0
 
ReneCrozierCommented:
We are experiancing the same issue.  However, we have several applications using or calling different versions of OpenSSH and Tectia SSH.  How do you determine which one needs to be updated?
0

Featured Post

Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 4
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now