ttelesca
asked on
Error when trying to use remote desktop through an SSH tunnel
I am using PUTTY to create an SSH tunnel from one xp machine to another machine. I can connect to the PC via PUTTY just fine, but once I try to RDC to localhost I run into problems. Initially I was getting a message saying that another console could not be opened. I modified the registry so that XP would allow multiple connections to it. When I specify the fowarded port with localhost (3390 in this case) I get "the client could not connect to the remote computer". I really not sure where to go next, or what I'm doing wrong. Any help would be appreciated. Thanks
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I did set up the forwarding, but I think I'm confused by what you mean. Which port do I set for source, and which gets set after the : following localhost?
ASKER
Oh, and I'm testing this on my LAN, so no ports have been forwarded on the router.
In the Add new forwarded port:
Source Port: 3390
Destination: remoteservername:3389
Local
Auto
Source Port: 3390
Destination: remoteservername:3389
Local
Auto
After the SSH session is up and running, launch RPD and put in localhost:3390 as the computer.
are you able to remotely connect to the machine without the use of Putty. if not, try to do so. you want to eliminate problems,
Try to use RDP without tunneling the connection. If you get connected, then you'd know the problem is coming from a configuration in setting up the tunnel
Try to use RDP without tunneling the connection. If you get connected, then you'd know the problem is coming from a configuration in setting up the tunnel
ASKER
Ok, i set up the port fowarding as you suggested, except I did it with the local ip address. Now I'm getting "the client could not establish a connection to the remote computer". Remote access is granted on the PC I'm trying to connect to with the correct user. Does the forwarding need to be done by pc name? Still stuck. . . .
You say that you used local ip address.
The field in putty "Source Port:" only needs the local port (no need for IP or name).
Source Port: 3390
The destination can be the IP of the remote server.
Destination: 192.168.1.5:3389
Once you click add, you will notice it looks like "L.3390 192.168.1.5:3389" Which is correct. If this is still not working you should start looking at some of the issues Viruscan is pointing out. Has the 3389 port been excluded on the target server? It needs to be.
The field in putty "Source Port:" only needs the local port (no need for IP or name).
Source Port: 3390
The destination can be the IP of the remote server.
Destination: 192.168.1.5:3389
Once you click add, you will notice it looks like "L.3390 192.168.1.5:3389" Which is correct. If this is still not working you should start looking at some of the issues Viruscan is pointing out. Has the 3389 port been excluded on the target server? It needs to be.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ttelesca, do you have any updates, meaning, did the solutions we provided were of any use to you.
Please give us an update.
txs
Please give us an update.
txs
Forced accept.
Computer101
EE Admin
Computer101
EE Admin
connection >> ssh >> tunnels
Using 3390 for localhost and 3389 for the remote IP.