Port Forwarding / DMZ not working

Port Forwarding / DMZ not working

Port Forwarding / DMZ not working
Port Forwarding / DMZ not working
2025-02-05 18:42:40 - last edited 2 weeks ago
Model: Archer AX3000  
Hardware Version: V1
Firmware Version: 1.3.1 Build 20241120 rel.54901(5553)

Port forwarding dosen't seems to be working on my router.

 

Quick disclaiment: I have double NAT setup but I dont think that this is the issue, more on that below.

 

So, here's my setup. I have my ISP modem alongside my TP-Link Router with DMZ and port forwarding configured on both, from my modem to the router and from the router to my NAS. The modem DHCP is configured to use 192.168.2.1 up until 192.168.2.254 while having the TP-Link bound to 192.168.2.2 (both as Fixed IP on the Router and as DHCP Binding on the Modem). The router DHCP is configured to use 192.168.1.0 up until 192.168.1.254 with a fixed ip for my NAS. I'm testing with some random private port 50123 so to exclude the possbility that my ISP is blocking it.

 

Rigth. When I try to telnet into that port from my phone using 5G (from the internet) all I got is timeout after a while. When I try to do the same but connected to the modem subnet it also timeout after a while. To eliminate the possibility that perhaps my NAS isn't repsponding I tested both accessing the port from within the route subnet (it worked) and from the internet with the NAS connected directly to the modem with the DMZ pointing to it (it also worked). That's why I don't think the issue would be double NAT, becouse if it were the case it would've worked from my phone contected to the modem subnet (as it would not be a double NAT setup in this case). Of course this does not exclude that a double NAT is ALSO a problem, but for sure isn't the only one.

Also a simple ping test from the modem to the external ip of the router show that it's responding properly

 

PING 192.168.2.2 (192.168.2.2): 56 data bytes
Reply from 192.168.2.2: bytes=56 ttl=64 time=0.9ms seq=0
Reply from 192.168.2.2: bytes=56 ttl=64 time=0.8ms seq=1
Reply from 192.168.2.2: bytes=56 ttl=64 time=0.8ms seq=2
Reply from 192.168.2.2: bytes=56 ttl=64 time=0.8ms seq=3

--- 192.168.2.2 ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 0.8/0.8/0.9 ms

 

What could be messing up this seput?

 

Before anyone says anything, I know exposing my NAS to the internet with DMZ is usually not a good idea, I'm just using it while trying to make it work, I intend to use only port forwarding for the ports I want to expose then.

  0      
  0      
#1
Options
1 Accepted Solution
Re:Port Forwarding / DMZ not working-Solution
2 weeks ago - last edited 2 weeks ago

Hi @eKorn,

Port forwarding on a router is a technique that is used to allow external devices access to services on private networks. This is typically used for gaming, running a web server, or for some peer-to-peer file sharing systems. The port forwarding feature is only available when the router is working in Router Mode.
You may log in to rotuer's Web management page and go to Advanced > NAT Forwarding > Port Forwarding/Virtual Server/DMZ to configure it. You can set up to 32 entries.
If you are using port forwarding and DMZ host at the same time, please note that port forwarding rules have greater priority than DMZ.
This FAQ provides the detailed instructions on configuring port forwarding based on different router models: Port forwarding: how to set up virtual server on TP-Link wireless router?
Additionally, here are some tips for you if port forwarding doesn't work:
    1. Make sure the server is accessible from the internal network.
    2. Make sure your router obtains the public WAN IP address, if your WAN IP is not a public one, port forwarding will not work. (CGNAT address is also private IP address that ranges from 100.64.0.0 to 100.127.255.255.)
    3. Check the firewall settings of your server, make sure it allows traffic from the outside Internet.
You may check more detailed instruction following the FAQ: Why port forwarding feature is not working on my Wi-Fi router or Deco?

Recommended Solution
  0  
  0  
#3
Options
1 Reply
Re:Port Forwarding / DMZ not working-Solution
2 weeks ago - last edited 2 weeks ago

Hi @eKorn,

Port forwarding on a router is a technique that is used to allow external devices access to services on private networks. This is typically used for gaming, running a web server, or for some peer-to-peer file sharing systems. The port forwarding feature is only available when the router is working in Router Mode.
You may log in to rotuer's Web management page and go to Advanced > NAT Forwarding > Port Forwarding/Virtual Server/DMZ to configure it. You can set up to 32 entries.
If you are using port forwarding and DMZ host at the same time, please note that port forwarding rules have greater priority than DMZ.
This FAQ provides the detailed instructions on configuring port forwarding based on different router models: Port forwarding: how to set up virtual server on TP-Link wireless router?
Additionally, here are some tips for you if port forwarding doesn't work:
    1. Make sure the server is accessible from the internal network.
    2. Make sure your router obtains the public WAN IP address, if your WAN IP is not a public one, port forwarding will not work. (CGNAT address is also private IP address that ranges from 100.64.0.0 to 100.127.255.255.)
    3. Check the firewall settings of your server, make sure it allows traffic from the outside Internet.
You may check more detailed instruction following the FAQ: Why port forwarding feature is not working on my Wi-Fi router or Deco?

Recommended Solution
  0  
  0  
#3
Options