Fix NERR_TooManyServers (0X0000099F) – No Space for Entry

Quick Answer

Run net stop lanmanserver && net start lanmanserver as admin to clear the cached server list. If it comes back, increase the registry key MaxCachedServers under HKLM\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters to 64 or higher.

What's Actually Happening

Windows keeps a small table of all servers it discovers on your network. This table has a hard limit — by default it's 64 entries on most systems, but on older or locked-down installs it can be as low as 16. When you're on a busy network with lots of machines, or if a service keeps scanning and adding entries without cleanup, the table fills up. The error 0X0000099F means there's literally no space for another entry.

I've seen this most often on file servers that run SMB multi‑channel or on domain controllers in large offices. It also shows up if you have a script that calls NetServerEnum repeatedly — it fills the table and then stops working.

Why the Error Shows Up

The server service (LanmanServer) maintains an internal list of discovered servers. When that list hits the max, any attempt to add a new server — like joining a new share or browsing the network — fails with this error. The system doesn't throw a warning before it happens; you just get the error when you try to connect to something new.

Fix Steps

1. Restart the Server Service — Open Command Prompt as admin and type:
   net stop lanmanserver && net start lanmanserver
   This flushes the cached server list. Your existing connections stay alive, but new ones can be added again.
2. Check the Current Limit — Open Registry Editor (regedit) and go to:
   HKLM\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters
   Look for a DWORD named MaxCachedServers. If it's missing, the default is 64.
3. Increase the Limit — If the error keeps coming back, create or edit MaxCachedServers as a DWORD and set it to 128 (decimal). Restart the server service after the change.
4. Reboot — If nothing works, a full reboot forces a clean state. This is the nuclear option but it's reliable.

If the Main Fix Doesn't Help

Sometimes the problem isn't the limit but a misbehaving service or script that spams the server table. Check the Event Viewer under Applications and Services Logs > Microsoft > Windows > Server for repeated entries. If you see a specific process, stop it or increase the interval between its scans.

Another rare cause: antivirus software that hooks into server enumeration. Try temporarily disabling the AV (just for testing) and see if the error disappears.

Prevention Tip

Set MaxCachedServers to 256 if you run a busy network. The downside is slightly more memory used — about 4KB per entry — but on modern machines that's nothing. Also, if you write scripts that call NetServerEnum, add a delay of at least 10 seconds between calls to avoid flooding the table.

The real fix isn't just restarting — it's understanding that the default limit was designed for small networks. If your network has more than 64 servers, you need to tell Windows to expect that.