The putty tunnels defined in any session are not created. These tunnels work if putty is used in the native RDP client. I'm attempting to connect to localhost which is then tunneled (securely) by putty.

Any ideas?
Thanks in advance!

Adam

Honestly, I have no idea what you are trying to do, so I have no way to test it. Can you elaborate some?

http://theillustratednet...sh/RemoteDesktopSSH.html 

Thanks!
Adam

Unfortunately, I do not have a SSH server to test this, so I cannot tell you exactly if this scenario will work with RD Tabs, nor can I help with debugging this scenario.

However, I can offer these tips...

1. If you are worried about security, require TLS on the server side. This is as secure as SSH (possibly more secure) as it relies on a SSL certificate for encryption.

2. If you want to access more than one remote desktop server on the same IP address, you can change the listening port for RDP on the server side, so that you can go to domain.com, domain.com:3391, domain.com:3392, etc. to access different PCs, assuming your router/firewall allows you to set up different internal destination PCs based on port. http://support.microsoft.com/kb/306759  - Note that port 3390 has issues (for some reason) on some computers. I don't know why, but I've read it in several places that using port 3390 won't work due to some bug.

To specify a non-standard port in RD Tabs, you cannot use the server:port method in the computer name. You must change the port number in the "RDP Port" box.

If this doesn't help, maybe somebody else can chime in if they've tried SSH port forwarding with RD Tabs.

instead of connecting to localhost use 127.0.0.2. RDP will not allow you to connect to your local host so you have to fool it by using the alternate address.