Black Ops 2 PS5 Friends Can’t Join Each Other? NAT Type 2 Isn’t Always the Problem

Trying to play Black Ops 2 with friends on PS5, but neither of you can join the other's lobby?

You may see:

- “Unable to Join Session”

- the invitation does nothing

- the game briefly freezes and returns to the menu

- PlayStation shows you in the same game group, but BO2 does not put you in the same lobby

- public matches work, but joining a specific friend does not

- PS5 says NAT Type 2, while BO2 shows Moderate or even Strict

If that sounds familiar, don't immediately assume your NAT Type is the problem.

Recent Black Ops 2 PS5 players have reported this exact combination of symptoms, including cases where both players could play public matches normally but could not join one another. Some players also reported that changing the ISP's IPv4 configuration solved the problem, while others found that different joining methods, UPnP, the PS4 version, or simply restarting the game changed the result.

The important part is figuring out which type of BO2 connection problem you actually have.

---

Black Ops 2 PS5 Friends Can't Join Each Other: The Quick Answer

If you and your friend:

- can both play public matches,

- both appear online,

- have PS5 NAT Type 2,

- but cannot join each other's private lobby,

then your internet connection is not automatically the problem.

Start with these tests:

1. Make sure both players appear Online.

2. Try joining through the in-game friends list.

3. Have the host start matchmaking, stop searching, and then try the join again.

4. Completely restart BO2 on both consoles.

5. Test who can host successfully.

6. Compare the BO2 NAT status on both consoles.

7. Test a different internet connection if possible.

8. Check whether one player's router is behind CGNAT or another restrictive IPv4 configuration.

9. Test the PS4 version if available.

10. If the problem affects only one specific friend, don't assume the whole BO2 service is down.

---

Why Can You Play Public Matches but Not Join Your Friend?

This is one of the most confusing parts of the BO2 PS5 problem.

You might think:

«“If I can play multiplayer, my connection must be fine.”»

Not necessarily.

There is a difference between finding a public match and establishing a direct connection to a particular player's lobby.

Recent players have reported being able to find public games normally while being completely unable to join a specific friend's session.

That gives us an important diagnostic clue.

If public matchmaking works:

Your PS5 is capable of reaching BO2's online environment.

If joining one specific friend fails:

The problem may involve the connection path between the two players, NAT compatibility, router configuration, IPv4/CGNAT, or a BO2 session/party bug.

That's why simply testing another public match isn't enough.

---

1. Make Sure Both Players Appear Online

This is extremely simple, but older multiplayer games can behave strangely when the PlayStation presence information and the game's own friend/session information don't line up.

Before changing your router:

Player A

Check that your PS5 status is:

Online

Player B

Do the same.

Then completely close BO2 on both consoles and launch it again.

Some players have reported that being shown as offline prevented friend joining, although this isn't a universal fix.

It costs nothing to test.

---

2. Try Joining Through BO2's In-Game Friends List

Don't rely exclusively on the PS5 notification.

Open Black Ops 2 and look at the game's own friends/session options.

If your friend appears as joinable:

Select the friend → Join Game Session

Some recent players specifically reported that joining through the in-game friends list worked better than accepting a normal PS5 invitation.

However, other players have reported the opposite behavior.

That's why we're testing methods rather than calling one method a guaranteed fix.

---

3. Have the Host Start Searching — Then Stop

This is one of the stranger community-discovered workarounds.

Try this:

Player A — Host

1. Enter Multiplayer or Zombies.

2. Start searching for a public game.

3. Let the search begin.

4. Stop searching.

5. Return to the lobby.

Player B

Immediately try:

Join Game Session

Some players report that this can refresh the game's session state and allow the friend to connect.

It sounds random, but it is worth testing before touching your router.

---

4. Test Who Can Host

This is one of the most useful diagnostic tests.

Don't just try the same person repeatedly.

Test A

Player A hosts.

Player B joins.

Test B

Player B hosts.

Player A joins.

Now compare the results.

Example

If:

A → B = fails

but:

B → A = works

then the problem is probably not simply “BO2 doesn't work.”

You've identified a directional connection problem.

That makes the host's network configuration much more important.

