Re: fatal: mm_request_receive_expect error
- From: Leif Ericksen <lericksen@xxxxxxxxxxxxx>
- Date: Fri, 19 Oct 2007 22:01:24 -0500
If the only thing that changes was the destination client it is a GOOD
BET that your PIX is not culpable.
Now, what protocol of SSH is being used on the SSH client? Is it
forcing say protocol 2 while the destination server only talks protocol
1 or vice verse?
NOTE:
/etc/ssh/sshd_config
Port 22
Protocol 2
I am betting it is the Protocol and the client is not self adjusting.
--
Leif Ericksen
On Wed, 2007-10-17 at 13:24 -0500, Ryan McCain wrote:
We have a client that is coming through our PIX firewall (rules are set properly) and trying to SSH into our Linux box. We are using SLED 10 with openssh-4.2p1-18.25. He previously was able to SSH in until will rebuilt the server (hardware failure). Now when he tries login I get this error in /var/log/messages:
Oct 16 16:22:12 dss-cs99la07 sshd[16641]: fatal: mm_request_receive_expect: read: rtype 48 != type 46
..He is using a Windows SSH client. My first guess was he still had our old certificate but it prompts him to accept the new one and he does.
I have confirmed myself and others can SSH from outside the firewall so I'm pretty sure it's not a firewall issue.
Any ideas?
- Follow-Ups:
- Re: fatal: mm_request_receive_expect error
- From: Ryan McCain
- Re: fatal: mm_request_receive_expect error
- References:
- fatal: mm_request_receive_expect error
- From: Ryan McCain
- fatal: mm_request_receive_expect error
- Prev by Date: fatal: mm_request_receive_expect error
- Next by Date: CFP for HITBSecConf2008 - Dubai now open
- Previous by thread: fatal: mm_request_receive_expect error
- Next by thread: Re: fatal: mm_request_receive_expect error
- Index(es):
Relevant Pages
|