Fix STATUS_BAD_NETWORK_NAME (0XC00000CC) Fast

The 30-Second Fix: Check Your Typo

I had a client last month—small law firm, three partners sharing a folder called "ClientFiles2024." One partner couldn't access it, got this exact 0XC00000CC error. Turns out she typed \\SERVER\ClientFiles instead of \\SERVER\ClientFiles2024. Took me five seconds to spot.

So first thing: double-check the share name. If you're mapping a drive, look at what you typed in the Folder box. Common gotchas:

• Missing a backslash? \\SERVER\Share is correct, \\SERVERShare is not.
• Capitalization matters on some networks—Linux Samba shares are case-sensitive.
• Spaces in the share name? Use quotes: "\\SERVER\My Share".

Open a Command Prompt and run net view \\SERVER. If that works, you'll see a list of all shares. Compare the exact name. If the share isn't listed, it doesn't exist or you're looking at the wrong server.

Still broken? Move to the next step.

The 5-Minute Fix: Clear Stale Connections

Windows loves caching old network credentials. Once you change a share name or permission, your PC might hold onto the old connection and throw 0XC00000CC.

Here's the quick way to flush that junk:

1. Open an elevated Command Prompt (right-click, Run as Administrator).
2. Type net use and hit Enter. You'll see all active connections.
3. Look for the one with the error—maybe it's marked as "Unavailable" or "Disconnected."
4. Delete it: net use * /delete (removes all) or net use X: /delete (replace X: with the drive letter).
5. Now remap the drive fresh: net use X: \\SERVER\CorrectShareName /persistent:yes.

I've seen this fix about 40% of the time. Windows just doesn't release the old connection on its own—you have to force it.

Still no luck? Let's dig deeper.

The Advanced Fix: Network Discovery and Credential Manager

If the simple stuff didn't work, something's blocking the connection. Here are the two most common culprits.

1. Network Discovery Is Off

Windows 10 and 11 turn off network discovery by default on public networks. If your network profile says "Public," file sharing won't work.

Check it: Open Settings > Network & Internet > Status. Click Properties under your active network. Change the network profile to "Private." Then go to Control Panel > Network and Sharing Center > Change advanced sharing settings and turn on network discovery and file and printer sharing.

I had a small manufacturing shop this year—their IT guy had set all PCs to Public. Took me 10 minutes to fix all five machines.

2. Stale Credentials in Windows Credential Manager

Old saved passwords can override what you type now. Here's how to blow them away:

• Open Credential Manager (type it in the Start menu).
• Click Windows Credentials.
• Scroll to the Generic Credentials section.
• Look for anything starting with TERMSRV or MicrosoftAccount or the server name—like \\SERVER.
• Remove those entries. All of them.
• Reboot and try mapping the drive again.

One more thing: if the server is a Windows machine, check that the share exists in the File Explorer of the server itself. Right-click the folder, go to Properties > Sharing tab. If it's not shared there, re-share it. I've seen admins delete a share and forget to re-create it.

Still stuck? Open Event Viewer on your machine and look under Windows Logs > System for errors from source "MrxSmb" or "Bowser." That'll tell you exactly which server is failing. But 90% of the time, it's one of the fixes above.

Pro tip: If you're using a mapped drive in a batch script, add a net use command at the start to disconnect and reconnect. Keeps things fresh.