Gaming & speed

How to Change Your NAT Type to Open (PS5, Xbox, PC)

How to change NAT type from strict or moderate to open on PS5, Xbox and PC: test it first, then fix UPnP, port forwarding, double NAT or CGNAT, in that order.

In this guide

To change your NAT type to open, give your router one way to accept incoming game traffic: turn on UPnP, or forward your platform’s documented ports to a reserved address for the console, and make sure only one device performs NAT. If your provider uses CGNAT, no router setting can open it; ask for a public IP or use IPv6.

Test it now

Cloudflare edge
IP websites see216.73.216.115
LocationColumbus, United States
Internet providerAnthropic, PBC

Read at the Cloudflare edge from this request. The homepage adds your provider, network type and the VPN, DNS and WebRTC checks.

Show details

What NAT type measures

NAT type is a label for how your router treats traffic that other players send to you. The router shares one public IPv4 address among every device at home by rewriting addresses and ports on the way out and remembering the mapping on the way back (the guide to what NAT is covers the mechanism). Multiplayer games connect players directly, so what matters is whether a packet from a player you have never contacted can reach your console through that mapping.

RFC 4787, the IETF’s behavioral requirements for NATs, splits this into two properties. Mapping behavior: does the router reuse the same public port for a console’s socket regardless of destination (endpoint-independent mapping, which RFC 4787 says a NAT “MUST” have), or allocate a new one per destination address or port (address- or address-and-port-dependent mapping, often called symmetric NAT)? Filtering behavior: who may send packets to that mapped port: anyone (endpoint-independent filtering, which RFC 4787 recommends when application transparency matters most), only addresses the console already contacted, or only exact address-and-port pairs it contacted? Consoles and games probe these properties with STUN servers (RFC 8489: a way for an endpoint “to determine the IP address and port allocated to it by a NAT”) and translate the result into a label:

  • Xbox: Open, Moderate, Strict, or Unavailable. Microsoft’s definitions: Open lets you play and host with people of any NAT type; Moderate means you might not be able to play with some people and normally will not be chosen as host; Strict means you can only play with people who have Open NAT and cannot host; Unavailable means party chat and some multiplayer titles do not work at all.
  • PlayStation: Type 1, 2 or 3. Sony’s user guide defines Type 1 as a system connected directly to the internet, Type 2 as connected through a router, and Type 3 as connected through a router with limits, where communication with other PlayStation systems might be impossible.
  • Nintendo Switch and Switch 2: A through F. Nintendo says A is preferred and B is compatible with most other types, C may have difficulty with more restrictive types, D can generally only connect to players with type A, and F makes connecting to other players impossible.
  • Windows PC: no single label. Each game or launcher measures the same properties itself; Steam documents the UDP ports its peer-to-peer networking and voice chat need (in the table below).

What is the NAT type on my PC or console? Check it now

Measure before you change anything, because each fix below targets a different cause.

  1. Run the NAT type test from any device on the same network, including the PC you game on. It uses WebRTC to ask CheckMyIP’s own STUN server how your NAT maps addresses and ports from several angles and reports your public UDP address, the mapping behavior (endpoint-independent, or address- or port-dependent), whether your port number was preserved, whether a NAT is present and whether carrier-grade NAT was detected, with the equivalent Xbox, PlayStation and PC/Switch labels. Because a browser cannot ask a second server address to send a packet, it cannot measure filtering, which is what separates open from moderate; the page says so rather than guessing.
  2. Run the console’s own test, which does measure filtering. On Xbox: press the Xbox button, then Profile & system > Settings > General > Network settings; the NAT Type field sits under Current Network Status, and Test NAT type re-runs it. Note any extra message such as “Double NAT detected” or “UPnP not successful.” On PlayStation, the Test Internet Connection screen reports NAT Type 1, 2 or 3. On Switch, Nintendo’s steps are HOME Menu > System Settings > Internet > Test Connection, and the results include the NAT type letter and your global IP address.
  3. Read the two results together. Address- or port-dependent mapping or a CGNAT detection from CheckMyIP means the router or the provider, not a closed port, is the cause; endpoint-independent mapping with a console still reporting Strict or Type 3 points at filtering, which UPnP or a port forward fixes.

The test talks only to CheckMyIP’s STUN server, candidates stay in your browser, and nothing is stored.

Why is my NAT type strict or moderate?

