Introduction to Samba

The Samba package provides file and print services to SMB/CIFS clients and Windows networking to Linux clients. Samba can also be configured as a Windows Domain Controller replacement, a file/print server acting as a member of a Windows Active Directory domain and a NetBIOS (rfc1001/1002) nameserver (which among other things provides LAN browsing support).

This package is known to build and work properly using an LFS-7.4 platform.

Package Information

Samba Dependencies




popt-1.16, Linux-PAM-1.1.7, Cups-1.6.3, OpenLDAP-2.4.36, Gamin-0.1.10, acl-2.2.52, xfsprogs-3.1.11, MIT Kerberos V5-1.11.3, Python-2.7.5 (used only in parts of the test suite), libxslt-1.1.28 (used only for documentation), tdb, ctdb, libcap2-2.22, libunwind, Avahi-0.6.31, OpenAFS, and Valgrind (optionally used by the test suite)

User Notes:

Installation of Samba



If you wish to run the test suite after the binaries are built, you must add the --enable-socket-wrapper and --enable-selftest parameters to the configure script below. You may want to run configure with the --help parameter first. There may be other parameters needed to take advantage of optional dependencies.

Install Samba by running the following commands:

sed -i -e "/dmapi_lib/s/$/ldflags='-ltirpc',/" source3/wscript_build &&

./configure                            \
    --prefix=/usr                      \
    --sysconfdir=/etc                  \
    --localstatedir=/var               \
    --with-piddir=/run/samba           \
    --with-pammodulesdir=/lib/security \
    --enable-fhs                       \
    --enable-nss-wrapper               &&


To test the results, as the root user,issue: make quicktest (about 8 SBU). There are other targets (test, subunit-test) available, but take a very long (over 100 SBU) time.

Now, as the root user:

make install &&

mv -v /usr/lib/libnss_win{s,bind}.so*   /lib                       &&
ln -v -sf ../../lib/ /usr/lib/ &&
ln -v -sf ../../lib/    /usr/lib/    &&

install -v -m644    examples/smb.conf.default /etc/samba &&

mkdir -pv /etc/openldap/schema                        &&

install -v -m644    examples/LDAP/README              \
                    /etc/openldap/schema/README.LDAP  &&
install -v -m644    examples/LDAP/samba*              \
                    /etc/openldap/schema              &&
install -v -m755    examples/LDAP/{convert*,get*,ol*} \
                    /etc/openldap/schema              &&

install -v -m755 -d /usr/share/doc/samba-4.0.9 &&

install -v -m644    lib/ntdb/doc/design.pdf \
                    /usr/share/doc/samba-4.0.9 &&

ln -v -s ../../samba/swat  /usr/share/doc/samba-4.0.9

To create the html documents needed for swat (libxslt-1.1.28 required), do the following:

cd docs-xml &&
autoreconf  &&
./configure &&
make htmlman

Now, as the root user:

