Forwarding ports to different port numbers

[rbxslvr]

Is it possible to forward a port to a different port number? I'm interested in using remote desktop on several computers on my network - which works fine within LAN, but if I want to access it from outside the network, I have to choose one to forward to.

I'd like to have it set up so that my ip forwards to port 3389 from 3390 and 3391... ie:

99.18.xx.xx:3390 forwards to 192.168.1.113:3389
99.18.xx.xx:3391 forwards to 192.168.1.114:3389

Is there a way to do something like this? Or perhaps another way to achieve this goal?

 

[MyDixieWrecked]

What you've described isn't what you're looking for. You can absolutely do that by forwarding each port to the same LAN IP, but I don't think that's what you're getting at. However, you can change the listening port on each PC on the LAN, then create a rule for each port to be forwarded. Just to go the registry and change the port number from 3389 to whatever you want. The key is located at HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp. The next step would be port forwarding each port to the correct PC. Then, when you connect from the WAN, just specify the port to get to the right PC on the LAN. Cheers.

 

[Black6]

This is something you would set in your firewall port forwarding settings. The internal port number can stay the same for each computer. Also, pick unique port numbers for the outside ports. Might just as well make it a little more difficult for hackers than using default port numbers.

 

[tremmor]

Check here. Lot more detail.
http://portforward.com/

 

[MyDixieWrecked]

This is something you would set in your firewall port forwarding settings. The internal port number can stay the same for each computer. Also, pick unique port numbers for the outside ports. Might just as well make it a little more difficult for hackers than using default port numbers.

Well, that's just wrong. If you want to be able to access two different PCs (let's start with two) on a LAN from a WAN, you cannot use the same port, as the router will not know which PC to forward the packets to. How can you create a rule in a router that says "Forward all incoming packets using port 3389 to 192.168.1.5 and 192.168.1.6?" What you need to do is change one PC to listen to port 3390 (or whatever) then tell the router "For port 3389, forward to 192.168.1.5 and for 3390, forward to 192.168.1.6" That way, when you open your Remote Desktop application, you can just type in YOURWANIP:3389 to get to .5 and YOURWANIP:3390 to get to .6. Cheers.

PS - Please excuse the lateness of my reply. I've been on vacation.

 

[Black6]

Well, that's just wrong. If you want to be able to access two different PCs (let's start with two) on a LAN from a WAN, you cannot use the same port, as the router will not know which PC to forward the packets to. How can you create a rule in a router that says "Forward all incoming packets using port 3389 to 192.168.1.5 and 192.168.1.6?" What you need to do is change one PC to listen to port 3390 (or whatever) then tell the router "For port 3389, forward to 192.168.1.5 and for 3390, forward to 192.168.1.6" That way, when you open your Remote Desktop application, you can just type in YOURWANIP:3389 to get to .5 and YOURWANIP:3390 to get to .6. Cheers.

PS - Please excuse the lateness of my reply. I've been on vacation.

Apparently the six Linux servers I am running SSH on with the same internal port number don't know that.

192.168.100.1:22 = external IP:1025
192.168.100.2:22 = external IP:1026
192.168.100.3:22 = external IP:1027

 

[MyDixieWrecked]

Apparently the six Linux servers I am running SSH on with the same internal port number don't know that.

192.168.100.1:22 = external IP:1025
192.168.100.2:22 = external IP:1026
192.168.100.3:22 = external IP:1027

Well, yeah if that's your configuration (VHM) then it will work, but seeing as you're trying to use Remote Desktop, I thought you were talking about a standard Windows setup. It's little details like this that can be added to the original issue to avoid confusion. I wasn't about to have a Windows admin attempt to setup VHM in a Linux environment... Cheers.