Five causes account for almost every strict result, and each needs a different fix.

  1. UPnP is off or failing. Consoles use UPnP to ask the router for a port mapping automatically. With it off, nothing opens the inbound path and the router’s default filtering applies. Microsoft’s troubleshooting makes it the first step once double NAT and a private WAN address are ruled out.
  2. The platform’s ports are closed. A router with UPnP off and no forwarding rule drops unsolicited inbound packets on the ports your console listens on.
  3. Double NAT. Two devices translate addresses in series, typically an ISP gateway plus your own router. A forward or UPnP mapping on the inner router opens a path only from the outer router’s private address, so the console reports Strict or “Double NAT detected.”
  4. CGNAT. Your provider shares one public address between many customers and performs NAT upstream of your router. RFC 6598 reserves 100.64.0.0/10 for the link between the carrier NAT and your equipment; a WAN address in that range, or any WAN address that differs from your public IP, means the inbound path ends at the provider. The guide to what CGNAT is lists the signs and the providers known to use it.
  5. A VPN or a mobile hotspot. A VPN tunnel ends at the VPN operator’s NAT, which usually accepts no inbound traffic unless the service offers port forwarding. A phone hotspot adds the phone’s NAT and, on many carriers, CGNAT behind it.

The Xbox “Unavailable” result and the “Can’t get a Teredo IP address” error are a separate case: the console could not obtain a Teredo address, which party chat needs. Microsoft’s fix is in the router’s IPv6 settings (set Allow Teredo tunneling or Allow IPv6 tunneling to Yes; if the error persists, set Enable IPv6 to No), then Test multiplayer connection.

Fix 1: turn on UPnP (and when you should not)

UPnP lets a device on your LAN ask the router to map a public port to itself (the UPnP Internet Gateway Device specification, published by the Open Connectivity Foundation, defines the WANIPConnection service used for such requests). It is the reason most consoles reach Open or Moderate without any configuration.

  1. Log in to your router and find UPnP (usually under Advanced, NAT, or Applications and Gaming). Turn it on and save.
  2. If it is already on, Microsoft’s procedure for refreshing the NAT table is: turn UPnP off, save, power-cycle the router and modem (unplug for 10–20 seconds), confirm UPnP is off, turn it back on, save, and restart the network hardware again. If the router has a Zero Config setting, turn that on too.
  3. Restart the console from a full shutdown and re-run its NAT test.

Microsoft’s warning applies whichever path you take: do not combine port forwarding, UPnP and DMZ settings for the same console. Pick one.

When not to use it: any device on the LAN can open ports with UPnP, including a compromised one, so on a network with many untrusted devices a manual forward for the console alone is the more conservative choice. UPnP also cannot help when the ports it opens lead nowhere, which is the double NAT and CGNAT cases below.

Fix 2: forward the ports your platform uses

A port forward tells the router to send inbound traffic on given ports to one internal address; the guide to what port forwarding is walks through a typical router’s screens. The ports below are copied from the platform vendors’ own pages.

Platform (source)TCPUDP
Xbox console (Xbox Support, network ports)3074, 53, 8088, 3074, 53, 500, 3544, 4500; 9002 only if remote play fails on Strict NAT
PS5 (PlayStation Support, CE-106444-9)80, 443, 3478, 3479, 34803478, 3479, 49152–65535
Nintendo Switch and Switch 2 (Nintendo Support)none listed1024–65535
Steam client (Steam Support)80, 443, 27015–27050 remote; 27036 local (Remote Play)27000–27250 remote (game traffic), 27015–27050 remote, 27031–27036 local (Remote Play), 4380 remote
Steamworks P2P networking and Steam voice chat (Steam Support)none listed3478, 4379, 4380, 27014–27030 remote

Reading the table: Nintendo asks for the 1024–65535 UDP range, which opens nearly every UDP port to the console and is a reason to prefer UPnP on a Switch; Valve says the Steam ports “can not be re-mapped to HTTP or reconfigured to a custom port range”; Microsoft notes that individual games may need additional ports and that a second Xbox on the same network needs an alternate port in place of 3074.

To set it up: log in to the router, open the port forwarding page (also called virtual server, applications and gaming, or firewall pinholes), create one rule per row with the protocol, the port or range and the console’s LAN address, then save and reboot the router. Verify from outside with the open port checker, which connects from CheckMyIP’s server to your own public address on the ports you list; a TCP port such as 3074, 3478 or 80 showing open proves the forward reaches the console. The checker is TCP-only. UDP ports, which carry most game traffic, cannot be verified with a connect test, so for those the console’s own NAT test is the proof.

Fix 3: give the console a fixed address (DHCP reservation)

A forward points at an address. If the router hands the console a different address after a reboot, the rule silently stops matching, which is a common reason a NAT type that was open last month is strict today. Microsoft’s advice is to use the router’s DHCP reservation function when available: in the DHCP or LAN section, add the console’s MAC address in the reserved section so that it always receives the same address. The console’s MAC address and current address are shown in its network settings, and the local IP page explains how to read the LAN address on each system and why it is in a 192.168.x, 10.x or 172.16–31.x range.

