First, you can probably get the window back if you type ~. to kill the ssh
session. The only commands that seem to respond when this happens are the ~
ones.
Anyway, the error is the same one OpenSSH gets when a rekey request comes in
from the server. I discovered this when a client who uses OpenSSH (v2.3.0) was
connecting to a server that got upgraded to ssh.com's v2.3.0. Seems the default
for the ssh.com ssh2 server is to force a rekey every 1 hour. It was fixed when
the server was reconfiged to not force a rekey (RekeyIntervalSeconds 0).
Clients could still request it, but the server wouldn't force it. This is
needed since OpenSSH and some other ssh clients don't support rekeys or support
them improperly (info in ssh.com's ssh2d man page).
So, did the server get upgraded and not restarted? Maybe it then started the
newer version when the machine came back up.
Anyway, I hope this helps since you didn't give any info on what ssh client and
protocol you were using or ssh server version/protocol you were connecting to.
--Dave
>Date: Fri, 12 Jan 2001 09:55:14 -0600
>From: Ben Ricker <[EMAIL PROTECTED]>
>User-Agent: Mozilla/5.0 (X11; U; Linux 2.2.16-22 i686; en-US; m18)
Gecko/20001107 Netscape6/6.0
>X-Accept-Language: en
>MIME-Version: 1.0
>CC: [EMAIL PROTECTED]
>Subject: Weird error - SSH? version)
>Content-Transfer-Encoding: 7bit
>
>I use slogin to login to a box. I use it merrily for a while and then I
>get the following message:
>
>Hm, dispatch protocol error: type 20 plen 136
>
>Is this an SSH problem? An sshd problem? Something else?
>
>The connection is fragged. I must close the terminal window and start
>another terminal up. When I try to log in again, it works perfectly
>fine. I noticed this problem only after we had a server crash due to the
>/dev/procs/file-max limit was reached. This may be related?
>
>Ben Ricker
>Senior Systems Admin
>Us-Rx, inc.
>
--
David Knight French
Black Mountain Computer Consulting
Voice: (858)279-4862
Email: [EMAIL PROTECTED]
