What Is SMB Protocol and Why Is It Unreliable on Windows 11?
SMB (Server Message Block) is the protocol Windows uses for file sharing. Understanding what it is and why it keeps breaking on Windows 11 explains most small office networking problems.
SMB Is the Foundation of Windows File Sharing
SMB — Server Message Block — is the network protocol that powers virtually everything you do with Windows file sharing. When you open the Network folder and see other computers, when you map a network drive, when you access a shared printer — all of it uses SMB underneath.
It is one of the oldest continuously-developed network protocols in computing. The original version (SMB1) dates to 1983, developed at IBM and later adopted by Microsoft. The protocol has been through four major versions, each more capable and more complex than the last.
SMB Protocol Versions
| Version | Introduced in | Key characteristics |
|---|---|---|
| SMB1 | 1983 / Windows NT 3.1 | Simple, no encryption, no signing, severe security vulnerabilities. Now largely disabled. |
| SMB2 | Windows Vista / Server 2008 | Major rewrite: compound requests, better scalability, pipelining |
| SMB2.1 | Windows 7 / Server 2008 R2 | Large MTU support, improved performance |
| SMB3.0 | Windows 8 / Server 2012 | End-to-end encryption, SMB Direct (RDMA), failover |
| SMB3.1.1 | Windows 10 / Server 2016 | Pre-authentication integrity, AES-128-GCM encryption, required signing in some configurations |
Current Windows 11 systems use SMB3.1.1 between modern Windows machines and SMB2 with older systems that do not support SMB3.
Why SMB1 Was Disabled and Why That Broke Things
In 2017, the EternalBlue exploit — leaked from the NSA — demonstrated catastrophically how vulnerable SMB1 was. WannaCry ransomware used it to propagate across networks automatically, infecting hundreds of thousands of machines in days.
Microsoft's response was to disable SMB1 by default from Windows 10 version 1709 onwards, and eventually remove it entirely from Windows 11 default installations.
This was the correct security decision. But it had collateral effects: any device that only spoke SMB1 — older NAS units, network printers, Windows XP and Windows 7 machines, some Linux Samba installations — stopped working with Windows. For small offices with older hardware that had run reliably for years, the update created sudden, unexplained failures.
Why SMB Is Unreliable on Windows 11 Specifically
SMB itself is not the direct cause of Windows 11 file sharing unreliability. The problem is the dependency chain SMB relies on:
Windows Discovery (finding machines in the Network folder) is handled not by SMB but by WS-Discovery and SSDP — separate services that are prerequisites for seeing machines in the Network browser. SMB only handles the file transfer after you know where to connect. If discovery fails, SMB never gets involved.
The four discovery services required for machines to appear in the Network folder are:
- Function Discovery Resource Publication
- SSDP Discovery
- UPnP Device Host
- DNS Client
These run as independent Windows services. They have individual startup type settings (Automatic, Manual, Disabled). Windows Updates occasionally reset these startup types, causing the services not to run at boot — making machines invisible in the Network folder even though SMB is fully functional.
SMB signing requirements are new to Windows 11 (introduced in version 22H2). SMB signing cryptographically verifies the integrity of SMB packets, preventing man-in-the-middle attacks. When connecting to a system that does not support SMB signing — an older NAS, a printer, a Windows 7 machine — the connection fails with an error that is not always obvious.
The Credential and Authentication Layer
Beyond discovery, SMB requires authentication. When you connect to a shared folder on another Windows machine, SMB presents credentials. If those credentials do not match an account on the host machine, access is denied.
In a workgroup (non-domain) environment, credential management is manual and fragile:
- Each user account on the host machine must match the connecting user's account name and password exactly
- Windows Credential Manager stores remembered credentials that may become stale after password changes
- Guest access (allowing connection without credentials) is disabled by default in current Windows versions for security
The credential system is correct in its security design; it is frustrating in its lack of visible error messaging when credentials do not match. "You do not have permission to access this resource" gives no indication whether this is a credential problem, a firewall problem, or a permissions problem.
SMB on macOS
macOS connects to SMB shares natively through Finder. Go menu → Connect to Server → smb://IP-ADDRESS/ShareName or browse via Network in the Finder sidebar.
Mac SMB support is generally reliable for connecting to Windows shares, though discovery of Windows machines from Mac can be inconsistent — macOS uses Bonjour for discovery, Windows uses SSDP, and they do not always see each other automatically. Using Connect to Server with a direct IP address bypasses the discovery issue.
macOS also supports hosting SMB shares: System Settings → General → Sharing → File Sharing → enable SMB. This lets a Mac present shared folders to Windows machines over the SMB protocol.
Why Application-Layer Tools Are More Reliable
SMB is a transport and authentication protocol, not a discovery system. Tools that implement their own discovery and authentication layer — independent of Windows' SSDP/WS-Discovery stack — eliminate the failure modes that make SMB frustrating for non-technical users:
- No dependency on the four discovery services — peer discovery happens at the application level
- No Windows credential management — authentication is handled by the application
- Survives Windows updates — application-level configuration does not reset with Windows Update
This is why tools like LocalSend and Oxolan maintain their own peer discovery rather than relying on the Windows Network folder.
Frequently Asked Questions
Should I re-enable SMB1 to fix compatibility with an old device? Only as an absolute last resort, and only for an isolated network that is not connected to the internet. SMB1 has known, unpatched vulnerabilities. The correct approach is to update the legacy device's firmware to support SMB2, or replace it. If neither is possible, network isolation and accepting the security risk may be the only remaining option.
What is the SMB signing error and how do I fix it? If you see "The specified network name is no longer available" or a reference to SMB signing when connecting to a device: check whether the target device supports SMB signing. Most NAS devices with current firmware do. If the device does not support it, either update its firmware or configure a Group Policy exception (Windows Pro/Enterprise) to allow unsigned connections to that specific device.
Can I tell which SMB version is being used for a connection?
Yes. Open PowerShell as Administrator and run Get-SmbConnection— this shows active SMB connections and their negotiated version. Get-SmbServerConfiguration | Select EnableSMB1Protocol, EnableSMB2Protocol shows which versions are enabled on the local machine.
Is SMB secure enough for sensitive data on a local network? SMB3 with signing and encryption enabled is considered secure for corporate environments. For a local LAN not connected to external parties, the risk profile depends on who has physical access to your network. SMB without encryption (older configurations) sends file data in a form readable by anyone monitoring network traffic on the same segment.
Done troubleshooting Windows?
Oxolan handles file sharing so you never have to think about this again.
Get Oxolan for Windows