SSH And Remote Desktop

[webuser]

I have been exploring using SSH as the protocol to access a Remote Desktop Application for my customers. Every time I ask someone what the disadvantages or risks are, I get a long winded response that usually does not make sense to me. Here is my proposed scenario:

Terminal Services box with SSH Server on it (or possibly on another box). Clients will use freeware SSH client to tunnel RDP through to the SSH Server which will forward it to the Terminal Services box on the same machine. Some of the SSH clients have the ability to embed an encrypted UserName/Password in the client profile, that only the admin (me) would know. So they would need that profile file (essentialy like a certificate I think) plus a UserName/Password to access Remote Desktop.

I am trying to accomplish several goals:
Keep costs down and keep it simple

We have tried other solutions like SSL VPN or IPSec VPN etc, but each has it's drawbacks (too complex, too many extra machines to maintain etc.)
This SSH thing sounds too good to be true. Is it and why?

Please advise...

Thanks in advance!!!

 

[MRamius]

You may have resolved this already by now, but just in case, I read an excellent article detailing every part of the process you are describing:

http://theillustratednetwork.mvps.org/RemoteDesktop/SSH-RDP-VNC/RemoteDesktopVNCandSSH.html

.

I would interested in hearing about whatever solution you came up with. Thanks.

 

[shane007]

We have used WiSSH.. We setup a linux SSH server and then connect through that to ANY computer on our internal network, Only port open to publich is SSH and that is secured through the linux login server. This setup works great! We have accomplished the same using Putty and the example above, but WiSSH was an easier solution for our non tech clients.

http://www.wissh.com/

(SLM)