PS5 NAT Type 2 but Black Ops 2 Says Strict? Here’s the Real Fix
Share
PS5 NAT Type 2 but Black Ops 2 Says Strict? Here’s the Real Fix
Your PS5 says NAT Type 2, your internet works normally, and other games may connect without problems — but when you launch Black Ops 2 on PS5, the game shows Strict NAT.
Then you try:
- UPnP
- Port forwarding
- Restarting the router
- Restarting the PS5
- Giving the PS5 a static IP
- DMZ
…and Black Ops 2 still says Strict.
If this sounds familiar, your PS5 itself may not be the problem.
The important thing to understand is that PS5 NAT Type 2 and Black Ops 2's in-game NAT status are not exactly the same test. Current player reports show that some players with PS5 NAT Type 2 are still getting Strict NAT inside BO2, with the underlying cause sometimes being the ISP's IPv4/NAT configuration.
This guide will help you find the actual cause instead of wasting hours changing random router settings.
---
The Quick Answer
If your PS5 shows NAT Type 2 but Black Ops 2 shows Strict, check these things in this order:
1. Forward UDP/TCP port 3074 to your PS5
2. Make sure your PS5 has a consistent local IPv4 address
3. Check whether your router's WAN IPv4 is a public IP
4. Look for CGNAT / 100.64.0.0–100.127.255.255
5. Test Black Ops 2 through a mobile hotspot
6. If the hotspot changes BO2 from Strict to Moderate/Open, contact your ISP
7. Ask your ISP whether you are behind CGNAT and whether they can provide a public IPv4 address
The key point:
«If your ISP is putting you behind CGNAT, changing port-forwarding settings on your own router may not solve the problem.»
---
Why Does PS5 Say NAT Type 2 While BO2 Says Strict?
This is the part that confuses almost everyone.
Your PS5 performs its own network connectivity test and reports a PlayStation NAT result.
Black Ops 2 performs its own connectivity checks for multiplayer communication.
So you can have:
PS5: NAT Type 2
Black Ops 2: Strict
That does not automatically mean your PS5 is broken.
PlayStation itself notes that PS5 networking can involve IPv4, IPv6, routers and other network configurations, and recommends contacting your ISP if you're not familiar with advanced network settings.
And current BO2 players are reporting exactly this combination.
---
Step 1 — Check Your PS5 NAT Type
On your PS5:
Settings → Network → Connection Status → Test Internet Connection
Check the result.
If you see:
NAT Type 2
that's not necessarily a problem by itself.
The important thing is what Black Ops 2 reports after you enter multiplayer.
---
Step 2 — Check Black Ops 2's NAT Status
Launch Black Ops 2 and enter multiplayer.
Check the NAT information.
If BO2 shows:
Strict
and you're having problems such as:
- Unable to join friends
- Unable to host
- Empty or limited lobbies
- Long matchmaking times
- “Unable to join session”
- Friends appearing online but being impossible to join
then continue with the steps below.
Recent PS5 players have reported these exact symptoms, including situations where both players could play public matches but could not join each other's lobby.
---
Step 3 — Try Port 3074 First
Before assuming you have CGNAT, test the simplest possible fix.
Black Ops 2 players have repeatedly reported improvements after forwarding port 3074 to the PS5. Some users reported going from Strict/Moderate to Open after forwarding 3074.
Log into your router and look for:
Port Forwarding / Port Mapping / Virtual Server
Create a rule for your PS5.
Black Ops 2
Setting| Value
Device| Your PS5
External port| 3074
Internal port| 3074
Protocol| UDP
Optional| TCP/UDP if your router requires a combined rule
Save the configuration and restart your router and PS5.
Important
Don't blindly add dozens of ports from random internet guides.
Start with the port specifically associated with BO2 multiplayer.
Some current community reports indicate that UDP 3074 is the important BO2-specific port, while other players have reported success with TCP/UDP 3074.
---
Step 4 — Make Sure Your PS5 Keeps the Same Local IP
Port forwarding only works correctly if the router knows which device should receive the traffic.
Your PS5 might have a local address such as:
192.168.1.25
or:
192.168.0.25
If that address changes later, your port-forwarding rule may point to the wrong device.
The better approach is to create a DHCP reservation for your PS5 in your router.
This tells the router:
«“Always give this PS5 the same local IP.”»
You usually do not need to manually configure every IP setting on the PS5.
---
Step 5 — Still Strict? Check Your Router's WAN IPv4
This is where the investigation gets interesting.
Log into your router and find its:
WAN IP / Internet IPv4 / Public IPv4
Do not confuse this with your PS5's local IPv4.
Your PS5 may have:
192.168.x.x
That's normal.
We're interested in the address your router receives from your ISP.
---
Step 6 — Look for CGNAT
If your router's WAN IPv4 begins with something like:
100.64.x.x
100.85.x.x
100.100.x.x
100.120.x.x
you may be behind Carrier-Grade NAT (CGNAT).
The CGNAT address range is:
100.64.0.0 – 100.127.255.255
This matters because your router is no longer receiving a directly reachable public IPv4 address.
Instead, your ISP may be putting multiple customers behind another NAT layer.
Your network can effectively look like:
PS5 → Router NAT → ISP CGNAT → Internet
Port forwarding on your home router only controls the first NAT layer.
It cannot magically open a port through the ISP's NAT.
---
The Real-World BO2 Example
This isn't just a theoretical networking problem.
In July 2026, a BO2 PS5 player reported having:
PS5 NAT Type 2
BO2 Strict NAT
They tried UPnP, port forwarding and DMZ without fixing it.
They then checked their router and found a 100.85.x.x WAN address, while their externally visible public IP was different.
After testing through a mobile hotspot, BO2 changed to Moderate NAT.
The player contacted their ISP, had CGNAT removed and received a public IPv4 address.
After that, Black Ops 2 worked normally.
Another player reported being unable to join a friend in BO2 despite both PS5 consoles showing Moderate NAT. They later reported that their ISP changed their connection from a 100.x.x.x WAN IPv4 to a public IPv4 address, after which direct joining worked.
That's why checking the ISP connection can be much more important than endlessly changing your PS5 settings.
---
Step 7 — The Mobile Hotspot Test
This is one of the easiest ways to determine whether your home ISP is responsible.
Temporarily connect your PS5 to a mobile hotspot.
Then launch Black Ops 2.
If BO2 changes from:
Strict → Moderate/Open
that's a very strong clue that your normal home internet connection is the problem.
One current BO2 player specifically reported using a mobile hotspot as a workaround while their normal ISP connection was behind CGNAT.
The hotspot isn't necessarily the permanent solution.
It's a diagnostic test.
---
Step 8 — Ask Your ISP the Right Question
Don't simply tell your ISP:
«“Black Ops 2 doesn't work.”»
That can lead to generic router instructions.
Instead, tell them:
«“Is my internet connection behind CGNAT? My router is receiving a 100.x.x.x WAN IPv4 address. Can you provide me with a public IPv4 address or remove CGNAT from my connection?”»
That's much more specific.
If your ISP offers public IPv4 access, ask whether it is:
- Dynamic public IPv4
- Static public IPv4
- Included with your plan
- Available as an optional service
You don't necessarily need a static IP just for gaming.
What matters is getting out of the problematic NAT arrangement.
---
What If I'm NOT Behind CGNAT?
Good news: CGNAT is not the only possible cause.
If your router has a genuine public IPv4 address, continue troubleshooting.
Check:
1. UPnP
Try enabling UPnP.
Then restart the router and PS5.
2. Port 3074
Verify that the forwarding rule points to the correct PS5 IP.
3. Double NAT
If you have:
ISP modem/router → your own router → PS5
you may have two NAT layers.
PlayStation specifically recommends removing multiple NAT routers when troubleshooting connection problems.
4. Router firewall
Some routers have additional firewall or security features that can interfere with incoming connections.
5. ISP-specific restrictions
Some ISPs use DS-Lite, CGNAT or other IPv4/IPv6 configurations that can affect older peer-to-peer games.
---
Should You Use DMZ?
DMZ is often suggested as the magic solution.
It isn't.
If you have a normal public IPv4 connection, putting the PS5 in the router's DMZ may sometimes change NAT behavior.
But DMZ will not remove ISP-level CGNAT.
If the router itself does not have a directly reachable public IPv4 address, your home router cannot forward an incoming connection through the ISP's NAT layer.
And if you do use DMZ, only expose the gaming console—not your entire network.
---
The Fastest Diagnostic Checklist
If you're stuck, use this:
PS5 says Type 2 + BO2 says Strict
↓
Forward port 3074
↓
Still Strict?
Check router WAN IPv4
↓
Is it 100.64–100.127.x.x?
YES → likely CGNAT
↓
Test mobile hotspot
↓
BO2 improves?
YES → contact ISP
↓
Ask for:
Public IPv4 / CGNAT removal
---
What NOT to Do
Don't spend hours changing:
- DNS
- MTU
- random ports
- dozens of port-forwarding rules
- random PS5 IP addresses
if the actual problem is ISP-level CGNAT.
And don't assume:
«“My PS5 says NAT Type 2, therefore my BO2 connection must be fine.”»
That is exactly the situation this guide is designed to explain.
---
Why This Problem Is So Confusing
Modern games often hide complicated networking behind matchmaking systems.
Black Ops 2 is different.
The current PS5 version is exposing networking problems that many players are encountering in different ways:
- Strict NAT
- Moderate NAT
- Empty lobbies
- Unable to join session
- Friends can't connect
- PS5 says NAT Type 2
- Router says something completely different
Community reports from July and August 2026 show that there isn't one universal fix. Some players solved BO2 NAT problems with port 3074, while others needed their ISP to change their IPv4/CGNAT configuration.
That's why the correct approach is diagnosis first, fix second.
---
Final Answer
If your PS5 says NAT Type 2 but Black Ops 2 says Strict, don't immediately assume your PS5 is broken.
Try 3074 port forwarding first.
If that doesn't work, check your router's WAN IPv4.
If the WAN address is in the 100.64.0.0–100.127.255.255 CGNAT range, your ISP may be creating the extra NAT layer that BO2 cannot work around properly.
The mobile-hotspot test can help confirm it.
And if the hotspot fixes the BO2 NAT problem, contact your ISP and ask for a public IPv4 address / CGNAT removal.
That is the fix many players are missing.
---
Frequently Asked Questions
Why is my PS5 NAT Type 2 but BO2 Strict?
Because the PS5's NAT result and Black Ops 2's own multiplayer NAT check are not necessarily measuring the same thing. Router configuration, port forwarding and ISP-level NAT can affect BO2 separately.
Does port forwarding 3074 fix BO2 Strict NAT?
It can. Multiple current player reports say forwarding port 3074 changed BO2 from Strict/Moderate to Open. However, it will not solve an ISP-level CGNAT problem.
Can CGNAT cause Strict NAT in Black Ops 2?
Yes. Current 2026 player reports specifically connect BO2 PS5 NAT problems with 100.x WAN addresses and ISP CGNAT.
How do I know if I'm behind CGNAT?
Check your router's WAN IPv4 address. If it falls within 100.64.0.0–100.127.255.255, it is within the address range reserved for carrier-grade NAT. Also compare your router's WAN IPv4 with the public IPv4 shown by an external IP-checking service.
Can a VPN fix CGNAT?
A VPN-based workaround may help in some configurations, but it can add latency and isn't the first solution I'd recommend. If your ISP can provide a public IPv4 address, that's the cleaner option.
Why can I play public matches but not join my friends?
Public matchmaking and direct peer-to-peer connections can behave differently. Current BO2 PS5 reports include players who could play public matches but received “Unable to join session” when trying to connect directly to friends.
---
Bottom Line
PS5 NAT Type 2 + BO2 Strict does NOT automatically mean you need more port forwarding.
Check the network path.
3074 → WAN IPv4 → CGNAT → mobile hotspot test → ISP
That's the troubleshooting path.
And if your router is behind CGNAT, stop fighting your router and talk to your ISP.