SMB

SMB
Name	SMB
Title	SMB
Developer	IBM, Microsoft
Initial release	1983
Latest release	SMB 3.1.1 (2018)
Operating system	MS-DOS, OS/2, Microsoft Windows, Linux, FreeBSD, macOS
License	Proprietary, Samba (software) GPL

SMB Server Message Block is a network protocol for shared access to files, printers, and serial ports, and inter-process communication. Originally developed by IBM and later extended by Microsoft, SMB enables resource sharing across networks used in Windows NT domains, Active Directory forests, and mixed Samba (software) deployments. SMB has influenced and coexisted with protocols such as NFS (protocol), CIFS, and SMB2-family specifications.

Definition and Overview

SMB defines a client–server model where a client requests services from a file server, print server, or application server using structured messages. Implementations interact with systems like Windows Server 2016, Windows 10, Samba (software), FreeNAS, and NetApp ONTAP appliances to provide shared folders, named pipes, and remote administration. SMB sessions are negotiated over transports such as NetBIOS over TCP/IP, Direct Hosted SMB over TCP, and transports used in SMB 3.x to enable features like encryption and multichannel. The protocol is specified in documents published by Microsoft and reverse-engineered by projects such as Samba (software) and analyzed in academic work from International Organization for Standardization contexts.

History and Development

SMB traces to work by IBM in the early 1980s and was adapted by Microsoft for MS-DOS-based networking and later for Windows for Workgroups and Windows NT 4.0. Subsequent milestones include the publication of CIFS by Microsoft in the late 1990s, the introduction of SMB2 with Windows Vista and Windows Server 2008, and the redesign in SMB3 with Windows 8 and Windows Server 2012 adding resilience and encryption. Third-party reimplementations like Samba (software) enabled interoperability with Linux distributions such as Red Hat Enterprise Linux and Debian, and integration with macOS through Apple Filing Protocol coexistence mechanisms. Standardization efforts and security advisories from organizations like National Institute of Standards and Technology have shaped later revisions.

Protocol Specification and Versions

The specification family includes SMB 1.0 (often called CIFS), SMB2, SMB2.1, SMB3.0, SMB3.02, SMB3.1.1 and vendor extensions by Microsoft. SMB 1.0 used NetBIOS-style session services and packet formats documented in legacy IBM materials and Microsoft technical notes. SMB2 reduced chattiness and introduced command multiplexing, large read/write buffers, durable handles, and improved oplock semantics used by Hyper-V and SQL Server cluster scenarios. SMB3 added multichannel, persistent handles, end-to-end encryption, and witness mechanisms used with Storage Spaces Direct and Cluster Shared Volumes. Formal specifications, protocol traces, and RFC-adjacent analyses appear in publications from IETF-adjacent working groups and in technical white papers from Microsoft and community projects.

Implementations and Platforms

Key implementations include Microsoft Windows Server built-in SMB stack, Samba (software) for Unix-like systems, and commercial NAS firmware from vendors such as NetApp, Synology, and QNAP Systems, Inc.. Client stacks exist in FreeBSD, macOS, Android-derived devices, and embedded systems from Dell EMC and Hewlett Packard Enterprise. Enterprise features integrate with Active Directory for authentication, with Kerberos and NTLM used in various deployment modes, and with OpenLDAP in mixed environments. Cloud providers offer SMB endpoints in services by Microsoft Azure Files and partner integrations with Amazon Web Services-marketplace appliances.

Security and Vulnerabilities

SMB has been the vector for major incidents involving WannaCry, NotPetya, and other malware outbreaks exploiting SMB1 weaknesses and remote code execution vulnerabilities disclosed in advisories by Microsoft and coordinated via US-CERT. Authentication mechanisms include NTLMv1/v2 and Kerberos, and modern SMB versions support signing and AES-based encryption introduced in SMB3.0 and strengthened in SMB3.1.1. Vulnerabilities such as EternalBlue targeted implementation flaws in Windows Server 2008 R2 and Windows 7 stacks, prompting emergency patches and mitigation guidance from Microsoft Security Response Center. Best practices reference disabling SMB1, applying patches, and using network segmentation advised by CISA and NIST publications.

Uses and Applications

SMB is used for file sharing in enterprise environments like Exchange Server backups, SQL Server storage offload, and home media sharing with devices such as Roku and Plex Media Server. It supports printer sharing with HP LaserJet and Brother printers and is leveraged for administrative operations by tools like PowerShell remoting (over file share-based modules) and backup solutions from Veeam and Commvault. SMB also underpins virtualization scenarios in Hyper-V live migration, clustering with Windows Server Failover Clustering, and storage pooling in Storage Spaces Direct.

Performance and Interoperability

Performance characteristics vary with versions and features: SMB2/SMB3 offer reduced latency and improved throughput compared with SMB1 due to request batching, large MTU support, and multichannel aggregation used with RDMA and SMB Direct hardware like Mellanox adapters. Interoperability challenges arise between Samba (software) versions and proprietary SMB extensions in Windows Server 2019 or NetApp ONTAP firmware; these are resolved via configuration options, protocol negotiation, and compatibility modes documented by Microsoft and Samba (software). Benchmarks often reference tools and suites from Iometer and vendor-specific testing with storage arrays from EMC Isilon and Pure Storage.

Category:Network protocols