If the router has no reservation feature, set the address on the console instead. Microsoft’s procedure for Xbox: read the subnet mask, default gateway and DNS servers from a PC with ipconfig /all, pick an unused address in the same range (Microsoft suggests the PC’s address plus 10), then on the console go to Profile & system > Settings > General > Network settings > Advanced settings > IP settings > Manual, enter the address, subnet mask and gateway, and set DNS to Manual with the same servers. Nintendo’s equivalent for Switch is a manual IP in the network’s advanced settings: another device’s address with 20 added to the last group (30 or 40 if the connection test fails), plus the same subnet mask and gateway. Then update the forwarding rule to the new address.

Fix 4: remove double NAT (bridge or access-point mode)

If the console reports “Double NAT detected,” or your router’s WAN address is a private one, two devices are translating (the double NAT guide has the three checks and the per-provider bridge-mode steps). Microsoft’s instructions are to remove one of them: first try putting the ISP gateway into bridge mode, which each manufacturer and provider handles differently; if that is not possible, change your own router to work only as an access point, which removes it as a NAT. Google gives the same two options for Nest Wifi, and NETGEAR’s guidance for Orbi and Nighthawk prefers bridge mode on the gateway with AP mode on the NETGEAR router as the alternative.

To confirm which case you are in, compare two addresses. Log in to the router and read the WAN or Internet IP on its status page, then open the IP lookup, which pre-fills your public address and shows the network it belongs to. If they match, your router holds the public address and open NAT is achievable with the fixes above. If the WAN address is in a RFC 1918 private range (10.0.0.0–10.255.255.255, 172.16.0.0–172.31.255.255, 192.168.0.0–192.168.255.255), another router (yours or the provider’s gateway) is in front; if it is in 100.64.0.0–100.127.255.255 or is any other address that differs from your public IP, go to Fix 5.

After bridging or switching to access-point mode, restart the console and the network hardware and re-run the NAT test; Microsoft’s instruction is to check that the Double NAT message is gone before trying anything else.

Fix 5: behind CGNAT? Ask for a public IPv4 or rely on IPv6

When the provider performs the NAT, inbound traffic stops at its equipment and nothing you forward on your router is reachable. Microsoft’s guidance is direct: if the address your router receives is private, open NAT is not possible under the current configuration, and you need to contact the ISP to request a public IP address. The alternative is IPv6, which gives each device a globally unique address with no translation. Whether that helps depends on the game: for Switch, Nintendo suggests the opposite step, turning IPv6 off, for NAT types D and F, so test per platform.

A third option is a VPN service that offers port forwarding, which moves the inbound path to the VPN operator’s address; that trades trust and latency rather than fixing anything.

DMZ, which routers also call a perimeter network, is the last resort and only on a router that holds a public address. Microsoft describes it as moving the console outside the router’s firewall so that every inbound port reaches it, requires a fixed address on the console first, and repeats that it must not be combined with UPnP or port forwarding; if DMZ produces Open NAT where UPnP did not, Microsoft’s reading is that UPnP on that router was not working. Behind CGNAT, DMZ changes nothing, because the traffic never arrives at your router.

Which NAT type is best for gaming, and what Open changes in practice

Open is best, Moderate is acceptable, Strict is the one to fix. The difference shows up in three places. Hosting: Microsoft says an Open console can host for anyone, a Moderate one is normally not chosen as host, and a Strict one cannot host. Matchmaking: two Strict players cannot connect to each other at all, and Nintendo’s rule of thumb is that type D connects only to type A, so a lobby of players with poor NAT shrinks to those with open ones. Voice: Xbox party chat depends on the same path, which is why a Strict console often means missing voices rather than a failed game.

Open does not make the connection faster or reduce lag by itself. It removes refused connections and lets a game use a direct path instead of a relay where it supports one, which is why the symptoms of a bad NAT type are empty lobbies, failed invites and dropped parties rather than low speed.

Sources

Questions

Should NAT be enabled on my router?

Yes. NAT is what lets every device share your one public IPv4 address; a home router cannot connect your LAN to the internet without it. A strict result is not a reason to turn NAT off but to let game traffic in through UPnP or a port forward, and to remove any second layer of NAT in front of it.

How do I change NAT type 3 to 2?

Type 3 means your PlayStation sits behind a router that rejects unsolicited inbound traffic. Turn on UPnP, or forward Sony’s documented ports (TCP 80, 443, 3478–3480; UDP 3478, 3479, 49152–65535) to a reserved address for the console, remove any double NAT, then re-run Test Internet Connection. Type 1 needs a public IP on the console itself.

How can I check my NAT type online?

Run the test at https://checkmyip.com/nat-type-test from a device on the same network. It asks CheckMyIP’s own STUN server how your NAT maps addresses and ports, reports endpoint-independent (open-style) or address/port-dependent (strict-style) mapping, and detects CGNAT. It cannot measure the open-versus-moderate filtering that consoles test, so confirm with the console’s own test.