SSH won't execute shell

From: IT Services (filtered_at_btopenworld.com)
Date: 08/24/04 

Date: Tue, 24 Aug 2004 16:02:33 +0100

I am trying to access a remote IPCop box (and also a SME box behind it). 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.

Can anyone shed any light on this?

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

Relevant Pages

  • SSH wont execute shell
    ... I am trying to access a remote IPCop box (and also a SME box behind it (SME is a ... the people on the remote site can logon to the same accounts without any problems. ... Event Log: Authentication successful ...
    (SSH)
  • Re: Cant read event logs on Win2003 server
    ... You do not have problems reading the event log, etc, when you log on to ... You have problems when you are on a remote machine and try to "manage" it. ... This posting is provided "AS IS" with no warranties, and confers no rights. ... > "Arch Willingham" wrote in message ...
    (microsoft.public.windows.server.security)
  • Re: Event ID: 4000
    ... Based on the text of your event log, it appears that DNS is working fine. ... The problem may happen when your server attempts to connect to the remote ...
    (microsoft.public.exchange2000.protocols)
  • Re: Vista Remote Event Log viewer
    ... The remote computer is un-available on the network. ... The Remote Event Log Management firewall exception has been NOT set on ... Log Management firewall" exception is enabled on the remote Vista machine ... On the remote Windows Vista machine, click Start, type: ...
    (microsoft.public.windows.server.general)
  • Re: writing to a remote event log.....
    ... and call my advice useless. ... >> Everybody who cross-posts has a reason for doing so. ... >>> But when I moved the COM+ component onto a remote application server I ... >>> Can anyone tell me how to cofig the event log so that the remote COM+ ...
    (microsoft.public.dotnet.languages.csharp)