Chapter 2. 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 homepage. @@ -8,29 +9,29 @@ appropriate appendix chapter.

If you have already installed samba, or if your operating system was pre-installed with samba, then you may not need to bother with this chapter. On the other hand, you may want to read this chapter anyhow - for information about updating samba.

Configuring samba (smb.conf)

+ for information about updating samba.

Configuring samba (smb.conf)

Samba's configuration is stored in the smb.conf file, that 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. -

Example Configuration

There are sample configuration files in the examples subdirectory in the distribution. I suggest you read them carefully so you can see how the options go together in practice. See the man page for all the options.

The simplest useful configuration file would be something like this: -

+	

+	 	[global]
 		workgroup = MYGROUP
 
 	[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 that the workgroup that Samba must also be set.) @@ -42,7 +43,7 @@ For more information about security settings for the [homes] share please refer to the chapter Securing Samba. -

Test your config file with testparm

It's important that you test the validity of your smb.conf file using the testparm program. If testparm runs OK then it will list the loaded services. If not it will give an error message. @@ -50,7 +51,7 @@ Make sure it runs OK and that the services look reasonable before proceeding.

Always run testparm again when you change smb.conf! -

SWAT

SWAT is a web-based interface that helps you configure samba. SWAT might not be available in the samba package on your platform, but in a separate package. Please read the swat manpage @@ -66,7 +67,7 @@ machine but connecting from a remote machine leaves your connection open to password sniffing as passwords will be sent in the clear over the wire. -

Try listing the shares available on your +

Try listing the shares available on your server

$ smbclient -L yourhostname

You should get back a list of shares available on your server. If you don't then something is incorrectly setup. @@ -76,7 +77,7 @@ See the smbclient man page for details. (you can force it to list the shares without a password by adding the option -U% to the command line. This will not work - with non-Samba servers)

Try connecting with the unix client

$ smbclient + with non-Samba servers)

`Try connecting with the unix client`

$ smbclient //yourhostname/aservice

Typically the yourhostname would be the name of the host where you installed smbd. The aservice is @@ -85,18 +86,18 @@ section in smb.conf.

For example if your unix host is bambi and your login name is fred you would type:

$ smbclient //bambi/fred -

`Try connecting from a DOS, WfWg, Win9x, WinNT, +`

Try connecting from a DOS, WfWg, Win9x, WinNT, Win2k, OS/2, etc... client

Try mounting disks. eg:

C:\WINDOWS\> net use d: \\servername\service

Try printing. eg:

C:\WINDOWS\> net use lpt1: \\servername\spoolservice

C:\WINDOWS\> print filename -

What If Things Don't Work?

Then you might read the file chapter +

What If Things Don't Work?

Then you might read the file chapter Diagnosis and the FAQ. If you are still stuck then try to follow the Analysing and Solving Problems chapter Samba has been successfully installed at thousands of sites worldwide, - so maybe someone else has hit your problem and has overcome it.

Common Errors

+ so maybe someone else has hit your problem and has overcome it.

Common Errors

The following questions and issues get raised on the samba mailing list over and over again. -

Why are so many smbd processes eating memory?

“ Site that is running Samba on an AIX box. They are sharing out about 2 terabytes using samba. Samba was installed using smitty and the binaries. We seem to be experiencing a memory problem @@ -108,8 +109,8 @@ processes of smbd running: Is samba suppose to start this many different smbd processes? Or does it run as one smbd process? Also is it normal for it to be taking up this much memory? ” -

+

+ Inuse * 4096 = amount of memory being used by this process
 
      Pid Command        Inuse      Pin     Pgsp  Virtual   64-bit    Mthrd
@@ -136,8 +137,8 @@ Inuse * 4096 = amount of memory being used by this process
    19110 smbd            8404     1906      181     4862        N        N
 
    Total memory used:  841,592,832 bytes
-

-

+

+
Samba consists on three core programs: nmbd, smbd, winbindd. nmbd is the name server message daemon, smbd is the server message daemon, winbindd is the daemon that @@ -152,4 +153,4 @@ connection made. That is why you are seeing so many of them, one (1) per client
winbindd will run as one or two daemons, depending on whether or not it is being run in "split mode" (in which case there will be two instances). -

I'm getting "open_oplock_ipc: Failed to get local UDP socket for address 100007f. Error was Cannot assign requested" in the logs

Your loopback device isn't working correctly. Make sure it's running.

Prev	Up	Next
Chapter 1. Introduction to Samba	Home	Chapter 3. FastStart for the Impatient

I'm getting "open_oplock_ipc: Failed to get local UDP socket for address 100007f. Error was Cannot assign requested" in the logs

Your loopback device isn't working correctly. Make sure it's running.

Prev	Up	Next
Chapter 1. Introduction to Samba	Home	Chapter 3. FastStart for the Impatient

-- cgit