---

5. Don't Confuse PS5 NAT Type 2 With BO2's NAT Status

This is a big one.

Your PS5 may report:

«NAT Type 2»

while Black Ops 2 may show:

«Moderate»

or:

«Strict»

Those are not necessarily the same measurement.

PS5 NAT Type 2 generally means the console is connected through a router and has normal internet access.

It does not guarantee that every older peer-to-peer game can establish a connection with every other player.

So don't conclude:

«“I have NAT Type 2, therefore NAT cannot be involved.”»

It can still be relevant.

---

6. Compare Both Players' BO2 NAT Status

Have both players check the NAT information shown inside Black Ops 2.

Write down the results.

For example:

Player| PS5 NAT| BO2 NAT| Can Host?

Player A| Type 2| Moderate| Yes

Player B| Type 2| Moderate| No

If both players have identical-looking NAT results but still cannot connect, don't automatically keep changing NAT settings.

Recent reports include players with Moderate NAT on both sides who still could not join each other.

That is why NAT is only one part of the diagnosis.

---

7. Restart BO2 — But Restart It Properly

Don't just return to the PS5 dashboard and immediately reopen the game.

For both players:

1. Exit BO2.

2. Highlight BO2 on the PS5 home screen.

3. Press the Options button.

4. Select Close Game.

5. Wait a few seconds.

6. Launch BO2 again.

7. Re-enter the lobby.

8. Test the friend connection again.

Players have reported that restarting the game can sometimes clear the session problem, although it isn't reliable for everyone.

---

8. Try the PS4 Version If You Have Access to It

This is an important diagnostic test for players experiencing problems specifically with the native PS5 version.

Some players reported that switching to the PS4 version allowed them to join friends when the PS5 version would not. Others reported that the PS4 version did not solve their particular problem.

That difference is important.

If PS4 version works:

The problem may be related to the PS5 version/session implementation.

If PS4 version also fails:

Your network, account, or the specific player-to-player connection becomes more suspicious.

Don't treat the PS4 version as a guaranteed permanent solution. Use it as a diagnostic test.

---

9. Try a Different Internet Connection

This is one of the strongest tests you can perform.

If possible, have one player temporarily use:

- mobile hotspot

- another Wi-Fi connection

- another ISP

- a different home network

Then try joining again.

If it suddenly works

Your normal home connection becomes a serious suspect.

If it still fails

The problem is less likely to be your ISP alone.

This is especially useful because recent BO2 players have reported both successful and unsuccessful hotspot tests, meaning the result can vary depending on the actual network involved.

---

10. Check Your Router's WAN IPv4 Address

If one player can host but another cannot connect, investigate the router's internet-facing IPv4 address.

Log into your router and find the:

WAN IP / Internet IPv4 / Public IP

If it begins with:

100.64.x.x – 100.127.x.x

you may be behind Carrier-Grade NAT (CGNAT).

CGNAT means your ISP is sharing public IPv4 addresses between customers.

That can make inbound peer-to-peer connections more complicated.

---

11. Why CGNAT Can Matter in BO2

Imagine:

Player A → ISP → Internet

and:

Player B → ISP → Internet

If one player's router doesn't have a directly reachable public IPv4 address, establishing certain peer-to-peer connections can become more difficult.

This is especially relevant for older games that rely heavily on peer-to-peer networking.

But again:

CGNAT is not automatically the explanation.

You need to test it.

---

12. A Real 2026 Example: Public IPv4 Fixed BO2 Joining

This is one of the most interesting reports we've found.

A BO2 PS5 player reported that their ISP connection was using a 100.x.x.x WAN IPv4 address.

They contacted the ISP and had the connection changed to a public IPv4 address.

According to the player's report, they were then able to join their friend directly in BO2.

That's not proof that public IPv4 will fix every BO2 player.

But it gives us a very useful diagnostic clue.

If you're behind CGNAT and BO2 friend joining consistently fails, asking your ISP about a public IPv4 address may be worthwhile.

---

13. What to Tell Your ISP

Don't tell your ISP:

«“Black Ops 2 doesn't work.”»

That may not get you very far.

Instead, ask:

