How to Fix Modern Warfare 4 “Networking Failed to Start” (HUENEME – NEGEV) Error

You launch Call of Duty: Modern Warfare 4, the game sits on the connecting screen for a while, and then it gives up with “Networking Failed to Start”. Most players see two odd words after it, such as [Reason: HUENEME – NEGEV]. Since the game launched on October 23, this has become one of the most common errors on PC, PS5, Xbox Series X|S, and Switch 2.

The two words look like a clue, but they aren’t. Call of Duty uses random word pairs like HUENEME – NEGEV as session tags, and they don’t tell you what went wrong. What the message does tell you is that the game couldn’t connect to Activision’s online services. That can be caused by the servers themselves, or by something between your device and the servers, such as your router, DNS, NAT type, VPN, or firewall.

What Causes “Networking Failed to Start” in Modern Warfare 4?

• Server outages or heavy load, which are common during launch week and after big updates.
• A stale route or DNS entry on your router or PC that points to a server that no longer responds.
• A Strict or Moderate NAT type, or blocked ports, which stop the connection handshake.
• A VPN or router geo-filter that blocks or redirects one of the matchmaking servers.
• Firewall or antivirus software blocking the game on PC.
• Missing TPM 2.0 or Secure Boot on PC. Without them, online play is blocked, and the result can look like a networking error.

Fix: Modern Warfare 4 “Networking Failed to Start” Error

Start with the first method, because if the servers are down, nothing else will help. Then work down the list.

1. Confirm Activision’s Servers Are Online

There’s no point changing your router settings if the problem is on Activision’s side. Open Activision’s Online Services page, choose Modern Warfare 4, and look for any outage or degraded service warning. The official Call of Duty updates account on X also posts when something is down.

Sometimes the servers are up but simply overloaded at peak times. If that’s the case, return to the main menu, give it a minute or so, and try connecting again.

2. Give Your PC or Console a Proper Reboot

Quitting to the home screen isn’t enough here. The game, its launcher, and your device all need a clean start so the connection is set up from scratch.

• PC: Close the game, then right-click Battle.net, Steam, or the Xbox app in the system tray and quit it before reopening.
• PS5: Choose Turn Off PS5 rather than Rest Mode, wait until the light goes out, and power it back on.
• Xbox Series X|S: Press and hold the console’s power button for about 10 seconds, pull the power cable for 30 seconds, then switch it on again.
• Switch 2: Hold the POWER button, pick Power Options, select Turn Off, and wait half a minute before turning it on.

3. Reset Your Network Hardware

Routers that have been running for weeks can hold on to bad routes. A full power cycle clears them out.

1. Pull the power cables from both the modem and the router.
2. Leave them unplugged for one full minute.
3. Reconnect the modem on its own and wait until its lights show it’s online.
4. Reconnect the router and give it a minute or two to come back up.

4. Switch From Wi-Fi to Ethernet

A wireless connection that drops even briefly during sign-in can be enough to trigger this error. Run an Ethernet cable from your router to your PC or console if you can. When a cable isn’t practical, sit closer to the router and connect to its 5 GHz network.

5. Swap Your DNS for Cloudflare or Google

Your internet provider’s DNS can be slow or point to the wrong server. Switching to a public DNS often fixes this error.

On PC:

1. Open Command Prompt as administrator and run ipconfig /flushdns.
2. Open Settings > Network & internet, select your connection, and choose to edit the DNS server assignment.
3. Set it to Manual, turn on IPv4, and enter 1.1.1.1 and 1.0.0.1 (Cloudflare) or 8.8.8.8 and 8.8.4.4 (Google).
4. Save and restart the game.

On PS5: Go to Settings > Network > Settings > Set Up Internet Connection, select your network, choose Advanced Settings, set DNS to Manual, and enter the same addresses.

On Xbox: Go to Settings > General > Network settings > Advanced settings > DNS settings, choose Manual, and enter the same addresses.

6. Disable VPNs and Router Geo-Filters

A VPN can send your connection through a region that doesn’t match your account, and that can stop the game from connecting. Turn your VPN off completely before launching the game.

If your router has a geo-filter feature, such as on Netduma or ASUS gaming routers, check that it isn’t blocking any Call of Duty matchmaking servers. Users on Netduma’s forum found that blocking a single matchmaking server was enough to trigger the HUENEME – NEGEV error. Remove any blocked servers, or turn the geo-filter off for your gaming device while you test.

7. Open Up Your NAT Type

A Strict or Moderate NAT type can stop Modern Warfare 4 from completing its connection. You can check your NAT type in the game under Settings > Account & Network > Network Info.

The simplest fix is to enable UPnP in your router’s settings, then restart the router. If that doesn’t give you an Open NAT, forward these ports to your device’s local IP address:

These are the same ports used by recent Call of Duty games. On PC, you may also need to allow the game through Windows Firewall, which is covered in the next method.

8. Let Call of Duty Through Windows Firewall

Even with the right ports open, Windows can still block the game’s traffic if it isn’t on the allowed list.

1. Type firewall into the Start menu and open Allow an app through Windows Firewall.
2. Hit Change settings so the list becomes editable.
3. Tick both the Private and Public boxes for Call of Duty, your launcher, and the game executable. Missing entries can be added with Allow another app.
4. Running a third-party antivirus with its own firewall? Add the Call of Duty install folder to its trusted list as well.

9. Rule Out the TPM and Secure Boot Check

On PC, Modern Warfare 4 won’t allow any online mode unless TPM 2.0 and Secure Boot are both active. When that check fails, the result can easily be mistaken for a network fault. Our TPM and Secure Boot guide for Modern Warfare 4 shows you how to confirm both are switched on.

10. Try the Mobile Hotspot Trick

Some players get past the error by connecting through a different network just for the login step.

1. Turn on the hotspot on your phone and connect your PC or console to it.
2. Launch Modern Warfare 4 and wait until you reach the main menu or a lobby.
3. Switch back to your home network.

If the game connects on your hotspot but not at home, the problem is almost certainly your router, DNS, or internet provider. Be careful with mobile data limits, as the game may start downloading updates.

11. Clear Your Console’s Network Cache

PS5: Turn the console off, then hold the power button until you hear a second beep to start in Safe Mode. Connect your controller with a USB cable and choose Clear Cache and Rebuild Database, then Clear System Software Cache.

Xbox Series X|S: Go to Settings > Device & connections > Blu-ray > Persistent storage and clear it. You can also go to Settings > General > Network settings > Advanced settings > Alternate MAC address and select Clear, then restart.

If none of these methods work and the servers show as online, contact your internet provider. Some providers block or throttle certain gaming ports, and only they can change that. You can also report the issue through Activision’s Modern Warfare 4 support page.

Conclusion

The “Networking Failed to Start” error in Modern Warfare 4 means the game couldn’t reach Activision’s online services, and the HUENEME – NEGEV words after it are just a session tag. Always check the server status first. If the servers are up, power-cycle your router, switch to a public DNS, turn off any VPN or geo-filter, and make sure your NAT type is Open. On PC, also confirm that TPM 2.0 and Secure Boot are enabled.

Which fix worked for you? Let us know in the comments, along with your platform, so other players can find the solution faster.