Re: Windows Remote Desktop over ssh
- From: comphelp@xxxxxxxxx (Todd H.)
- Date: 23 Jan 2006 10:02:01 -0600
"O. Olson" <olson_ord@xxxxxxxx> writes:
> O. Olson wrote:
>
> > ssh -L 3389: 10.1.169.25:3389 usern...@xxxxxxxxxxxxxxxxxxxxxxx
> >
> Before someone catches me here I would like to mention that I have
> tried both 3389 and 3390
> i.e.
> ssh -L 3389:10.1.169.25:3389 usern...@xxxxxxxxxxxxxxxxxxxxxxx
> rdesktop localhost or rdesktop localhost:3389
>
> and
> ssh -L 3390:10.1.169.25:3389 usern...@xxxxxxxxxxxxxxxxxxxxxxx
> rdesktop localhost:3390
>
> - and both have not worked.
Well poop.
Try the -vv option with ssh, and see if it tells you anything useful
when you try to rdesktop.
Also run netstat -an| grep LISTEN on the Linux box to verify that is
indeed listening to 3390 or 3389 when issuing the ssh command.
Oh... one thing you may need to check is whether windows firewall is
eating things. Do you have a hardware firewall such that you can
safely drop windows firewall for testing?
--
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
- Re: Windows Remote Desktop over ssh
- From: O. Olson
- Windows Remote Desktop over ssh
- Prev by Date: ssh key based authentication
- Next by Date: Re: OpenSSH passwordless scp not working
- Previous by thread: Re: Windows Remote Desktop over ssh
- Next by thread: Re: Windows Remote Desktop over ssh
- Index(es):