Re: channel 3: open failed: connect failed: Connection refused

per@xxxxxxxxxxxx (Per Hedeland) writes:

In article <m2ir3sodwk.fsf@xxxxxxxxxxxxxxxxx> blueman
<NOSPAM@xxxxxxxxxx> writes:
I have done a lot of googling and have not been able to figure out
what the above error message means.

My specific situation is as follows:
Case 1: ssh from linux box to linux box
Screen1: Client> ssh Server -L 9546:127.0.0.1:9546

Screen2: Client> telnet 127.0.0.1 9546

Then on Screen1 (which is now ssh'd into the Server, I see the
following message:
channel 3: open failed: connect failed: Connection refused

There is nothing actually running on port 9546 of the
Server.

Which is exactly what the message is telling you. Your instructions to
ssh/sshd are: When I connect to the local port 9546, forward that
connection to the server and connect to port 9546 there. When you
actually do the connect, you are duly informed that the remote
connection failed because nothing was listening on that port on the
server. You can try e.g. 'telnet localhost 12345', i.e. connect to a
*local* port where nothing is listening - it will give the same
"Connection refused".

Case 2: Same as case 1 but using cygwin from a Windoze machine.
Here I don't get any problems.

Meaning what? You actually get connected to something at port 9546 on
the server even though there's nothing there (that would be quite a
feature)? Or you just don't get an appropriate error message (a bug)?


OK. I assume then the problem is that for some reason the cygwin ssh
client doesn't generate the right error message. I had assumed that
the error message was generated on the server side and therefore
didn't understand the different behavior.

So, presumably there is a problem with the cygwin implementation of
the ssh client???
.

Relevant Pages

  • Re: Still cant connect to RWW or OWA remotely
    ... it certainly appears to be something about the SBS configuration. ... Meridian.local Ethernet adapter Local Area Connection: ... Windows SMALL BUSINESS SERVER 2003 Windows IP Configuration ... 192.168.254.254) directly to a port on the router and then ...
    (microsoft.public.windows.server.sbs)
  • Re: Still cant connect to RWW or OWA remotely
    ... it certainly appears to be something about the SBS configuration. ... Meridian.local Ethernet adapter Local Area Connection: ... Windows SMALL BUSINESS SERVER 2003 Windows IP Configuration ... 192.168.254.254) directly to a port on the router and then ...
    (microsoft.public.windows.server.sbs)
  • RE: VBscript Error on SBS2k3
    ... DHCP Server turned of SonicWALL with VPN Pass through request for IP to ... the problem should be caused by the 4125 port. ... > | Accessories and Communications and Remote Desktop Connection? ... > | 2.In Internet Explorer on the workstation you are connecting from, ...
    (microsoft.public.windows.server.sbs)
  • Re: interfaces lo:1 lo:2 lo:3? (for remote ssh tunnels)
    ... That's the problem tunneling (port forwarding) solves. ... >>can't get past the client firewall. ... > I don't understand why the server would be making the ... server initiates another connection to the client -- in this ...
    (Debian-User)
  • Re: Can not access Web and FTP sites from Internet
    ... your IP Configuration on the Server is correctly. ... Connecting To 12.208.215.87...Could not open connection to the host, ... 1> From the result, we can see the telnet failed, which means the router ... does not forward Port 443 to SBS Server. ...
    (microsoft.public.windows.server.sbs)