2 Port Forwards both trigger the same application despite having different ports
I have two Windows 11 computers on my network that I want to access using Remote Desktop. In the past with a Netgear router I was able to set both of these up with no problem and could get to either machine.
I have a DDNS with no-ip and it is registering with my Router. I have the Router in Router Mode, and my Fiber Modem is set up with IP Pass through.
I'm able to access everything in terms of browsing and general networking However since I have moved over to TPLink, I cannot duplicate my Port Forwarding success I experienced with the Netgear.
First of all, setting up the Port Forward on the TPLink, the External port seems to not matter as I have used both a range of all ports (1-65535) and individual ports but I settled on the full range of ports. When I try to setup another computer which has a different IP and a different port, I cannot add the full range of ports for External Port because TPLink doesn't allow overlap with any other port forwards. This WAS NOT the case with the Netgear Router.
So I have two port forwards setup and instead of using the full range of External Ports, I used the same external port that I use for the internal port. This works for computer 1 So I duplicated this on Computer 2 using a different External and Internal port and have it forwarding to a different IP. I decided to use different single ports for the External port which is the same as the internal port
As an example Port Forward
Service Name | Device IP Address | External Port | Internal Port | Protocol | Status | Modify |
---|
RDP83 |
192.168.2.74 |
35588 |
35588 |
TCP |
|||
RDP47 |
192.168.2.87 |
24525 |
24525 |
TCP |
My problem is that Service Name RDP47 works fine and it it forwards it to 192.168.2.87
However when I try to connect to RDP83, instead of it forwarding it to 192.168.2.74, it forwards it to 192.168.2.87
I can connect to both of these computers using local LAN addresses which proves there is nothing wrong with the RDP side, and I know this doesn't go through the port forwarding logic.
I've tried to use Port triggering but I can't get anything to work with that option