PortCheckPortCheck
← All guides

Port Forwarding for Gaming Consoles

Fixing strict NAT and multiplayer connection issues on Xbox, PlayStation, and Switch

Console multiplayer relies heavily on peer-to-peer connections for voice chat and some game sessions, which makes it far more sensitive to NAT and firewall configuration than a typical web request. When a console reports a “strict” or “Type 3” NAT type, it usually means incoming connections from other players are being blocked somewhere between the console and the internet — most often at the router. Forwarding the correct ports is the standard fix.

Console Port Reference

Xbox (Xbox Live)

  • 88UDP
  • 500UDP
  • 3074TCP/UDP
  • 3544UDP
  • 4500UDP

PlayStation Network

  • 3478–3480TCP/UDP
  • 443TCP
  • 80TCP

Nintendo Switch

  • 1–65535UDP (for a single console, per Nintendo’s own guidance)
  • 6667TCP
  • 12400TCP/UDP
  • 28910TCP/UDP

Manufacturers periodically update these lists as services change — always cross-check the current official support page for your platform before finalising a firewall rule.

Step 1: Give the Console a Static Local IP

Exactly as with any other port-forwarding setup, reserve a fixed local IP address for the console — either through your router's DHCP reservation feature or a static IP configured on the console itself — before creating any forwarding rules. See our port forwarding guide for the general process.

Step 2: Forward the Ports Above

Create a forwarding rule for each port or port range listed for your platform, pointing to the console's reserved local IP, using the protocol specified (TCP, UDP, or both). Consoles frequently need both — forwarding only TCP when UDP is also required is a common reason the NAT type doesn't improve after forwarding.

Step 3: Consider Using DMZ Only as a Last Resort

Some router manufacturers suggest placing the console in the router's “DMZ”, which forwards essentially all inbound ports to that device. This works but removes the router's firewall protection entirely for that device — targeted port forwarding is safer and should be tried first.

Step 4: Verify the TCP Ports

The TCP-based ports in the tables above (such as PlayStation's 443 and 80, or Xbox's 3074) can be verified directly: enter the port on PortCheck and confirm it shows as reachable. UDP ports cannot be verified the same way — see our guide on the difference between TCP and UDP for why, and rely on the console's own NAT type test for those.

If the NAT type still shows as strict after forwarding every port correctly, double check for Carrier-Grade NAT (CGNAT) — no forwarding rule can fix that on its own.