

"Connection refused" means that a connection attempt was rejected. The "connection refused" error is coming from the ssh server on when it tries to make the TCP connection to the target of the tunnel.

From there, the ssh server makes TCP connection to localhost port 8783 and relays data between the tunneled connection and the connection to target of the tunnel. When you connect to port 8783 on your local system, that connection is tunneled through your ssh link to the ssh server on. I think it might either be the virtual network card driver, or somebody rooted our ssh.įor the benefit of others who made a silly mistake like I did (one that isn't mentioned in other answers): Make sure your remote machine actually has a process listening on the port that you're trying to tunnel to! I haven't rebooted yet - perhaps somebody here can suggest other diagnostics. I tried restarting the ssh daemon to no avail. NetBSD host 5.1_STABLE NetBSD 5.1_STABLE (XEN3PAE_DOMU) #6: Fri Nov 4 16:56: i386 The remote host runs NetBSD: bash-4.2# uname -a I tried also with localhost:80 to connect to the (remote) web server, with identical results. The ssh debug says: debug1: Connection to port 7000 forwarding to localhost port 7000 requested.Ĭhannel 2: open failed: connect failed: Connection refusedĭebug1: channel 2: free: direct-tcpip: listening port 7000 for localhost port 7000, connect from 127.0.0.1 port 53954, nchannels 3 Then, in another shell: $ irssi -c localhost -p 7000 The symptoms concern ssh tunneling.įrom my laptop I launch: $ ssh -L 7000:localhost:7000 -N -v All of a sudden (read: without changing any parameters) my netbsd virtualmachine started acting oddly.