mkdir -pv                          /usr/share/samba/swat/help/manpages &&
cp output/htmldocs/manpages/*.html /usr/share/samba/swat/help/manpages

Command Explanations

sed ... source3/wscript_build: This command enables the build to complete when using libtirpc instead of the deprecated glibc rpc functions.

--sysconfdir=/etc: Sets the configuration file directory to avoid the default of /usr/etc.

--localstatedir=/var: Sets the variable data directory to avoid the default of /usr/var.

--with-fhs: Assigns all other file paths in a manner compliant with the Filesystem Hierarchy Standard (FHS).

--enable-nss-wrapper: Builds the nss-wrapper library.

--enable-socket-wrapper and --enable-selftest: These options are required to run the test suite.

mv -v /usr/lib/libnss_win{s,bind}.so* /lib: The nss libraries are installed in /usr/lib by default. Move them to /lib.

ln -v -sf ../../lib/ /usr/lib/ and ln -v -sf ../../lib/ /usr/lib/ These symlinks are required when applicates build against these libraries.

install -v -m644 examples/LDAP/* /etc/openldap/schema: These commands are used to copy sample Samba schemas to the OpenLDAP schema directory.

install -v -m644 ../examples/smb.conf.default /etc/samba: This copies a default smb.conf file into /etc/samba. This sample configuration will not work until you copy it to /etc/samba/smb.conf and make the appropriate changes for your installation. See the configuration section for minimum values which must be set.

Configuring Samba

Config Files


Printing to SMB Clients

If you use CUPS for print services, and you wish to print to a printer attached to an SMB client, you need to create an SMB backend device. To create the device, issue the following command as the root user:

ln -v -sf /usr/bin/smbspool /usr/lib/cups/backend/smb

Configuration Information

Due to the complexity and the many various uses for Samba, complete configuration for all the package's capabilities is well beyond the scope of the BLFS book. This section provides instructions to configure the /etc/samba/smb.conf file for two common scenarios. The complete contents of /etc/samba/smb.conf will depend on the purpose of Samba installation.



You may find it easier to copy the configuration parameters shown below into an empty /etc/samba/smb.conf file instead of copying and editing the default file as mentioned in the “Command Explanations” section. How you create/edit the /etc/samba/smb.conf file will be left up to you. Do ensure the file is only writeable by the root user (mode 644).

Scenario 1: Minimal Standalone Client-Only Installation

Choose this variant if you only want to transfer files using smbclient, mount Windows shares and print to Windows printers, and don't want to share your files and printers to Windows machines.

A /etc/samba/smb.conf file with the following three parameters is sufficient:

    workgroup = MYGROUP
    dos charset = cp850
    unix charset = ISO-8859-1

The values in this example specify that the computer belongs to a Windows workgroup named “MYGROUP”, uses the “cp850” character set on the wire when talking to MS-DOS and MS Windows 9x, and that the filenames are stored in the “ISO-8859-1” encoding on the disk. Adjust these values appropriately for your installation. The “unix charset” value must be the same as the output of locale charmap when executed with the LANG variable set to your preferred locale, otherwise the ls command may not display correct filenames of downloaded files.

There is no need to run any Samba servers in this scenario, thus you don't need to install the provided bootscripts.

Scenario 2: Standalone File/Print Server

Choose this variant if you want to share your files and printers to Windows machines in your workgroup in addition to the capabilities described in Scenario 1.

In this case, the /etc/samba/smb.conf.default file may be a good template to start from. Also add “dos charset” and “unix charset” parameters to the “[global]” section as described in Scenario 1 in order to prevent filename corruption.

The following configuration file creates a separate share for each user's home directory and also makes all printers available to Windows machines:

    workgroup = MYGROUP
    dos charset = cp850
    unix charset = ISO-8859-1

    comment = Home Directories
    browseable = no
    writable = yes

    comment = All Printers
    path = /var/spool/samba
    browseable = no
    guest ok = no
    printable = yes

Other parameters you may wish to customize in the “[global]” section include:

    server string =
    security =
    hosts allow =
    load printers =
    log file =
    max log size =
    socket options =
    local master =

Reference the comments in the /etc/samba/smb.conf.default file for information regarding these parameters.

Since the smbd and nmbd daemons are needed in this case, install the samba bootscript. Be sure to run smbpasswd (with the -a option to add users) to enable and set passwords for all accounts that need Samba access, or use the SWAT web interface (see below) to do the same. Using the default Samba passdb backend, any user you attempt to add will also be required to exist in the /etc/passwd file.

Advanced Requirements

More complex scenarios involving domain control or membership are possible. Such setups are advanced topics and cannot be adequately covered in BLFS. Many complete books have been written on these topics alone. Note that in some domain membership scenarios, the winbindd daemon and the corresponding bootscript are needed.

There is quite a bit of documentation available which covers many of these advanced configurations. Point your web browser to the links below to view some of the documentation included with the Samba package:

Boot Script

For your convenience, boot scripts have been provided for Samba. There are two included in the blfs-bootscripts-20130908 package. The first, samba, will start the smbd and nmbd daemons needed to provide SMB/CIFS services. The second script, winbind, starts the winbindd daemon, used for providing Windows domain services to Linux clients.

The default Samba installation uses the nobody user for guest access to the server. This can be overridden by setting the guest account = parameter in the /etc/samba/smb.conf file. If you utilize the guest account = parameter, ensure this user exists in the /etc/passwd file. To use the default user, issue the following commands as the root user:

groupadd -g 99 nogroup &&
useradd -c "Unprivileged Nobody" -d /dev/null -g nogroup \
    -s /bin/false -u 99 nobody

Install the samba script with the following command issued as the root user:

make install-samba

If you also need the winbindd script to resolve names from Windows clients, run:

make install-winbindd

Configuring SWAT

The SWAT (Samba Web Administration Tool) utility can be used for configuration of the Samba installation.

Setting up SWAT using xinetd

If not already done, add an entry to /etc/services file as the root user:

echo "swat            905/tcp" >> /etc/services

Create the Samba xinetd-2.3.15 file as /etc/xinetd.d/swat.



You may modify or remove the “only_from” line below to include other host(s). BLFS does not recommend doing this because of the security risk involved. However, in a home network environment, disclosure of the root password may be an acceptable risk.

cat >> /etc/xinetd.d/swat << "EOF"
# Begin /etc/xinetd.d/swat

service swat
    port            = 905
    socket_type     = stream
    wait            = no
    instances       = 5
    only_from       =
    user            = root
    server          = /usr/sbin/swat
    log_on_failure += USERID

# End /etc/xinetd.d/swat

Issue a killall -HUP xinetd to read the new /etc/xinetd.d/swat file.



If you linked Linux-PAM into the Samba build, you'll need to create an /etc/pam.d/samba file.

SWAT can now be launched by pointing your web browser to http://localhost:905.

Setting up SWAT using stunnel

A better way to set up SWAT for network access is through stunnel-4.56. For convenience, a boot scripts has been provided for SWAT via stunnel. First, create the stunnel configuration file:

cat >> /etc/stunnel/swat.conf << "EOF"
; File: /etc/stunnel/swat.conf

pid    = /run/
setuid = root
setgid = root
cert   = /etc/stunnel/stunnel.pem

accept = swat
exec   = /usr/sbin/swat


Next, install the swat bootscript:

make install-swat

After starting the SWAT boot script the tool can be accessed by pointing your web browser to https://localhost:905. Note: https. If access to the tool needs to be further restricted, then Iptables-1.4.20 can be used.


Installed Programs: cifsdd, dbwrap_tool, eventlogadm, gentest, ldbadd, ldbdel, ldbedit, ldbmodify, ldbrename, ldbsearch, locktest, masktest, ndrdump, net, nmbd, nmblookup, nmblookup4, ntlm_auth, oLschema2ldif, pdbedit, pidl, profiles, regdiff, regpatch, regshell, regtree, rpcclient, samba, samba_dnsupdate samba_kcc, samba_spnupdate, samba-tool, samba_upgradedns, sharesec, smbcacls, smbclient, smbclient4, smbcontrol, smbcquotas, smbd, smbget, smbpasswd, smbspool, smbstatus, smbta-util, smbtar, smbtree, smbtorture, swat, testparm, tdbbackup, tdbdump, tdbrestore, and tdbtool, winbindd, and wbinfo
Installed Libraries:,,,,,, the and PAM libraries, and assorted character set, filesystem and support modules.
Installed Directories: /etc/samba, /usr/include/samba-4.0, /usr/lib/samba, /usr/share/samba, /var/cache/samba, /var/lib/samba, /var/log/samba, /var/lock/samba, and /var/run/samba

Short Descriptions


is used to write records to eventlogs from STDIN, add the specified source and DLL eventlog registry entries and display the active eventlog names (from smb.conf).


is a command-line utility for adding records to an LDB database.


is a command-line program for deleting LDB database records.


allows you to edit LDB databases using your preferred editor.


allows you to modify records in an LDB database.


allows you to edit LDB databases using your preferred editor.


searches an LDB database for records matching a specified expression.


is a tool for administration of Samba and remote CIFS servers, similar to the net utility for DOS/Windows.


is the Samba NetBIOS name server.


is used to query NetBIOS names and map them to IP addresses.


is a tool to allow external access to Winbind's NTLM authentication function.


is a tool used to manage the SAM database.


is a utility that reports and changes SIDs in Windows registry files. It currently only supports Windows NT.


is used to execute MS-RPC client side functions.


manipulates share ACL permissions on SMB file shares.


is used to manipulate Windows NT access control lists.


is a SMB/CIFS access utility, similar to FTP.


is used to control running smbd, nmbd and winbindd daemons.


is used to manipulate Windows NT quotas on SMB file shares.


is the main Samba daemon which provides SMB/CIFS services to clients.


is a simple utility with wget-like semantics, that can download files from SMB servers. You can specify the files you would like to download on the command-line.


changes a user's Samba password.


sends a print job to an SMB printer.


reports current Samba connections.


is a shell script used for backing up SMB/CIFS shares directly to Linux tape drives or a file.


is a text-based SMB network browser.


is the Samba Web Administration Tool.


is a tool for backing up or validating the integrity of Samba .tdb files.


is a tool used to print the contents of a Samba .tdb file.


is a tool which allows simple database manipulation from the command line.


checks an smb.conf file for proper syntax.


queries a running winbindd daemon.


resolves names from Windows NT servers.

provides Name Service Switch API functions for resolving names from NT servers.

provides API functions for Samba's implementation of the Windows Internet Naming Service.

provides the API functions for the administration tools used for Samba and remote CIFS servers.

provides the API functions for the Samba SMB client tools.

provides API functions for accessing SMB share modes (locks etc.)

provides API functions for Windows domain client services.

Last updated on 2013-08-27 02:03:59 -0700