Strict NAT in Windows can ruin the online gaming experience — difficulty connecting to parties, lag, or inability to host games. The good news is that NAT type is largely a router configuration issue, with a few Windows-specific settings that matter. You’ll find the complete rundown in our Complete Guide to Fixing Windows, Browser, and Software Errors.
First: understand what NAT type actually means for your situation. If you’re on a home network with a router: fixing NAT type means configuring the router (and sometimes Windows). If you’re in a student dorm, office, or on mobile data: the NAT type may be set by the ISP or network administrator, and local changes may not help.
What the NAT types mean
- Open / Type 1: no restrictions — direct connection to the internet. Best for gaming.
- Moderate / Type 2: router with UPnP or port forwarding configured. Most gaming functions work normally.
- Strict / Type 3: heavily restricted — can only connect to Open NAT players; can’t host games; party chat may fail
Most home routers produce Moderate (Type 2) NAT by default when configured with UPnP. Strict NAT usually indicates UPnP is disabled, a double NAT situation (two routers in series), or ISP-level restrictions.
Fix 1: Enable UPnP on your router
UPnP (Universal Plug and Play) lets gaming applications automatically request port forwarding from the router. This is the fastest fix and handles NAT negotiation automatically without manual port configuration.
- Open your router’s admin page (typically 192.168.1.1 or 192.168.0.1 — check the sticker on your router)
- Look for UPnP settings under: Advanced, Network, or NAT settings
- Enable UPnP → save → restart the router
- Restart the Windows machine → recheck NAT type in the game or through Xbox’s NAT test (Settings → General → Network settings → Test NAT type)
UPnP works for most home gaming scenarios. Security-conscious users note that UPnP has had vulnerabilities — weigh this against NAT type needs.
Fix 2: Port forwarding for specific games
If UPnP isn’t available or you prefer not to use it: manually forward the ports each game requires. This gives guaranteed Open NAT for those specific games without UPnP’s security concerns.
Common gaming ports:
- Xbox/Microsoft gaming: TCP/UDP 3074, UDP 88, UDP 500, UDP 3544, UDP 4500
- PlayStation network: TCP 80, TCP 443, TCP 3478, TCP 3479, UDP 3478, UDP 3479
- Steam: UDP 27000-27100 (game traffic), TCP 27015-27030
- Specific games: check the game publisher’s support page for current port requirements
In the router admin: Advanced → Port Forwarding → add rules pointing those ports to the Windows machine’s local IP address.
Fix 3: DMZ as a last resort
If port forwarding doesn’t achieve Open NAT: putting the Windows machine’s IP in the router’s DMZ (Demilitarised Zone) gives it unrestricted inbound access. Router → Advanced → DMZ → enter the Windows machine’s local IP.
Security warning: DMZ exposes the machine directly to the internet with no router-level NAT protection. Only use on machines with Windows Defender Firewall enabled, no open services, and all software updated. A gaming console in DMZ is lower risk than a PC due to the more limited attack surface.
Fix 4: Check for double NAT
Double NAT (two routers between the PC and internet) creates strict NAT that can’t be fixed by UPnP or port forwarding on the outer router alone. Run Command Prompt → tracert 8.8.8.8 → look at the first two hops. If both show private IP addresses (192.168.x.x, 10.x.x.x): double NAT exists.
Solutions:
- Put the outer device (typically the ISP modem-router) in bridge mode — converts it to a simple modem, removing its NAT layer
- Or: configure UPnP/port forwarding on both devices (both must have the same rules)
Windows Firewall and NAT type
Windows Defender Firewall doesn’t directly cause strict NAT (that’s the router’s job), but it can prevent games from communicating even with Open NAT. If NAT shows as Open but games still have connection issues: Windows Firewall → Allow an app through firewall → confirm the game executable has both Private and Public access.
Also: Settings → Network and internet → your connection → Network profile → set to “Private” rather than “Public.” Public profile has more restrictive firewall rules that can mimic strict NAT symptoms even when router NAT is correctly configured.
Teredo for Xbox Live on PC
Xbox gaming on Windows 11 uses Teredo, a tunnelling protocol for IPv6 connectivity. If Xbox Live shows strict NAT on Windows specifically: Administrator Command Prompt:
netsh interface teredo set state type=default
netsh interface teredo show state
If Teredo shows “Error” or “Qualified: No”: restart and test. Also check: if a VPN is installed, Teredo often conflicts with VPN virtual adapters. Disabling the VPN virtual adapter when not in use resolves Teredo qualification failures for Xbox Live on Windows.
Our guide on gaming network performance covers latency and packet loss issues that affect gaming alongside NAT type. For VPN conflicts that affect both NAT type and game connectivity, our VPN troubleshooting guide covers the adapter and routing conflicts. Microsoft’s Xbox networking documentation covers the specific port and protocol requirements for Xbox Live on Windows 11 and the network diagnostic tool in the Xbox app that checks connectivity, NAT type, and service availability simultaneously.
Static IP for stable port forwarding
Port forwarding rules target a specific local IP address. If the Windows machine gets its IP via DHCP (automatic assignment), the IP can change when the machine restarts or the DHCP lease expires. When the IP changes, the forwarding rules point to the wrong device — or to nothing — and NAT type reverts to strict.
Fix this by assigning a static IP either:
- At the router (DHCP reservation): in the router’s DHCP settings, reserve a specific IP for the Windows machine’s MAC address. The machine still uses DHCP but always gets the same IP. No configuration needed on Windows.
- In Windows: Settings → Network and internet → your connection → IP settings → Manual → enter a static IP, subnet mask, gateway, and DNS. Choose an IP outside the router’s DHCP range to avoid conflicts (e.g., if DHCP assigns 192.168.1.100-200, use 192.168.1.50).
ISP-level NAT (CGNAT)
Carrier-Grade NAT (CGNAT) means your ISP assigns a private IP to your router rather than a public one — multiple customers share a single public IP. CGNAT makes it impossible to achieve Open NAT because port forwarding at your router doesn’t reach the public internet.
Check for CGNAT: router admin → WAN IP address. If it shows a private address (10.x.x.x, 172.16-31.x.x, 192.168.x.x) rather than a public IP: your ISP is using CGNAT. Solutions:
- Contact ISP and request a public IP (some ISPs charge for this; some provide it free on request)
- Use a VPN that provides a dedicated IP — routes your gaming traffic through the VPN’s public IP, bypassing CGNAT. Some VPN providers offer gaming-specific plans with fixed IPs for this purpose
- Accept moderate NAT — CGNAT often allows Moderate (Type 2) NAT for most games, even if Open (Type 1) isn’t achievable
Game-specific NAT requirements
Not all games require Open NAT to function well. Modern games often work fine with Moderate NAT — strict NAT is the problem tier. Some older games or games with poor P2P implementations struggle with anything below Open. Check the specific game’s community or developer documentation for what NAT type is required and what the symptoms of each NAT type look like in that game.
For example: Call of Duty series has historically been more NAT-sensitive than games using dedicated servers like Fortnite. Understanding whether the specific game uses P2P (NAT-sensitive) or dedicated servers (less NAT-sensitive) helps calibrate how urgently fixing NAT type is needed.
Xbox app network test
The Xbox app on Windows 11 includes a NAT type test: Xbox app → Settings → General → Network settings → “Test NAT type.” This specifically tests Xbox Live/Game Pass game connectivity. Results:
- “Open” — no restrictions; best state
- “Moderate” — most gaming features work; can connect to Open and Moderate players
- “Strict” — limited connectivity; can only connect to Open players; can’t host
The test also checks for Teredo qualification and shows which specific connectivity tests passed or failed — more informative than just the NAT type label alone.
NAT type and console vs PC differences
Consoles (Xbox, PlayStation) use a simplified NAT type system that maps cleanly to their specific protocols. PC gaming has a more complex situation because different games, platforms (Steam, Xbox, Epic, Battle.net), and protocols each have independent NAT behaviour. A PC showing Moderate NAT for Xbox Live may show Open NAT for Steam simultaneously because they use different protocols and port ranges.
Troubleshoot NAT type per platform/game rather than seeking a single universal Open NAT fix. Enabling UPnP usually achieves Open or Moderate NAT for all platforms simultaneously. Manual port forwarding requires separate rules per platform.
VPN and NAT type interaction
A VPN can improve or worsen NAT type depending on configuration. An “open” VPN with a dedicated IP can give Open NAT by routing traffic through the VPN’s unrestricted connection. But VPNs that use Symmetric NAT internally (many consumer VPNs) worsen NAT type to Strict regardless of the underlying network.
Test: connect and disconnect the VPN → check NAT type each time. If NAT type is better without VPN: the VPN is adding NAT restrictions. If better with VPN: the VPN is providing a better connection path than the underlying network (CGNAT situation). This test immediately shows whether the VPN helps or hurts for gaming NAT.
Quick NAT type troubleshooting summary
| Situation | Likely cause | Fix |
| Was Open, now Strict | IP changed; UPnP failed; router reset | Re-enable UPnP; update port forwarding static IP |
| Always been Strict | UPnP off or double NAT | Enable UPnP; check for double NAT (tracert) |
| Router IP is private (10.x or 192.168.x) | CGNAT — ISP-level NAT | Request public IP from ISP; gaming VPN |
| Open on console, Strict on PC | Windows Teredo/Xbox or firewall | Fix Teredo; check Windows Firewall |
| Strict on one game only | Game-specific ports not forwarded | Forward game-specific ports |
Open NAT for home gamers is achievable in most situations by enabling UPnP. The few situations where it isn’t (CGNAT, managed networks) require either ISP-level changes or accepting moderate NAT as the realistic ceiling. The tracert test for double NAT and the WAN IP check for CGNAT are the two diagnostic steps that quickly identify whether you’re in a fixable situation or an ISP/network limitation.
Port triggering as an alternative to port forwarding
Port triggering is a router feature that dynamically opens inbound ports when a specific outbound port is used — without needing a static IP. This is useful for NAT type issues when DHCP IP assignment makes static port forwarding impractical and you don’t want to assign a static IP.
In the router admin: Port Triggering → create rules where the “trigger port” is an outbound port the game uses, and the “forwarded port” is the inbound port to open. When the game sends traffic out the trigger port, the router automatically opens the forwarded port. Port triggering is more secure than static port forwarding because ports are only open when the game is active, and it works without a static IP.
Checking current NAT type quickly
To see the current NAT situation on Windows without launching a game:
netsh interface teredo show state
Look at “State” — should be “Qualified.” If “Error”: Teredo is broken. Also:
ipconfig /all
Look at the “Default Gateway” for your network adapter. This is your router’s IP. Navigate to that IP in a browser to access the router admin. Simultaneously: the WAN IP in the router admin (usually under Status or WAN settings) tells you whether you have a public IP or are behind CGNAT.
These two commands give you the information needed to diagnose NAT type issues in under 2 minutes — without needing to launch any game.
A note for apartment buildings and student residences: shared network infrastructure frequently uses CGNAT or managed NAT that gives all residents Strict or Moderate NAT with no ability to change it. In these environments, the only practical options are a gaming VPN with a dedicated IP, or the mobile hotspot workaround (using a 4G/5G mobile hotspot as the internet connection — mobile networks often provide better NAT types for gaming than managed building networks, though with higher latency on some networks). The limitations are infrastructure-level and no amount of router or Windows configuration changes them.
Understanding CGNAT is genuinely useful knowledge for any gamer — ISPs have been increasingly using it to conserve IPv4 addresses since approximately 2018, and it explains many “why is my NAT strict no matter what I do” frustrations that were previously mysterious. If the WAN IP check reveals CGNAT: the conversation moves from Windows or router configuration to an ISP conversation, which is the most productive path to actually getting Open NAT for the cases where it’s possible. See also Why Internet Drops When Gaming for a related case.