«“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?”»

If they provide a public IPv4 address, test BO2 again.

---

14. Check UPnP Before Manually Forwarding Ports

If your router supports UPnP, check whether it is enabled.

UPnP can allow the PS5 to automatically request the network mappings it needs.

Some BO2 players have reported that changing UPnP settings resolved their friend-joining problems.

But don't blindly change every router setting.

If BO2 works normally with other players, you don't necessarily need to rebuild your entire network.

---

15. What If You and Your Friend Live in the Same House?

This is an especially interesting case.

Two PS5 consoles on the same home network can sometimes have their own connection problems with older peer-to-peer games.

A recent BO2 report described two players on the same network who could not join each other, even though they could play other games together. The players discovered a strange workaround involving launching another Call of Duty title, joining each other there, closing it, and then launching BO2.

This is not an official BO2 fix.

We don't know exactly why it worked.

But if two players are on the same network and BO2 alone refuses to connect them, it is another clue that the issue may involve session/network handling rather than internet speed.

---

16. Don't Keep Changing NAT Type Just Because Someone Says “Open NAT”

You will find plenty of comments saying:

«“You need Open NAT.”»

That's sometimes useful, but it isn't the whole story.

Recent players have reported:

- Moderate + Moderate failing

- Type 2 + Moderate failing

- different NAT configurations working inconsistently

- public IPv4 fixing a connection

- PS4 working while PS5 doesn't

- one friend being able to host while another cannot

So if you've already tested the obvious NAT differences, don't spend hours randomly changing router settings.

Move to the next diagnostic test.

---

17. The Most Useful Test: Can Other Friends Join?

Suppose you have three players:

A, B and C

Try:

- A → B

- B → A

- A → C

- C → A

- B → C

- C → B

This sounds excessive, but it can reveal the pattern.

If nobody can join anybody

Look at the broader service/network situation.

If A can join everyone except B

B's connection, account/session state or network becomes more suspicious.

If B can host but cannot join

This may indicate a directional connection issue.

If everyone can play public matches but private joining fails

Focus on BO2 party/session behavior rather than internet speed.

---

18. Don't Assume the Entire BO2 Service Is Down

This is another common mistake.

If your friend cannot join you, that doesn't necessarily mean:

«“BO2 servers are down.”»

If public matchmaking continues working for you, the game is clearly communicating with its online services.

The problem may be specifically the player-to-player session.

That's why testing public matches, hosting direction and friend joining separately is so important.

---

19. A Strange Workaround: Use Another Call of Duty Session

There is one community-reported workaround that is unusual enough to mention.

Two players who could not connect on BO2/BO3 while on the same network reported:

1. Launch Infinite Warfare.

2. Join each other's lobby.

3. Close Infinite Warfare completely.

4. Launch BO2.

5. Try joining again.

They reported that the BO2/BO3 connection then worked repeatedly.

Important:

This is community-reported behavior, not an official Activision fix.

We don't know whether it changes some networking/session state or whether it is simply coincidence.

Try it only as a low-risk experiment.

---

20. What NOT to Do

Avoid random “BO2 networking fixes” that ask you to:

- download unknown DLL files

- install unofficial executables

- disable Windows or console security

- download suspicious patches

- enter your PSN credentials into third-party tools

- install random VPN software

- forward dozens of unrelated ports

- factory-reset your router without a reason

If a “fix” requires downloading an unknown file from a random website, don't use it.

A multiplayer connection problem is not worth compromising your account or computer.

---

The 5-Minute Black Ops 2 PS5 Diagnosis

If you want the fastest possible route, follow this order:

Step 1 — Test public multiplayer

Can both players play normally?

Yes → basic BO2 connectivity works.

Step 2 — Test both hosting directions

A hosts → B joins.

B hosts → A joins.

Step 3 — Check status

Both players should appear Online.

Step 4 — Try in-game joining

Use BO2's Join Game Session option.

Step 5 — Restart BO2

Close the game completely on both PS5s.

Step 6 — Try another connection

Use a hotspot or different network if possible.

Step 7 — Check router IPv4

Look for a 100.64–100.127.x.x WAN address.

