Tunnel with same listen and destination port



I'm trying to tunnel remote desktop to a machine on another network.
When I log into the SSH server(unix/linux), I can ping the windows
machine successfully from that machine I am SSH'd into. So in my SSH
client I have set it up to request a tunnel with listen port 3389 and
destionation of 3389 and the destination hostname.

When I connect I get an error like "Failed to create an outgoing
tunnel."

If I set the source port to 3388, and connect, then I do not get this
error. I don't quite understand why. It would seem it wouldn't
conflict, as the listen port only applies to my computer, and the
destination port only applies to the destination computer.

Maybe my computer is already listening for 3389 and the SSH client
can't connect to it as well?
.



Relevant Pages

  • Re: How do I FTP via a secure tunnel (set up instructions
    ... I want to run an FTP client and FTP deamon ... >> via this tunnel. ... > destination from A to Z then your destination must support for example ... Unless your destination has ssh available, ...
    (alt.privacy)
  • Re: How do I FTP via a secure tunnel (set up instructions
    ... I want to run an FTP client and FTP deamon ... >>> via this tunnel. ... >> destination from A to Z then your destination must support for example ... Unless your destination has ssh available, ...
    (alt.privacy)
  • Re: How do I FTP via a secure tunnel (set up instructions requested)
    ... I want to run an FTP client and FTP deamon ... > via this tunnel. ... destination from A to Z then your destination must support for example ... Unless your destination has ssh available, ...
    (alt.privacy)
  • Re: Tunnel with same listen and destination port
    ... When I log into the SSH server, I can ping the windows ... So in my SSH ... client I have set it up to request a tunnel with listen port 3389 and ...
    (comp.security.ssh)
  • Re: What is The SSH?
    ... Building and Using SSH Tunnels ... What is an SSH tunnel? ... how to use it to make a connection to a server. ... You will need a working SSH client and server installation to build and test ...
    (microsoft.public.windows.server.networking)