Re: Windows Remote Desktop over ssh
- From: comphelp@xxxxxxxxx (Todd H.)
- Date: 23 Jan 2006 15:43:15 -0600
"O. Olson" <olson_ord@xxxxxxxx> writes:
> Dear Todd,
> Thanks for responding. My internal LAN IP address is 10.1.169.25
>
> So I ended up trying
>
> ssh -L 3389: 10.1.169.25:3389 usern...@xxxxxxxxxxxxxxxxxxxxxxx
>
> - this did not work.
Did you really have a space between the first colon and the 10? If
so try without that space as in
ssh -L 3389:10.1.169.25:3389 usern...@xxxxxxxxxxxxxxxxxxxxxxx
if that fails try
ssh -L 3389:127.0.0.1:3389 usern...@xxxxxxxxxxxxxxxxxxxxxxx
If it still doesn't work can you tell us what ssh server you're
running on that windows box? Perhaps post the config file for the
sshd? The symptoms you're telling us seem like perhaps port
forwarding is turned off on your windows ssh server? But then again
the test you did from the windows box to itself with
-L3390:127.0.0.1:3389 and rdesktoping to 127.00.1:3390 I suppose rules
that out.
Another netstat command that might be helpful in debugging is
sshclientmachine$ netstatn -an | grep 3389
or whatever number you choose as the first port number in the -L
argument. That'll narrow it down from all the other ports that might
be listening.
Strange that setting up the reverse listener works, but the forward
one does not.
--
Todd H.
http://www.toddh.net/
.
- Follow-Ups:
- Re: Windows Remote Desktop over ssh
- From: O. Olson
- Re: Windows Remote Desktop over ssh
- References:
- Windows Remote Desktop over ssh
- From: O. Olson
- Re: Windows Remote Desktop over ssh
- From: Todd H.
- Re: Windows Remote Desktop over ssh
- From: O. Olson
- Windows Remote Desktop over ssh
- Prev by Date: Re: Windows Remote Desktop over ssh
- Next by Date: Re: OpenSSH 4.2p1 Compression Problems
- Previous by thread: Re: Windows Remote Desktop over ssh
- Next by thread: Re: Windows Remote Desktop over ssh
- Index(es):
Relevant Pages
|
|