Remote Desktop to more than one box with a wan ip

Soldato
Joined
28 Sep 2008
Posts
14,196
Location
Britain
Is it possible?

At the site, the router forwards RDP pings to the main server. lets say its wan IP is 10.11.12.13

If there are more than one machine here with RDP enabled, is there a way to access them?

Otherwise, I have to RDP from the main server, or use logmein which seems to be stupidly slow for some reason.

Ta
 
It most definitely is, I'm doing so now.

You might have to make a custom icon for this htough.

I've got 2 icons for my 2 PCs I connect to via RDP.

"target" mstsc.exe

"Arguments" /v:192.168.0.3 /w:1500 /h:750
 
+1 for Pea0n

Here is how to do it:
http://support.microsoft.com/kb/306759
It says for XP for works in XP/Vista/7 as well as Server.

You then use the format 10.111.12.13:12345 (or whatever port you set) in the Terminal Server client.
I'm not 100% sure if it's the same if you lauch the client from the command line.

Also remember you'll need to forward each port in the router to the correct LAN IP too.

@Kyle, he wants to access it from his WAN IP which is NAT'd
 
Last edited:
It most definitely is, I'm doing so now.

You might have to make a custom icon for this htough.

I've got 2 icons for my 2 PCs I connect to via RDP.

"target" mstsc.exe

"Arguments" /v:192.168.0.3 /w:1500 /h:750

Cheers mate, can you explain in more detail. Are you just creating shortcuts?

I'm on Windows 7, where do I stick the Argument?
 
+1 for Pea0n

Here is how to do it:
http://support.microsoft.com/kb/306759
It says for XP for works in XP/Vista/7 as well as Server.

You then use the format 10.111.12.13:12345 (or whatever port you set) in the Terminal Server client.
I'm not 100% sure if it's the same if you lauch the client from the command line.

Also remember you'll need to forward each port in the router to the correct LAN IP too.

@Kyle, he wants to access it from his WAN IP which is NAT'd

Ah, ok. Will do this. Ta
 
Can't you do the whole thing on the router with port forwarding?

WAN IP:1234 --> inside NAT 1:3389
WAN IP:4321 --> inside NAT 2:3389

That way you can do the whole thing without any registry tweaking on the RDP hosts.
 
Can't you do the whole thing on the router with port forwarding?

WAN IP:1234 --> inside NAT 1:3389
WAN IP:4321 --> inside NAT 2:3389

That way you can do the whole thing without any registry tweaking on the RDP hosts.

Hmm, I must be doing somthing wrong. The site has a netgear router but I don't see a NAT option.

Are you suggesting that if the router receives a request to the WAN ip with say :1234 after it, it will address it to the internal IP port :3389 (RDP)?
 
Yep exactly that. I think it's labeled as port forwarding on Netgear routers.

OK, I can create a service (I've called it RDP with port 3389) and then add it to the firewall, but it only lets me add a WAN IP in 4 defined blocks, as in, there is no way to specify a port just the IP address :(

Any ideas?
 
Last edited:
Netgears generally only do NAT, not PAT or PNAT.
You can only do NAT based on ports, but not translate the port at the same time.

Changing the listening port is the only easy solution.
 
Last edited:
Back
Top Bottom