Fix: “Connection Failed. Networking failed to start [HUENEME – NEGEV]” Error in Black Ops 6

Black Ops 6 can stop at Waiting for networking and then show Connection Failed. Networking failed to start [HUENEME – NEGEV]. The game has not reached its online menus or created a usable online session.

The console or PC may still browse the web and run other online apps. Those checks do not prove that Call of Duty can complete its separate path through the platform service, the local firewall or router, and Activision’s network.

The code does not identify which of those layers stopped responding. The useful evidence is where the error follows you: every device, one home network, the second Call of Duty device in the same house, one Windows PC, or one account.

1. Check Activision and Platform Service Status

Black Ops 6 cannot finish its startup connection when Activision or the sign-in platform cannot validate or route the session. Use this check first. If either service reports an incident, skip local changes until it recovers.

1. Open Activision’s Online Services page and select Call of Duty: Black Ops 6.

   

2. Use the same page’s Server Status by Network area to check PlayStation Network, Xbox Network, Steam, or Battle.net.

   

3. Confirm that the console or launcher is signed in to the platform account used to play Black Ops 6.
4. If either service reports maintenance or degraded service, wait for recovery. Close the game and test one fresh launch afterward.

Checkpoint: If the game connects after service recovery, the incident caused the error. If both service layers remain operational and the same device still fails, continue to Method 2.

If Black Ops 6 gets past this startup stage but later shows the broader online-services message, use this Black Ops 6 online-services guide for that later failure.

2. Start a Clean Game and Network Session

A suspended game, expired launcher session, queued update, or stale router mapping can prevent networking from starting. This method replaces that temporary state without changing permanent account or router settings. It follows Activision’s official BO6 connection sequence.

1. Close Black Ops 6 completely. On PC, also exit Steam, Battle.net, or the Xbox app from the notification area.
2. Check for a Black Ops 6 update and let every game-content download finish before reopening it.
3. Shut down the console or PC. Unplug the router and modem for about one minute, restore power, and wait until the connection is fully online before starting the gaming device.

   

4. On PlayStation or Xbox, run the built-in internet or network test. On PC, confirm that the launcher signs in normally before opening the game.

   

5. If possible, connect through Ethernet for one launch instead of Wi-Fi.

   

6. Pause downloads, streams, cloud backups, and other heavy network activity, then launch Black Ops 6 again.

Checkpoint: If the restart works, the session or router mapping was stale. If Ethernet works where Wi-Fi fails, repair the wireless connection. If HUENEME – NEGEV remains, Method 3 provides the fastest test of the entire home-network path.

3. Test Another Network Before Changing the Router

A hotspot changes the route to Activision while keeping the game, device, and account the same. That makes it a more useful diagnosis than immediately changing DNS or forwarding ports.

1. Connect the console or PC briefly to a phone hotspot or another trusted internet connection, then attempt one Black Ops 6 launch. Avoid downloading updates over mobile data.

   

2. If the hotspot also fails, do not change the home router yet. Continue to the account check only if the failure follows one identity; on one affected PC, skip to Method 5.
3. If the hotspot works, sign in to the home router. Remove or disable existing manual forwarding rules for the gaming device, enable UPnP, restart the router, and test again.
4. If only the second Call of Duty device in the house fails, close the game on the first device and retest. If the second one now connects, the router is mishandling concurrent mappings. Remove manual rules and let UPnP assign them; do not forward the same external port to two devices.
5. If UPnP does not help a single gaming device, turn it off before assigning that device a fixed local IP and following Activision’s current platform-specific port table.

   

6. If the router uses a gaming Geo-Filter, parental filter, or threat-blocking feature, review its blocked list and allow the Call of Duty endpoint that appears when the error occurs.
7. On a school, office, dormitory, hotel, cellular home-internet, or other managed connection, give the successful hotspot comparison to the administrator or ISP. They may need to resolve carrier-grade NAT, double NAT, or a blocked route that you cannot change locally.

Checkpoint: If another network works, keep the investigation with the router or ISP. If both networks fail, restore unsuccessful router changes. Continue to Method 4 only for an account-specific difference; otherwise use the PC or game-repair method.

If the game connects but reports Moderate or Strict NAT, use this Call of Duty NAT guide rather than mixing NAT repair into the remaining HUENEME – NEGEV checks.

4. Check the Activision Link Only When the Failure Follows One Account

Black Ops 6 loads its online profile and progression from the Activision account linked to the platform identity. A wrong link can therefore make one identity fail while another works on the same device and network. Skip this method when every account fails.

1. Open Activision’s account-management page and sign in with the same PlayStation, Xbox, Steam, or Battle.net identity used to launch Black Ops 6.
2. Open Linked Accounts and verify that the displayed platform account is the one you intend to use.

   

3. If the email address or password is outdated, use the platform-login route to open Basic Info and repair those details before considering an unlink.

   

4. Unlink and relink only when the displayed platform account is demonstrably wrong and you have reviewed the restriction and progression consequences.
5. If you find an unfamiliar link or other evidence of unauthorized access, secure the account and use Activision’s hacked-account recovery path.

Checkpoint: If correcting the identity restores the expected profile and connection, the account link caused the failure. If the link was already correct, leave it intact and continue to Method 5 on Windows or Method 6 on any platform.

5. Remove VPN or Firewall Interference on Windows

Use this method when only one Windows PC fails, including on a hotspot. A VPN changes its route, while a firewall or web filter can block the launcher or game connection. Skip it when consoles and PCs fail together.

1. Disconnect any active VPN or proxy, close its client completely, and launch the game once.

   

2. Open Windows Security > Firewall & network protection and note whether the active connection is Private or Public.
3. Select Allow an app through firewall > Change settings. Confirm that the trusted launcher and Call of Duty executable are allowed on the active profile. If an entry is missing, use Allow another app and select the genuine executable.

   

4. Temporarily close third-party web filters, traffic monitors, or security suites and retest. If one is responsible, re-enable it and add the narrow application exception documented by its vendor.

Microsoft’s firewall guidance considers an application exception safer than opening broad ports. Keep the firewall enabled, allow only executables you recognize, and do not change controls managed by an employer or school.

Checkpoint: If removing the VPN or correcting the application exception works, the failure was local to that PC. If the clean PC route still fails, re-enable protection and continue to Method 6.

6. Check the Current Build, Then Repair Its Files

An incomplete update or missing content package can leave the installed build unable to initialize networking. Launcher repair compares local files with the current release and replaces missing or damaged data. Skip it during a live outage or a proven home-router failure.

1. Review Activision’s Black Ops 6 Known Issues page for a current login or networking problem.

   

2. Install pending game, launcher, console, and Windows updates. On a console, open the game’s content-management screen and confirm that the required Black Ops 6 multiplayer package is fully installed.
3. On Steam, follow Steam’s Verify integrity of game files procedure. On Battle.net, run Scan and Repair. In the Xbox app for Windows, open Manage > Files > Verify and Repair.

   

4. Do not delete console saved data for this connection error. If repair finds nothing and no known issue is listed, submit an Activision bug report with the exact code, platform, region, time, and the results of the hotspot, second-device, and second-account comparisons.

Checkpoint: If repair restores access, the local build was incomplete or damaged. If it still fails, those comparison results give Activision Support a clear account, device, or route pattern to investigate.