Fix STATUS_NOT_SERVER_SESSION (0xC0000216) on Windows

Yeah, this one's annoying. You're staring at STATUS_NOT_SERVER_SESSION (0xC0000216) with that message about the transport only processing requests on the server side of a session. Usually shows up when you're trying to connect to a shared printer or a network drive on a Windows machine that's acting as both client and server. Happened to a client last month who had a Windows 10 Pro box sharing a printer to a few Macs—then suddenly the Macs couldn't print and threw this exact error. Let's fix it.

The Direct Fix: Restart the Server Service

Open an admin Command Prompt and run these two commands in order:

net stop server && net start server
net start

The net start command just confirms the Server service is running. You'll see a list of services—look for "Server" with a status of "running". If it's not there, run net start server again.

That's it. 90% of the time, this clears the error. No reboot required. The Server service manages SMB sessions, and when it gets confused about which side of a session it's on (client vs. server), restarting it resets the transport state.

Why This Happens

The error means the SMB transport layer received a request that expects to be handled on the server side, but something flagged it as a client-side request. Think of it like a mailroom that can't tell if a package is incoming or outgoing. Common triggers:

• A Windows machine is both hosting a shared resource (like a printer) and trying to connect to another share on the same network.
• A service or application (like a backup tool) initiates an SMB connection while the Server service is in a weird state after a network change.
• Third-party firewall or VPN software messes with the SMB port (445) and confuses the session handling.

The Server service registers transport protocols (like TCP over SMB) during startup. If something triggers a re-registration mid-session—like a network adapter reset or a service crash—the transport can end up in a half-client, half-server state.

Less Common Variations

If restarting the Server service doesn't work, try these in order:

1. Re-register the SMB Transport via netsh

Run this in an admin Command Prompt:

netsh int ip reset
netsh winsock reset

This resets the TCP/IP stack and Winsock catalog. Reboot after. I've seen this fix cases where a VPN client corrupted the transport chain. A client of mine had Cisco AnyConnect installed, and after disconnecting, the error popped up. Winsock reset did the job.

2. Check for Conflicting Print Spooler Services

If the error shows up specifically when printing, the Print Spooler might be holding a bad session. Run these in admin CMD:

net stop spooler
del /Q /F /S %systemroot%\System32\spool\PRINTERS\*
net start spooler

This clears stuck printer jobs. Had a scenario where a corrupted print job (from a Mac via AirPrint) caused the Spooler to keep a half-open session.

3. Verify SMB1 is Disabled (but Not Required)

Old SMB1 can cause session confusion. Check with:

Get-SmbServerConfiguration | Select EnableSMB1Protocol

If it shows True, disable it (unless you need it for legacy devices):

Set-SmbServerConfiguration -EnableSMB1Protocol $false

Reboot after. Don't bother with this unless the error persists—most modern Windows versions have SMB1 off by default.

Prevention

Once you've fixed it, stop it from coming back. Here's what I tell clients:

• Don't mix roles on the same machine. If a Windows box is a print server, don't also use it to connect to other network shares regularly. That's the #1 trigger.
• Keep the Server service set to Automatic and ensure it starts before any dependent services. Check with sc qc server—if the start type isn't AUTO, set it with sc config server start= auto.
• Update network drivers. Realtek and Intel NIC drivers have known issues with SMB session handling. Install the latest from the manufacturer, not Windows Update.
• Log off and back on after any network change (like connecting to a VPN or switching from Wi-Fi to Ethernet). This re-initializes your user session cleanly.

Do those, and you'll rarely see 0xC0000216 again. I've had a few clients run for years without a recurrence after applying these. If you do see it after all that, check Event Viewer under System logs for source srv or srv2 errors—that'll point to a deeper driver-level issue.