CS2 Stuck on "Connecting to the CS:GO Network"

Why the wording changed

If you are searching the CS:GO phrasing and finding nothing in your game, that is expected. The message comes from one string in Counter-Strike's localization file, and Valve rewrote its text when CS:GO became CS2 without changing the string itself:

Same code path, same failure, new branding. Anything written about the old message still applies — which is exactly why so much stale CS:GO-era advice survives around this problem.

What actually stops working

You do not have to guess at this. CS2 attaches a tooltip to the message that names the affected features outright: matchmaking, inventory, loadout, lobbies, invites and the store may all be temporarily unavailable while the connection is being made. That gives you a clean split:

Use that as your diagnostic. If you can load into an offline map and shoot but cannot queue or see your skins, the engine and your install are fine and the problem is squarely the Game Coordinator session. Stop verifying game files.

Where else CS2 tells you the same thing

The Play menu has its own wording for the identical condition — it will report that there is no connection to the Counter-Strike network where it would normally explain why a mode is locked. If you see that on the Play screen and the connecting spinner on the store, they are one problem, not two.

Fix 1: Restart the game — properly

The Game Coordinator session is negotiated when the client starts. When that negotiation stalls, it rarely recovers on its own, and no amount of clicking around the menu re-triggers it. A relaunch does.

1. Quit CS2 completely and let it disappear from Task Manager before relaunching.
2. If it comes straight back, quit CS2 and then exit Steam with Steam → Exit — the window X only minimises Steam to the tray, so "I restarted Steam" usually means you did not.
3. Let Steam finish signing in and show your friends list before launching CS2 again.

If Steam comes up in offline mode, or your friends list shows you as offline, that alone will keep the handshake from completing. Set yourself Online first.

Fix 2: Check whether your client is out of date

CS2 updates land without warning, and a client that has been sitting open across an update is a classic cause of a permanently stuck connection. The tell is a second message: CS2 shows a "Your Client Needs To Update" prompt whose body text simply tells you to restart the game to get the most recent update, and matchmaking will show a red notice saying the client needs to update.

If you see either of those, this is your fix and nothing else on this page matters. Our client is out of date page covers what to do when the restart alone does not pull the update down.

Fix 3: Rule out Valve before touching your PC

The Game Coordinator can go down while game servers stay perfectly healthy — which is why "Steam looks fine" and "my friend is in a match" are both weak evidence. A friend already inside a game has a session; they will not notice a coordinator outage until they return to the menu.

Check our live CS2 server status page first. If the coordinator or matchmaking is degraded, there is no local fix, and reinstalling during an outage just costs you an evening and a lot of bandwidth.

Fix 4: Fix the Steam session underneath it

The Game Coordinator connection is authenticated by your Steam session, so anything that breaks that session breaks this. In practice:

• Your account signed in somewhere else. Steam allows one active game session per account. A laptop or Steam Deck left running a game will take yours.
• A dead or stale login. Signing out of Steam and back in forces a brand-new authentication rather than reusing a cached one.
• Steam in offline mode. The game launches, the coordinator never will.

If you have also seen a "no user logon" kick from a server, that is the same underlying failure surfacing elsewhere — work through the no user logon fix, which goes into the Steam-session side in detail.

Fix 5: Network interference — but not the usual suspects

This is where most guides go wrong. Coordinator traffic does not use the UDP relay pings that CS2's other network errors complain about, so MTU tweaks and relay troubleshooting are largely beside the point here. What does matter is anything that filters your Steam client's connection:

• VPNs and proxies. Disconnect fully rather than split-tunnelling — Steam is sensitive to a session apparently changing country mid-connection.
• Security suites that replace the Windows firewall. Disable the suite entirely as a test; an exclusion rule does not always cover its network filtering.
• Restricted networks. Work, school and hotel networks routinely allow web browsing while blocking everything else. A phone hotspot test settles it in two minutes.

If it works on the hotspot, your PC and your install are clear and the problem is your home network. If it fails there too, keep looking on the PC.

Fix 6: Steam-side cleanup, in order

1. Clear the Steam download cache. It signs you out and forces a clean reconnection to Steam's servers, which is genuinely relevant to a session problem — unlike file verification.
2. Verify CS2 via Properties → Installed Files → Verify integrity of game files. Low odds here, but it is free and it rules the install out for good.
3. Reinstall the Steam client, keeping your steamapps folder so nothing re-downloads. Do this before you ever consider reinstalling CS2 itself.

If it turns out to be a different error

Three near neighbours worth separating. If the main menu warns you before you even queue, read failed to reach any official servers — that is the relay-ping system, not the coordinator. If you time out while joining one specific match, see unable to establish a connection with the game server. And if your items are the only thing missing once you are connected, inventory unavailable is the closer match. If CS2 never opens at all, start at CS2 not launching.