If your console shows a strict NAT type, enable UPnP on your router first. Log in to your router, switch UPnP on, restart the router and the console, then test your NAT type again. UPnP fixes most strict NAT problems at home. If it does not work, check for double NAT and a shared provider address, then forward the ports for your platform.
What a strict NAT type means
NAT stands for Network Address Translation. Your router uses it to share one public internet address between every device in your home. It also blocks incoming connections that no device asked for. That blocking protects your home network, but it can break the peer to peer connections that games use for party chat, invites and hosting lobbies.
Strict NAT does not mean your internet is slow. It means other players struggle to connect to you. You may fail to join friends, host a lobby, or hold a stable party chat. Matchmaking can also take longer.
| Connection | PlayStation label | Xbox label | What happens |
|---|---|---|---|
| Open | Type 1 | Open | You can connect to any player and host games. |
| Moderate | Type 2 | Moderate | Most connections work. Some strict players cannot join you. |
| Strict | Type 3 | Strict | Only open players can connect to you. Party chat and hosting often fail. |
Type 2 is the normal target for a console behind a home router. You do not need Type 1. Aim for Type 2 on PlayStation or Open on Xbox, and stop there.
Check your NAT type first
On PS5, go to Settings, then Network, then Connection Status, then View Connection Status. Note the NAT Type shown. On Xbox Series X, Xbox Series S and Xbox One, go to Profile and system, then Settings, then General, then Network settings. Your NAT type shows on that screen, and you can select Test NAT type to refresh it.
On PC there is no single NAT reading. Many games show it in their own network settings. If the game reports a stricter type, trust the game reading. Check server status first. No router setting fixes an outage.
Fix strict NAT in this order
Work through these steps one at a time and test after each change.
1. Restart the router and the console
Switch the console off fully, not into rest mode. Switch the router off, wait 30 seconds, then switch it back on. Wait until the internet light is steady, then start the console and test again.
2. Enable UPnP
UPnP stands for Universal Plug and Play. It lets your console ask the router to open the ports it needs, automatically, and close them when it finishes. For most homes this single setting moves strict NAT to moderate or open.
Log in to your router using the address on its label, usually 192.168.1.1, 192.168.0.1 or 192.168.1.254. Use the admin login on the label, not your Wi-Fi password. Find UPnP under Advanced Settings, Firewall, or Network Settings. Switch it on, save, restart the router and the console, then test again.
UPnP carries a small security trade off, but the risk is low on a normal home network with trusted devices. It is far safer than the DMZ option below. If you forward ports by hand, you do not need UPnP as well. Use one method, not both.
3. Check for double NAT and a shared provider address
This step explains why port forwarding sometimes does nothing at all. Double NAT means two routers are translating your connection in turn. It happens when you plug a mesh Wi-Fi system or a second router into your provider router without putting one of them in bridge mode or modem mode. Xbox often reports this directly as double NAT detected. Fix it by putting your provider router in bridge mode or modem mode.
A shared provider address causes a similar dead end. Some providers use Carrier Grade NAT, known as CGNAT, where many homes share one public address. Sky full fibre can also use a similar sharing method called MAP-T on some connections. Under either setup, port forwarding on your own router cannot work. Test for it by comparing the WAN address in your router settings with the public address shown by a site such as whatismyip.com. If they differ, you are behind provider level sharing. Ask your provider for a public IPv4 address. No new gaming router fixes this.
4. Reserve an address and forward the ports
Only forward ports by hand if UPnP did not work and you have ruled out double NAT and a shared address. Port forwarding points traffic at one device, so that device needs a fixed local address first. In your router settings, find DHCP reservation or static lease. Bind your console to one address, then restart it so it picks up that address.
Then create port forwarding rules for your platform, pointing at that reserved address:
| Platform | Ports to forward |
|---|---|
| PlayStation Network | TCP 80, 443, 3478 to 3480 and UDP 3478 to 3479 |
| Xbox network | TCP 53, 80, 3074 and UDP 53, 88, 500, 3074, 3544, 4500 |
Save the rules, restart the router and the console, then test again. Forward each port to one device only. If two consoles play the same game in one house, use UPnP instead.
5. Use the DMZ only as a last resort
The DMZ, or demilitarised zone, opens every port to one device and bypasses most of the router firewall for that device. Only use it for a games console, never for a PC, and only after UPnP and port forwarding have failed.
UK router settings: BT, Virgin Media and Sky
UK provider hubs hide the same settings in different places. Use this table as your starting point.
| Provider hub | Router address | Where to find the settings |
|---|---|---|
| BT Smart Hub | 192.168.1.254 | Hub Manager, then Advanced Settings, then Firewall. UPnP and port forwarding both live under Firewall. |
| Virgin Media Hub 3, Hub 4 and Hub 5 | 192.168.0.1 | Advanced Settings, then Security, then Port Forwarding. On the older Hub 3 the path is Advanced Settings, then Port Forwarding. |
| Sky Broadband Hub | 192.168.0.1 | Advanced, then UPnP, to switch UPnP on. For port forwarding, use Security and the firewall rules for your hub. On newer Sky hubs some settings sit in the My Sky app or website. |
BT broadband does not normally use CGNAT, so BT customers can usually fix strict NAT with router settings alone. Virgin Media and Sky customers should run the WAN address check above first.
What strict NAT will not fix
Strict NAT is a connection problem, not a speed problem. Fixing it will not lower your ping or speed up downloads. If players teleport or shots register late, read our guide to fixing lag on PS5. If downloads crawl, read our guide to speeding up slow PS5 downloads. If controls feel delayed while the picture stays smooth, see our guide to reducing input lag in gaming. A VPN also does not fix router NAT for a console.
FAQs
Will a strict NAT type slow down my downloads?
No. NAT type controls who can connect to you, not how fast data moves. Slow downloads come from Wi-Fi, shared bandwidth, busy servers, or peak time congestion.
What NAT type should I aim for on PS5?
Type 2. It is the normal result for a console behind a home router, and it supports online play, party chat and hosting. Type 3 is the one to fix.
Is the DMZ safe for my console?
It is safer than putting a PC in the DMZ, but it still exposes the console to direct internet traffic. Use it only as a last resort, only for the console, and remove it when you no longer need it.
Why does port forwarding not change my NAT type?
The most common reasons are double NAT, a shared provider address, or rules pointing at the wrong local address. Run the WAN address check first. If your router WAN address differs from your public address, no rule on your router can fix it. Ask your provider for a public address.
Conclusion
Restart first, switch on UPnP, then check for double NAT and a shared provider address before you touch port forwarding. Forward only the ports your platform needs, and keep the DMZ as a last resort. Once your console reports Type 2 or Open, stop changing settings and get back to playing.
About the Author
