Server Message Block (SMB) is a communication protocol originally developed in 1983 by Barry A. Feigenbaum at IBM and intended to provide shared access to files and printers across nodes on a network of systems running IBM's OS/2.

<protocol> (SMB) A client/server protocol that provides file and printer sharing between computers. In addition SMB can share serial ports and communications abstractions such as named pipes and mail slots. SMB is similar to {remote procedure call} (RPC) specialised for file system access. SMB was developed by Intel, Microsoft, and IBM in the early 1980s. It has also had input from Xerox and 3Com. It is the native method of file and print sharing for Microsoft operating systems; where it is called {Microsoft Networking}. Windows for Workgroups, Windows 95, and Windows NT all include SMB clients and servers. SMB is also used by OS/2, Lan Manager and Banyan Vines. There are SMB servers and clients for Unix, for example Samba and smbclient. SMB is a presentation layer protocol structured as a large set of commands (Server Message Blocks). There are commands to support file sharing, printer sharing, {user authentication}, resource browsing, and other miscellaneous functions. As clients and servers may implement different versions ("dialects") of the protocol they negotiate before starting a session. The redirector packages SMB requests into a {network control block} (NBC) structure that can be sent across the network to a remote device. SMB originally ran on top of the lower level protocols NetBEUI and NetBIOS, but now typically runs over TCP/IP. Microsoft have developed an extended version of SMB for the Internet, the Common Internet File System (CIFS), which in most cases replaces SMB. CIFS runs only runs over TCP/IP. {Just what is SMB? (http://samba.anu.edu.au/cifs/docs/what-is-smb.html)}. {IBM protocols (http://protocols.com/pbook/ibm.htm)}. {Microsoft SMB/CIFS documents (ftp://ftp.microsoft.com/developr/drg/CIFS/)}. (1999-08-08)

<protocol> (CIFS) An Internet file system protocol, based on Microsoft's SMB. Microsoft has given CIFS to the Internet Engineering Task Force (IETF) as an Internet Draft. CIFS is intended to complement existing protocols such as HTTP, FTP, and NFS. CIFS runs on top of TCP/IP and uses the Internet's {Domain Name Service} (DNS). It is optimised to support the slower speed dial-up connections common on the Internet. CIFS is more flexible than FTP. FTP operations are carried out on entire files whereas CIFS is aimed at routine data access and incorporates high-performance multi-user read and write operations, locking, and file-sharing semantics. CIFS is probably closest in functionality to NFS. NFS gives random access to files and directories, but is stateless. With CIFS, once a file is open, state about the current access to that file is stored on both the client and the server. This allows changes on the server side to be notified to the clients that are interested. {Microsoft Overview (http://msdn.microsoft.com/library/en-us/fileio/base/cifs_smb_protocol_overview.asp)}. SNIA page (http://snia.org/tech_activities/CIFS/). {CIFS: A Common Internet File System, Paul Leach and Dan Perry (http://microsoft.com/Mind/1196/CIFS.htm)}. {IETF Specification. CIFS version 1 (ftp://ietf.org/internet-drafts/draft-leach-cifs-v1-spec-01.txt)}. (2003-03-12)