Step 8 — Check UPnP

Make sure UPnP is functioning if your router supports it.

Step 9 — Test PS4 version

If available, compare the PS4 and native PS5 versions.

Step 10 — Compare the result

Now you know much more about the problem than you did when you started.

---

Black Ops 2 PS5 Friend-Join Problem: What the Results Tell You

What happens| What it suggests

Public matches work, friend joining fails| Player-to-player/session problem

A can host B, but B can't host A| Directional/network compatibility issue

Both players cannot host each other| Network/session issue more likely

PS4 works, PS5 doesn't| PS5-version behavior may be involved

Different internet fixes it| Home network/ISP is suspicious

100.x WAN IPv4| Possible CGNAT

UPnP change fixes it| Router/NAT mapping may be involved

Everyone fails with everyone| Broader BO2/service/network issue

Only one specific friend fails| Connection/account/session relationship needs investigation

---

So What Is Actually Causing the BO2 PS5 Problem?

There isn't one universal cause.

That's the important conclusion.

Recent player reports point toward several possible layers:

1. BO2 PS5 session/matchmaking behavior

Some players report that invitations simply do nothing or that joining repeatedly fails even with apparently normal NAT settings.

2. NAT compatibility

Moderate/Strict combinations can cause problems, but Moderate + Moderate can also fail.

3. ISP/IPv4 configuration

At least one recent player reported solving the issue by moving from a 100.x WAN address to a public IPv4.

4. Router configuration

UPnP and other NAT behavior can affect peer-to-peer connectivity.

5. PS4 vs PS5 version behavior

Some players report the PS4 version works when the native PS5 version doesn't. Others don't see any difference.

That is why the best fix depends on which symptom you have.

---

Final Answer: What Should You Try First?

If you're sitting on PS5 with NAT Type 2, BO2 shows Moderate, public matches work, but you can't join one particular friend, don't immediately buy a new router.

Start here:

1. Make both players appear Online.

2. Try joining through BO2's in-game friends list.

3. Test both hosting directions.

4. Completely restart BO2.

5. Try the host-search-then-stop method.

6. Test another internet connection.

7. Check the router's WAN IPv4.

8. If it is 100.x.x.x, ask your ISP about CGNAT/public IPv4.

9. Check UPnP.

10. Compare the PS4 and PS5 versions if available.

Most importantly, don't assume NAT Type 2 means your network cannot be involved — and don't assume every failed BO2 friend connection is caused by NAT either.

The pattern of the failure tells you much more.

---

Frequently Asked Questions

Why can't I join my friend on Black Ops 2 PS5?

The cause can vary. Recent players have reported BO2 session problems involving NAT compatibility, router/IPv4 configuration, the PS5 version, and inconsistent friend-session behavior.

Why does Black Ops 2 say “Unable to Join Session”?

The game is failing to establish the required connection to the friend's session. That can be caused by network compatibility, NAT/IPv4 configuration, or BO2's own session behavior.

Why can I play public matches but not join my friend?

Public matchmaking and direct friend-to-friend sessions are different connection scenarios. If public games work but one friend cannot join you, investigate the player-to-player connection rather than assuming your entire internet connection is broken.

Is NAT Type 2 good enough for Black Ops 2?

NAT Type 2 means your PS5 has normal internet access through a router, but it does not guarantee that every BO2 player can connect directly to your console.

Does changing to Open NAT fix BO2?

It can help in some situations, but it is not a guaranteed fix. Recent players have reported failed connections even with Moderate NAT on both sides.

Can CGNAT prevent Black Ops 2 friend joining?

It can make peer-to-peer connections more difficult. If your router has a 100.64–100.127.x.x WAN IPv4 address, ask your ISP whether you are behind CGNAT.

Does the PS4 version of BO2 work better?

Some players report that the PS4 version allowed them to join friends when the native PS5 version did not, but this isn't universal. Use it as a diagnostic test rather than a guaranteed fix.

Should I port forward BO2?

Don't start with extensive manual port forwarding. First determine whether the problem is actually your router/NAT configuration. If UPnP, public IPv4 and other basic network tests point toward your network, then more advanced router configuration may be appropriate.