Port forwarding is set, but the game still shows Strict NAT
Request
I set up a port-forward rule, but the game still shows Strict NAT or a port checker says the port is closed.
A port-forward rule can look correct and still do nothing. It only works when the rule is on the device that receives traffic from the internet, points to the right local device, and the game or server is actually listening on that port.
Do not open more ports, use DMZ, or disable the firewall as the first move. First find where the traffic stops.
Open the router status page and look for WAN IP, Internet IP, or IPv4 address. Compare it with a public IP checker in your browser.
If the router WAN starts with 10., 192.168., 172.16 through 172.31, or 100.64 through 100.127, your rule is probably not at the public edge. 10.x, 192.168.x, and 172.16-31.x usually mean another router or ISP modem is in front of yours. 100.64-100.127.x often means CGNAT, where many home plans cannot receive inbound IPv4 traffic.
If the WAN IP matches the public checker, move to the local-device checks. If it does not match, find the first box connected to the internet line. The clean fixes are bridge mode on the ISP modem/router if supported, a first port-forward from the ISP modem/router to your router and a second rule from your router to the PC or console, or a public IPv4 request from the ISP if the WAN is CGNAT.
If the ISP cannot provide public IPv4, normal port forwarding will not work from your side. Use a public IPv4 add-on, IPv6 if the game/server supports it, a VPN with port forwarding, or a hosted server instead.
If the WAN IP is public, check the local target:
- On the PC, run
ipconfigand check the IPv4 address. On a console, open network status. - Reserve that address in the router DHCP/reservation page.
- Edit the port-forward rule so the LAN IP is that reserved address.
- Check whether the game or server uses TCP, UDP, or both. A TCP-only rule will not help a UDP-only game.
- Restart the game/server after changing the rule, then test again.
Then test from outside your own Wi-Fi. Many routers do not support hairpin NAT, so a port test from the same Wi-Fi can say closed even when the port works from the internet. Use a phone on cellular data, a friend outside your network, the game’s own NAT test after restarting the game, or a port checker only after the app/server is actually running. If nothing is listening on the port, a checker will show closed even when the router rule is correct.
Keep the network safe. Do not start with DMZ, huge port ranges, remote-admin exposure, or disabling the firewall. For consoles, UPnP can be safer than manual port chaos if the router handles it well. For a home server, open only the exact port, keep the service updated, and do not expose admin panels.
If you ask for help, send only the router WAN/Internet status line, the PC or console local IP reservation, the one exact port-forward rule being tested, and the game/server screen that still says Strict NAT or closed port. Hide public IPs, usernames, serial numbers, Wi-Fi passwords, and account details.
Stop here if your ISP uses CGNAT and cannot provide public IPv4, you are forwarding ports for remote admin/NAS admin/RDP or another sensitive service, you need to expose a work device or private camera system, or the router is managed by your building, school, employer, or ISP.
Related Price2Click guide: Fix Home Wi-Fi.