SSH won't execute shell
From: WEC IT Services (UK) (lists-it_at_uk.wec-int.org)
Date: 08/31/04
- Previous message: Olaf Hoyer: "openssh v1 (protocol 1 ) deprecated /official statement anywhere?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Tue, 31 Aug 2004 12:31:22 +0100 To: SSH Mailing List <secureshell@securityfocus.com>
I am trying to access a remote IPCop box (and also a SME box behind it (SME is a
customised Redhat distribution)). I seem to be able to log on (according to the
log) to IPCop and SME, but it won't execute the shell, in either situtation, and
then terminates with: "Network error: Software caused connection abort". However
the people on the remote site can logon to the same accounts without any problems.
I have tried to force SSH1 as well as SSH2, the tail of the logs are attached.
I am wondering if the ADSL Routers do have something to do with this, but I
cannot find what. Can anyone shed any light on this, or give me any ideas what
to do?
Thank you very much,
Kees Vonk
Setup:
======
Local site:
WinXP --- IPCop --- IPCop --- Netgear ADSL Router (DG834) --- internet
Remote site:
SME --- IPCop -- Dlink ADSL Router (DSL502T) --- internet
I am using PuTTY 0.54 on my XP machine.
All IPCop boxes are 1.3 patched upto patch 9.
IPCop uses SSH-1.99-OpenSSH_3.1p1
SME uses SSH-1.99-OpenSSH_3.7.1p1
SSH1 log tail:
==============
Event Log: Sent password
Incoming packet type 14 / 0x0e (SSH1_SMSG_SUCCESS)
Event Log: Authentication successful
Outgoing packet type 10 / 0x0a (SSH1_CMSG_REQUEST_PTY)
00000000 00 00 00 05 78 74 65 72 6d 00 00 00 18 00 00 00 ....xterm.......
00000010 50 00 00 00 00 00 00 00 00 00 P.........
Incoming packet type 14 / 0x0e (SSH1_SMSG_SUCCESS)
Event Log: Allocated pty
Outgoing packet type 12 / 0x0c (SSH1_CMSG_EXEC_SHELL)
Event Log: Started session
Event Log: Network error: Software caused connection abort
SSH2 log tail:
==============
Event Log: Sent password
Incoming packet type 52 / 0x34 (SSH2_MSG_USERAUTH_SUCCESS)
Event Log: Access granted
Outgoing packet type 90 / 0x5a (SSH2_MSG_CHANNEL_OPEN)
00000000 00 00 00 07 73 65 73 73 69 6f 6e 00 00 01 00 00 ....session.....
00000010 00 40 00 00 00 40 00 .@...@.
Incoming packet type 91 / 0x5b (SSH2_MSG_CHANNEL_OPEN_CONFIRMATION)
00000000 00 00 01 00 00 00 00 00 00 00 00 00 00 00 80 00 ................
Event Log: Opened channel for session
Outgoing packet type 98 / 0x62 (SSH2_MSG_CHANNEL_REQUEST)
00000000 00 00 00 00 00 00 00 07 70 74 79 2d 72 65 71 01 ........pty-req.
00000010 00 00 00 05 78 74 65 72 6d 00 00 00 50 00 00 00 ....xterm...P...
00000020 18 00 00 00 00 00 00 00 00 00 00 00 01 00 ..............
Incoming packet type 99 / 0x63 (SSH2_MSG_CHANNEL_SUCCESS)
00000000 00 00 01 00 ....
Event Log: Allocated pty
Outgoing packet type 98 / 0x62 (SSH2_MSG_CHANNEL_REQUEST)
00000000 00 00 00 00 00 00 00 05 73 68 65 6c 6c 01 ........shell.
Event Log: Network error: Software caused connection abort
- Previous message: Olaf Hoyer: "openssh v1 (protocol 1 ) deprecated /official statement anywhere?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
