Chapter 1. How to Install and Test SAMBA

+ Binary packages of Samba are included in almost any Linux or UNIX distribution. There are also some packages available at the Samba home page. Refer to the manual of your operating system for details on installing packages for your specific operating system.

- + If you need to compile Samba from source, check How to Compile Samba. -

Configuring Samba (smb.conf)

- - +

Configuring Samba (smb.conf)

+ + Samba's configuration is stored in the smb.conf file, which usually resides in /etc/samba/smb.conf or /usr/local/samba/lib/smb.conf. You can either edit this file yourself or do it using one of the many graphical tools that are available, such as the Web-based interface SWAT, that is included with Samba. -

Configuration File Syntax

- +

Configuration File Syntax

+ The smb.conf file uses the same syntax as the various old .ini files in Windows 3.1: Each file consists of various sections, which are started by putting the section name between brackets ([]) on a new line. Each contains zero or more key/value pairs separated by an equality sign (=). The file is just a plaintext file, so you can open and edit it with your favorite editing tool.

- - - - - - + + + + + + Each section in the smb.conf file represents either a share or a meta-service on the Samba server. The section [global] is special, since it contains settings that apply to the whole Samba server. Samba supports a number of meta-services, each of which serves its own purpose. For example, the @@ -35,12 +35,12 @@ and that specifies the location of the intermediate spool directory into which print jobs are received from Windows clients prior to being dispatched to the UNIX/Linux print spooler.

- - - - - - + + + + + + The printers meta-service will cause every printer that is either specified in a printcap file, via the lpstat, or via the CUPS API, to be published as a shared print queue. The printers stanza in the smb.conf file can @@ -49,20 +49,20 @@ available as Windows print queues. If a comment parameter is specified, the value of it will be displayed as part of the printer name in Windows Explorer browse lists.

- + Each section of the smb.conf file that specifies a share, or a meta-service, is called a stanza. The global stanza specifies settings that affect all the other stanzas in the smb.conf file. Configuration parameters are documented in the smb.conf man page. Some parameters can be used only in the global stanza, some only in share or meta-service stanzas, and some can be used globally or just within a share or meta-service stanza.

- + A minimal smb.conf contains a very minimal smb.conf. - -

Example 1.1. A minimal smb.conf

[global]

workgroup = WKG

netbios name = MYNAME

[share1]

path = /tmp

[share2]

path = /my_shared_folder

comment = Some random files

TDB Database File Information

+ +

Example 1.1. A minimal smb.conf

[global]

workgroup = WKG

netbios name = MYNAME

[share1]

path = /tmp

[share2]

path = /my_shared_folder

comment = Some random files

TDB Database File Information

This section contains brief descriptions of the databases that are used by Samba-3.

- + The directory in which Samba stores the tdb files is determined by compile-time directives. Samba-3 stores tdb files in two locations. The best way to determine these locations is to execute the following command: @@ -80,7 +80,7 @@ Therefore the remaining control files will, in the example shown, be stored in the /var/lib/samba directory.

- + The persistent tdb files are described in the Persistent TDB File Descriptions table. All persistent tdb files should be regularly backed up. Use the tdbbackup utility to backup the tdb files. All persistent tdb files must be @@ -106,27 +106,27 @@ information so that clients that have temporarily disconnected can reconnect without needing to renegotiate the connection setup process.

nosessionid

Temporary cache for miscellaneous session information and for utmp handling.

nounexpected

Stores packets received for which no process is actively listening.

nowinbindd_cache

Cache of Identity information received from an NT4 domain or from ADS. Includes user - lists, etc.

yes

Starting Samba

- + lists, etc.

yes

Starting Samba

+ Samba essentially consists of two or three daemons. A daemon is a UNIX application that runs in the background and provides services. An example of a service is the Apache Web server for which the daemon is called httpd. In the case of Samba there are three daemons, two of which are needed as a minimum.

The Samba server is made up of the following daemons:

nmbd: - - + + This daemon handles all name registration and resolution requests. It is the primary vehicle involved in network browsing. It handles all UDP-based protocols. The nmbd daemon should be the first command started as part of the Samba startup process.
smbd: - - + + This daemon handles all TCP/IP-based connection services for file- and print-based operations. It also manages local authentication. It should be started immediately following the startup of nmbd.
winbindd: - - + + This daemon should be started when Samba is a member of a Windows NT4 or ADS domain. It is also needed when Samba has trust relationships with another domain. The winbindd daemon will check the smb.conf file for the presence of the idmap uid and idmap gid @@ -134,36 +134,36 @@ for UID and GID allocation. If these parameters are not specified, winbindd will start but it will not be able to allocate UIDs or GIDs.

- + When Samba has been packaged by an operating system vendor, the startup process is typically a custom feature of its integration into the platform as a whole. Please refer to your operating system platform administration manuals for specific information pertaining to correct management of Samba startup. -

Example Configuration

- - - - - +

Example Configuration

+ + + + + There are sample configuration files in the examples subdirectory in the source code distribution tarball package. It is suggested you read them carefully so you can see how the options go together in practice. See the man page for all the options. It might be worthwhile to start out with the smb.conf.default configuration file and adapt it to your needs. It contains plenty of comments.

- + The simplest useful configuration file would contain something like that shown in Another simple smb.conf File. - -

Example 1.2. Another simple smb.conf File

[global]

workgroup = MIDEARTH

[homes]

guest ok = no

read only = no

- - - - + +

Example 1.2. Another simple smb.conf File

[global]

workgroup = MIDEARTH

[homes]

guest ok = no

read only = no

+ + + + This will allow connections by anyone with an account on the server, using either their login name or homes as the service name. (Note: The workgroup that Samba should appear in must also be set. The default workgroup name is WORKGROUP.)

- + Make sure you put the smb.conf file in the correct place. Note, the correct location of this file depends on how the binary files were built. You can discover the correct location by executing from the directory that contains the smbd command file: @@ -171,13 +171,13 @@ root# smbd -b | grep smb.conf

- + For more information about security settings for the [homes] share, please refer to Securing Samba. -

Test Your Config File with `testparm`

- - - +

Test Your Config File with `testparm`

+ + + It's important to validate the contents of the smb.conf file using the testparm program. If testparm runs correctly, it will list the loaded services. If not, it will give an error message. Make sure it runs correctly and that the services look reasonable before proceeding. Enter the command: @@ -189,10 +189,10 @@

Always run testparm again whenever the smb.conf file is changed!

- - - - + + + + The smb.conf file is constantly checked by the Samba daemons smbd and every instance of itself that it spawns, nmbd and winbindd. It is good practice to keep this file as small as possible. Many administrators prefer to document Samba configuration settings @@ -205,8 +205,8 @@

This administrative method makes it possible to maintain detailed configuration change records while at the same time keeping the working smb.conf file size to the minimum necessary. -

SWAT

- +

SWAT

+ SWAT is a Web-based interface that can be used to facilitate the configuration of Samba. SWAT might not be available in the Samba package that shipped with your platform, but in a separate package. If it is necesaary to built SWAT please read the SWAT man page regarding compilation, installation, and @@ -221,7 +221,7 @@ machine leaves your connection open to password sniffing because passwords will be sent over the wire in the clear.

More information about SWAT can be found in The Samba Web Administration Tool. -