Problem using PuTTY and Dropbear for port forwarding (ssh tunneling)

Hi all,

I'm trying to do the following:
I have a couple of 'client' pc's that are behind routers. I want to be
able to connect to them (using VNC) from anywhere when needed without
having to open up ports on the routers.
My plan is to let those clients set up and keep open an SSH connection
to a server on the Internet that I have access to (running Dropbear as
an SSH server).
The clients I want to take over, are running a startup script creating
the connection and keeping it open. Over the connection, a tunnel is
then created from client port X, to server port Y. From my PC I then
create an SSH connection to the server and create a tunnel from PC
port Z to server port Y.

I'm currently testing this setup using two Windows pc's and a Linux
server (running Dropbear) in my own network, and using PuTTY. One pc
(A) is running ultra VNC. The other PC (B) is running the vnc viewer.
I use PuTTY to create an SSH connection from PC A to the server and
create a *remote* forward from server port X to PC A, port 5900 (this
is where ultra VNC is listening).
Then, I use PuTTY to create an SSH connection from PC B to the server
and create a *local* forward from PC B, port 5900 to server port X.

Then, I fire up Ultra VNC viewer on PC B and connect it to '<ip
address PC B>::5900'.
Now, I'm getting a connection error, saying something about a protocol
error.

I can connect directly from PC B to PC A fine ('<ip address PC A>::
5900').

Does anyone have a clue about what I'm doing wrong or forgot to do?

Kind regards!
.

Relevant Pages

  • Re: Unable to print to networked printer - get access denied messa
    ... Check the permissions on the server assuming the client has a true RPC ... How is the Standard TCP/IP port configured for the device? ...
    (microsoft.public.windowsxp.print_fax)
  • 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: Remote Connection Issue
    ... through port number 3389 and a workstation on the LAN through port number ... I understand that you want to allow a LAN client ... and you have configured server publishing rule ... > By default Terminal Server and Windows 2000 Terminal Services uses TCP ...
    (microsoft.public.windows.server.sbs)
  • Re: RealVNC
    ... Default listening port for RealVNC server that runs on the machine on which ... Then there is default Java listening port on port 5800 on the client machine ...
    (microsoft.public.windows.server.sbs)
  • Re: Redirecting data sent to a local printer to another host and port on the network
    ... All client workstations have access to the ... simply redirecting netcat traffic on port 9100 to port 515 on ... Only LPR clients talk to LPD print server daemons. ... >workstation at the branch site where the print job originated. ...
    (comp.unix.sco.misc)
Quantcast