Fix Port Forwarding Not Working on Router
Configured port forwarding rules fail to expose local services to the external internet, often due to CGNAT, double NAT, or host firewall blocks.
Confirmed working on: Windows 10 · Windows 11 · Routers
Before you begin
Problem overview
You have configured port forwarding rules on your router, but external users or port checking tools report that the port is still closed. This prevents remote access to local servers or affects gaming connectivity.
Common causes
- Carrier-Grade NAT (CGNAT) deployed by your ISP
- A Double NAT environment (e.g., two routers chained together)
- The target device’s local firewall blocking the inbound connection
- The port forwarding rule targets the wrong internal IP address
Solution 1: Check for Carrier-Grade NAT (CGNAT)
- Open a web browser and visit
whatismyip.comto find your public IPv4 address. - Log into your router’s web interface.
- Look for the WAN IP or Internet IP on the router’s status page.
- Compare the two IP addresses. If they are different, your ISP is using CGNAT.
- If you are behind CGNAT, traditional port forwarding will not work. You must contact your ISP to request a public IP or use a tunneling service.
If your router’s WAN IP starts with 100.64.x.x through 100.127.x.x, you are definitely behind a CGNAT.
Solution 2: Assign a static LAN IP
- Open Command Prompt on the target computer and run
ipconfig. Note your IPv4 Address and Default Gateway. - Log into your router and navigate to the DHCP or LAN Settings section.
- Find the DHCP Reservation or Static Lease feature.
- Add a new reservation using your computer’s MAC address and assign it the current IP address.
- Save the settings. Ensure your port forwarding rule points to this exact IP address.
Solution 3: Allow the port through Windows Firewall
- Press
Windows Key + R, typewf.msc, and press Enter to open Windows Defender Firewall with Advanced Security. - Select Inbound Rules on the left pane.
- Click New Rule on the right pane.
- Select Port and click Next.
- Choose TCP or UDP (depending on your service) and enter the specific port number.
- Select Allow the connection and apply the rule to all network profiles (Domain, Private, Public).
- Name the rule and click Finish.
- Retest your port using a service like
portchecker.co.
Solution 4: Eliminate Double NAT
- Trace your network layout. If you have a modem/router combo from your ISP and a second personal router, you have a Double NAT.
- Log into the ISP modem/router combo.
- Locate the Bridge Mode or IP Passthrough setting and enable it.
- Alternatively, find the DMZ setting on the ISP router and enter the WAN IP address of your personal router.
- Save and reboot both devices.
Enabling DMZ on your primary PC directly exposes it to the entire internet, bypassing the router’s hardware firewall. Only use DMZ to pass traffic to a secondary router.
Confirm the result
- Repeat the exact action that originally triggered the problem.
- Confirm the original error or symptom is gone and no new warning has appeared.
- If the guide changed a driver, service, package, or system setting, restart once and test again.
- If the result is worse or unexpected, stop. Reverse only the last change using its documented restore option; if none is documented, use your backup or qualified support.
Questions about this fix
How do I know if I have CGNAT?
Compare the WAN IP shown in your router interface to the IP shown on sites like whatismyip.com. If they don't match, you likely have CGNAT.
Do I need a static IP for port forwarding?
You need a static internal LAN IP for the device hosting the service, so the router always knows where to forward the traffic.
Did this fix work for you?
Weighted Consensus Protocol
Did this solution resolve your issue?
Confirming if this works strengthens verification statistics on the registry.
FixingTeam10,000 rep
Official Project Maintainers
The core engineering and moderation team behind FixingBook. We curate, verify, and maintain the standards of the troubleshooting ledger.
Related fixes
Fix Double NAT (Strict NAT Type) Issues
Two routers are performing Network Address Translation in series, leading to strict NAT types in gaming and broken port forwarding.
Fix Windows Firewall Blocking Ping (ICMP Echo)
Local network devices cannot ping a Windows machine because the default Windows Defender Firewall rules block ICMPv4 Echo Requests.
Discussion (0)
No comments yet. Share your experience or verify if this fixed your issue!
