Samba (software)
Samba is a free software program. It helps computers use the SMB networking protocol. It was originally developed by Andrew Tridgell. This article is about computer software. For other uses, see Samba (disambiguation).
Samba gives file and print services to many Microsoft Windows clients. It can also work with a Microsoft Windows Server domain. It can act as a Domain Controller (DC), or it can be a member of a domain. Since version 4, Samba also supports Active Directory domains. Before that, it supported only Microsoft Windows NT domains.
Samba runs on most Unix-like systems. These include Linux, Solaris, AIX, and the BSD variants. It also runs on Apple macOS (Mac OS X 10.2 and greater) and macOS Server. Samba works on other operating systems too, such as OpenVMS and IBM i. It is standard on nearly all distributions of Linux, and it is often included as a basic system service on other Unix-based systems.
Samba is released under the GNU General Public License. Its name comes from SMB (Server Message Block), the name of the private protocol used by the Microsoft Windows network file system.
Early history
Andrew Tridgell wrote the first version of Samba for Unix in December 1991 and January 1992, while he was a PhD student at the Australian National University. He used a packet sniffer and network analysis to study the protocol used by DEC Pathworks server software. The first releases had no formal name. Tridgell simply called it "a Unix file server for Dos Pathworks."
Tridgell focused on working well with Microsoft's LAN Manager and released version 1.5 in December 1993. It was the first release to include client software as well as a server. The program was first named smbserver, but a company called Syntax sent Tridgell a trademark notice because it owned the name "SMBserver." The name "Samba" was then found by running the Unix command grep through the system dictionary to find words with the letters S, M, and B in that order. Tridgell considers the adoption of CVS in May 1996 to mark the birth of the Samba Team, though Jeremy Allison and others had contributed earlier. Version 2.0.0 was a major release in January 1999, and version 2.2.0 came out in April 2001.
Version history
| Date | Version | Description |
|---|---|---|
| 23 September 2003 | Unsupported: 3.0 | Active Directory support. The 3.0.x series officially reached end-of-life on 5 August 2009. |
| 1 July 2008 | Unsupported: 3.2 | It will be updated on an as-needed basis for security issues only. There was a change of license from GPL2 to GPL3, with some parts released under LGPL3. The 3.2.x series officially reached EOL 1 March 2010. |
| 27 January 2009 | Unsupported: 3.3 | |
| 3 July 2009 | Unsupported: 3.4 | This was the first release to include both Samba 3 and Samba 4 source code. |
| 1 March 2010 | Unsupported: 3.5 | This was the first release to include experimental support for SMB2. |
| 9 August 2011 | Unsupported: 3.6 | This is the first branch to include full support for SMB2. |
| 11 December 2012 | Unsupported: 4.0 | A major rewrite that enables Samba to be an Active Directory domain controller, participating fully in a Windows Active Directory Domain. Its first technical preview (4.0.0TP1) was released in January 2006 after 3 years of development. |
| 10 October 2013 | Unsupported: 4.1 | Support for SMB3. |
| 4 March 2015 | Unsupported: 4.2 | Btrfs based file compression, snapshots and winbind integration |
| 8 September 2015 | Unsupported: 4.3 | New Logging features, SMB 3.1.1 support. |
| 22 March 2016 | Unsupported: 4.4 | Asynchronous flush requests |
| 7 September 2016 | Unsupported: 4.5 | NTLM v1 disabled by default, Virtual List View, Various performance improvements. |
| 7 March 2017 | Unsupported: 4.6 | Multi-process Netlogon support. |
| 21 September 2017 | Unsupported: 4.7 | Samba AD with MIT Kerberos. |
| 13 March 2018 | Unsupported: 4.8 | Apple Time Machine support. Setups using 'domain' or 'ads' security modes now require 'winbindd' to be running. |
| 13 September 2018 | Unsupported: 4.9 | Many changes. |
| 19 March 2019 | Unsupported: 4.10 | |
| 17 September 2019 | Unsupported: 4.11 | SMB1 is disabled by default as a mitigation for the WannaCry vulnerability. |
| 3 March 2020 | Unsupported: 4.12 | |
| 22 September 2020 | Unsupported: 4.13 | Samba 4.13 raises the minimum version of Python to 3.6. |
| 9 March 2021 | Unsupported: 4.14 | Major overhaul of VFS subsystem and more. |
| 20 September 2021 | Unsupported: 4.15 | Many changes. |
| 21 March 2022 | Unsupported: 4.16 | Many changes. |
| 13 September 2022 | Unsupported: 4.17 | Many changes. |
| 8 March 2023 | Unsupported: 4.18 | Many changes. |
| 4 September 2023 | Unsupported: 4.19 | Many changes. |
| 27 March 2024 | Supported: 4.20 | Many changes. |
| 2 September 2024 | Supported: 4.21 | Many changes. |
| 6 March 2025 | Supported: 4.22 | SMB3 Directory Leases are supported, Netlogon Ping can be done over LDAP and LDAPS, experimental Himmelblau authentication for Azure Entra ID, performance improvements, nmbd proxy logon feature is removed. |
| 12 September 2025 | Supported: 4.23 | Many changes. |
| 18 March 2026 | Latest version: 4.24 | Many changes. |
Security
Some versions of Samba 3.6.3 and lower have serious security problems. These can allow anonymous users to gain root access to a system through an anonymous connection, by taking advantage of an error in Samba's remote procedure call. In April 2016, Badlock, a serious security bug in Windows and Samba, was revealed. It is known as CVE-2016-2118.
In May 2017, a weakness that let others run code on a computer remotely was found in Samba. It was called EternalRed or SambaCry and affected all versions since 3.5.0. In September 2020, a proof-of-concept exploit was published for a vulnerability in Samba's netlogon system, called Zerologon (CVE-2020-1472). A patch for it has been available since August. Some federal agencies that use the software have been ordered to install the patch.
Features
Samba allows file and print sharing between computers running Microsoft Windows and computers running Unix. It is an implementation of dozens of services and a dozen protocols, including NetBIOS over TCP/IP (NBT), SMB, DCE/RPC or more specifically MSRPC, a WINS server, the Security Account Manager database, the Local Security Authority service, NTLM, Active Directory logon using Kerberos and LDAP, and a DFS server. Many of these services are wrongly called just NetBIOS or SMB. On Windows, the NBT and WINS protocols and SMB version 1 are no longer recommended. Since Windows Vista, the WS-Discovery protocol has been included, and it works with newer versions of SMB. On Unix-like systems, third-party daemons help Samba shares be found when the older protocols are turned off.
Samba sets up network shares for chosen Unix directories, including their subdirectories. Windows users see these as normal folders on the network. Unix users can mount the shares as part of their own file system, or use a tool called smbclient, which works like a standard command line FTP program. Each directory can have its own access permissions on top of normal Unix file protections. Samba services run as two daemons, smbd and nmbd, and are set up by editing one file. Samba can also provide user logon scripts. It is included in most Linux distributions. The OS/2-based ArcaOS includes Samba to replace the old IBM LAN Server software. Earlier versions had a web tool called SWAT, which was removed starting with version 4.1.
Samba TNG
Samba TNG (The Next Generation) was forked in late 1999, after the Samba Team leaders and Luke Leighton disagreed about the direction of the Samba project. They could not agree on a way for his research version, then called Samba-NTDOM, to slowly become part of Samba. Development was slow because there were few developers, and the Samba TNG team often pointed possible users to Samba because it had better support and development. A main goal of the project was to rewrite all the NT Domains services as FreeDCE projects. This was hard because the services had been built by hand through network reverse-engineering, with little or no reference to documentation.
The two projects handled the NT Domains protocols and MSRPC services differently. Samba offers all the NT Domains services from one place, while Samba TNG placed each service in its own program. ReactOS began using Samba TNG services for its SMB implementation, and the developers of both projects worked together to adapt the network code and build system. Samba TNG now seems to be abandoned and no longer maintained, and its website is offline except for an archive from 2016.

Quiz time!
5 questions about Samba (software)
Where does the name "Samba" come from?
Keep exploring
This article is a child-friendly adaptation of the Wikipedia article on Samba (software), available under CC BY-SA 4.0.
Images from Wikimedia Commons. Tap any image to view credits and license.