Samba for the Pi

Installing Samba on the Raspberry Pi

by Mark Stanley and Deve Krehbiel

The Raspberry Pi is one of the most versatile and useful machines out there sporting a 4 core processor allowing us to do some amazing things with a very small box. You can install many operating systems on the Pi, but the recommended one is Raspbian, a derivative of Debian Linux. Linux and Windows are two completely different things. There are many good things to say about each. One of the things that occurs to me in using Linux is that it came from a totally different philosophy. The graphical user interface is an afterthought. The command line is really the most efficient way to configure your Pi. This brings us to the reason why Mark and I want to provide you with this document. How much time do you have to invest in learning Linux? Our estimation is, you would rather spend your time with your Pi projects and let the Linux gurus handle the heavy lifting.

We started with Samba for a reason. I typed "samba" at the Pi's command prompt and a date appeared. The last revision date for the very latest Raspbian distribution dated July 7, 2017 had a Samba distribution of 2014. This means that the Raspbian Apt-Get system is sending you a Samba release that is 3 years old. Meanwhile, the guys over at Samba have put out 16 releases since then. So I asked in the Pi Forums about it and the usual "You DARE to insult our fearless leaders" responses ensued, but the truth is, they really didn't have a good response. I am sure the people responsible are doing their level best to get the latest and greatest out there for its customers. Wait! NO, this is the entire file and printer sharing vehicle for our Pi's. This is what is responsible for great programs like OctoPrint and many others to do its job. If there are security patches, improvements to the software, better ways to streamline the program, I want the latest!! I'm thinking you do too. Lets get started:

First, we should briefly talk about how to install the Distro version of Samba. Since a LOT of the work has been done for us, this is really easy. (Part of the exasperation)

To install the old version of Samba on your Pi:

sudo apt-get update
sudo apt-get upgrade
sudo apt-get install samba samba-common-bin
sudo nano /etc/samba/smb.conf and add the following to the bottom of the file:
[RaspiShare]
comment = RaspiShare Folder
path = /home/pi/
browseable = Yes
writeable = Yes
only guest = no
create mask = 0777
directory mask = 0777
public = no

sudo reboot
The end. Now on your windows machine go to Networks and in the line at the top, type \\the.pis.IP.address and your share will be visible.

Installing the Latest Version of Samba:

But this isn't about installing a 3 year old version on our Pi. This is about downloading the latest version from the source. This is more difficult and requires more time. This has been tested over and over so we know you have a very good chance at success. It's the best we can do if we want a newer version.

Lets start off making sure we have the latest Apt-Get updates and upgrades. These two lines ensure the Distribution is 'up to date'.

sudo apt-get install update
sudo apt-get install upgrade

Now we go to see what the latest version of Samba is by visiting their web site: Samba.org You will notice on their site on the right it has a link to the latest release download. Where it says "The source code can be downloaded now." Hover over the word downloaded, right click and Copy Link Address. With the proper link address available, in your Pi, type:

cd /home/Pi/Downloads (or wherever you choose to put the file so you know where it is), then:

sudo wget https://download.samba.org/pub/samba/stable/samba-4.8.0.tar.gz <-- substitute the latest filename. The above is the example from the latest release as of this writing.

Now we need to unzip the file:

sudo tar -xvf samba-4.8.0.tar.gz

For the following steps we need to be in that directory so:

cd /home/pi/Downloads/samba-4.6.7

Once it's downloaded and unzipped into your Pi, we have some Dependencies we need to take care of:

sudo apt-get install libacl1-dev gnutls-dev python-dev libldap2-dev libpam0g-dev libssl-dev

Those are the Dependency Files that will error if you do the following before the previous step. Next we need to configure:

sudo ./configure <-- takes about (5m39.736s) <-- Don't worry about all of the "not found" entries.

After ./configure you need to make the file. The below command cuts the make time in about a third. -j 4 tells it to make using all four of the Raspberry Pi's processor cores.

sudo make -j 4 <-- takes about (19m29.890s)

then:

sudo make install <-- takes about (15m39.509s)

The next thing we need to do is to set the Path parameters permanently:

sudo nano /etc/profile
add to the very bottom of the file:
export PATH=/usr/local/samba/bin/:/usr/local/samba/sbin/:$PATH

The rest of this instruction I give many thanks to Mark Stanley. He took the time to test all of these commands to get you up and running.

To make Samba work automatically from startup, we need to create a script. Put this script in /etc.init.d/ and name it samba

sudo nano -w /etc/init.d/samba
place the following script in the file:

#!/bin/sh
# /etc/init.d/samba
### BEGIN INIT INFO
# Provides: samba
# Required-Start: $network
# Required-Stop: $network
# Default-Start: 2 3 4 5
# Default-Stop: 0 1 6
# Short-Description: samba file sharing services
# Description: Auto boot on startup for Samba
### END INIT INFO
# chkconfig: 2345 91 35
# description: Initialization script for Samba
# chkconfig: 2345 91 35
#
# Make sure the configuration file exists
[ -f /etc/samba/smb.conf ] || exit 1

samba_start() {
          echo "Starting SMB services"
          /usr/local/samba/sbin/smbd -D
          echo "Starting NMB services"
          /usr/local/samba/sbin/nmbd -D
}
samba_stop() {
          echo -n "Stopping smbd"

          kill -15 $(</usr/local/samba/var/locks/smbd.pid)
          while [[ -f /usr/local/samba/var/locks/smbd.pid ]]; do echo -n .; sleep 1; done ; echo
          echo -n "Stopping nmbd"
          kill -15 $(</usr/local/samba/var/locks/nmbd.pid)
          while [[ -f /usr/local/samba/var/locks/nmbd.pid ]]; do echo -n .; sleep 1; done ; echo
}
samba_reload() {
          echo "Re-reading Samba configuration files"
          kill -HUP $(</usr/local/samba/var/locks/nmbd.pid)
}

# See how we were called
case "$1" in
          'start')
                    samba_start
                    ;;
          'stop')
                    samba_stop
                    ;;
          'restart')
                    samba_stop
                    sleep 1
                    samba_start
                    ;;
          'reload')
                    samba_reload
                    ;;
          *)
                    echo "Usage: $0 {start|stop|restart|reload}"
                    ;;
esac

Once the script is safely in the file, we need to tell the Pi we want that script to be executable:

sudo chmod +x /etc/init.d/samba

Next we need to update the system to allow the script to run at startup:

sudo update-rc.d samba defaults

sudo reboot

Now let's talk a little about the Samba Main Configuration file located in /usr/local/samba/etc/smb.conf. Here is a typical working smb.conf file. To use the one that came with the package, do a sudo find -name smb.conf from the top directory. This config enables a share to be available in Windows 10.

To edit this file: sudo nano /usr/local/samba/etc/smb.conf

NOTE: if the nano window is blank, copy the below script into your nano window or get one that comes with the package via sudo find -name smb.conf as mentioned earlier.

This is the configuration file for your Shares. If you do this one exactly as it is below, you will get one Share named RaspiShare with the directories allowed by the user Pi. If you wish to see all directories on the Pi, near the end of the file, change Path (under RaspiShare) to just a forward slash.

#
# Sample configuration file for the Samba suite for Debian GNU/ Linux.
#
#
# This is the main Samba configuration file. You should read the
# smb.conf(5) manual page in order to understand the options listed
# here. Samba has a huge number of configurable options most of which
# are not shown in this example
#
# Some options that are often worth tuning have been included as
# commented-out examples in this file.
# - When such options are commented with ";", the proposed setting
# differs from the default Samba behaviour
# - When commented with "#", the proposed setting is the default
# behaviour of Samba but the option is considered important
# enough to be mentioned here
#
# NOTE: Whenever you modify this file you should run the command
# "testparm" to check that you have not made any basic syntactic
# errors.

#======================= Global Settings =======================

[global]

## Browsing/Identification ###

# Change this to the workgroup/NT-domain name your Samba server will part of
   workgroup = WORKGROUP

# Windows Internet Name Serving Support Section:
# WINS Support - Tells the NMBD component of Samba to enable its WINS Server
# wins support = no

# WINS Server - Tells the NMBD components of Samba to be a WINS Client
# Note: Samba can be either a WINS Server, or a WINS Client, but NOT both
; wins server = w.x.y.z

# This will prevent nmbd to search for NetBIOS names through DNS.
  dns proxy = no

#### Networking ####

# The specific set of interfaces / networks to bind to
# This can be either the interface name or an IP address/netmask;
# interface names are normally preferred
; interfaces = 127.0.0.0/8 eth0

# Only bind to the named interfaces and/or networks; you must use the
# 'interfaces' option above to use this.
# It is recommended that you enable this feature if your Samba machine is
# not protected by a firewall or is a firewall itself. However, this
# option cannot handle dynamic or non-broadcast interfaces correctly.
; bind interfaces only = yes

#### Debugging/Accounting ####

# This tells Samba to use a separate log file for each machine
# that connects
   log file = /var/log/samba/log.%m

# Cap the size of the individual log files (in KiB).
   max log size = 1000

# If you want Samba to only log through syslog then set the following
# parameter to 'yes'.
# syslog only = no

# We want Samba to log a minimum amount of information to syslog. Everything
# should go to /var/log/samba/log.{smbd,nmbd} instead. If you want to log
# through syslog you should set the following parameter to something higher.
   logging = syslog@0 file

# Do something sensible when Samba crashes: mail the admin a backtrace
   panic action = /usr/share/samba/panic-action %d

####### Authentication #######

# Server role. Defines in which mode Samba will operate. Possible
# values are "standalone server", "member server", "classic primary
# domain controller", "classic backup domain controller", "active
# directory domain controller".
#
# Most people will want "standalone sever" or "member server".
# Running as "active directory domain controller" will require first
# running "samba-tool domain provision" to wipe databases and create a
# new domain.
   server role = standalone server

# If you are using encrypted passwords, Samba will need to know what
# password database type you are using.
   passdb backend = tdbsam

   obey pam restrictions = yes

# This boolean parameter controls whether Samba attempts to sync the Unix
# password with the SMB password when the encrypted SMB password in the
# passdb is changed.
   unix password sync = yes

# For Unix password sync to work on a Debian GNU/Linux system, the following
# parameters must be set (thanks to Ian Kahan)
# sending the correct chat script for the passwd program in Debian Sarge).
   passwd program=/usr/bin/passwd %u
   passwd chat = *new*password* %n\n *new*password* %n\n *changed*

# This boolean controls whether PAM will be used for password changes
# when requested by an SMB client instead of the program listed in
# 'passwd program' . The default is 'no' .
   pam password change=yes

# This option controls how unsuccessful authentication attempts are mapped
# to anonymous connections
   map to guest=bad user

########## Domains ###########

#
# The following settings only takes effect if 'server role = primary
# classic domain controller' , 'server role = backup domain controller'
# or 'domain logons' is set
#

# It specifies the location of the user's
# profile directory from the client point of view) The following
# required a [profiles] share to be setup on the samba server (see
# below)
; logon path=\\%N\profiles\%U

# Another common choice is storing the profile in the user's home directory
# (this is Samba's default)
# logon path=\\%N\%U\profile

# The following setting only takes effect if 'domain logons' is set
# It specifies the location of a user's home directory (from the client
# point of view)
; logon drive=H:
# logon home=\\%N\%U

# The following setting only takes effect if 'domain logons' is set
# It specifies the script to run during logon. The script must be stored
# in the [netlogon] share
# NOTE: Must be store in 'DOS' file format convention
; logon script=logon.cmd

# This allows Unix users to be created on the domain controller via the SAMR
# RPC pipe. The example command creates a user account with a disabled Unix
# password; please adapt to your needs
; add user script=/usr/sbin/adduser --quiet --disabled-password --gecos "" %u

# This allows machine accounts to be created on the domain controller via the
# SAMR RPC pipe.
# The following assumes a "machines" group exists on the system
; add machine script=/usr/sbin/useradd -g machines -c "%u machine account" -$

# This allows Unix groups to be created on the domain controller via the SAMR
# RPC pipe.
; add group script=/usr/sbin/addgroup --force-badname %g

############ Misc ############

# Using the following line enables you to customise your configuration
# on a per machine basis. The %m gets replaced with the netbios name
# of the machine that is connecting
; include=/home/samba/etc/smb.conf.%m

# Some defaults for winbind (make sure you're not using the ranges
# for something else.)
; idmap uid=10000-20000
; idmap gid=10000-20000
; template shell=/bin/bash

# Setup usershare options to enable non-root users to share folders
# with the net usershare command.

# Maximum number of usershare. 0 (default) means that usershare is disabled.
; usershare max shares=100

# Allow users who've been granted usershare privileges to create
# public shares, not just authenticated ones
   usershare allow guests=yes

#=======================Share Definitions=======================
[home]
   comment=Home Directory
   browseable=no
   path=/

# By default, the home directories are exported read-only. Change the
# next parameter to 'no' if you want to be able to write to them.
   read only=yes

# File creation mask is set to 0700 for security reasons. If you want to
# create files with group=rw permissions, set next parameter to 0775.
   create mask=0700

# Directory creation mask is set to 0700 for security reasons. If you want to
# create dirs. with group=rw permissions, set next parameter to 0775.
   directory mask=0700

# By default, \\server\username shares can be connected to by anyone
# with access to the samba server.
# The following parameter makes sure that only "username" can connect
# to \\server\username
# This might need tweaking when using external authentication schemes
   valid users=%S

# Un-comment the following and create the netlogon directory for Domain Logons
# (you need to configure Samba to act as a domain controller too.)
;[netlogon]
; comment=Network Logon Service
; path=/home/samba/netlogon
; guest ok=yes
; read only=yes

# Un-comment the following and create the profiles directory to store
# users profiles (see the "logon path" option above)
# (you need to configure Samba to act as a domain controller too.)
# The path below should be writable by all users so that their
# profile directory may be created the first time they log on
;[profiles]
; comment=Users profiles
; path=/home/samba/profiles
; guest ok=no
; browseable=no
; create mask=0600
; directory mask=0700

[printers]
   comment=All Printers
   browseable=no
   path=/var/spool/samba
   printable=yes
   guest ok=no
   read only=yes
   create mask=0700

# Windows clients look for this share name as a source of downloadable
# printer drivers
[print$]
   comment=Printer Drivers
   path=/var/lib/samba/printers
   browseable=yes
   read only=yes
   guest ok=no
# Uncomment to allow remote administration of Windows print drivers.
# You may need to replace 'lpadmin' with the name of the group your
# admin users are members of.
# Please note that you also need to set appropriate Unix permissions
# to the drivers directory for these users to have write rights in it
; write list=root, @lpadmin

[RaspiShare]
   comment=RaspiShare Folder
   path=/home/pi/
   browseable=Yes
   writeable=Yes
   only guest=no
   create mask=0777
   directory mask=0777
   public=yes
#END

You will notice near the top the networks group name is WORKGROUP. This is because most Windows machines use WORKGROUP for their network name. If yours is different, change it there. Other than that ONE possible change, this configuration file is pretty much ready. No need to activate Wins Support, that does not apply to most of us, The last 9 lines are the most important for your share. You can change the name within the brackets from [RaspiShare] to anything you want. You can change the path to a simple / if you want access to all of the files on the Pi. You can change permissions here as well. If everything is going good so far, at the command prompt type:

testparm

If this command is successful, you are good to go. This is Samba's way of checking the smb.conf file for human error. You can also type:

samba

This will give you the revision number of the installation. Just to prove to yourself you have the latest downloaded version.

To see the Share on the Windows machine is not very automatic. I wish it were, but this is a mystery that is above my pay-grade. Go to the Network window on your Windows machine. In the command line near the top, type \\IP.ADDRESS.OFYOUR.PI <-- be sure to use back slashes and the correct IP address of that specific Pi. If all is well, your share will appear in the window. Why it doesn't see it automatically is a mystery of the ages. But if you want that Pi to have a more Permanent Share, right click on the Share [RaspiShare] or whatever you named it in the config file, and choose Map Network Drive. Choose a safe drive letter, I like to use ones near the end of the alphabet so there are no conflicts and now that share will show up in your File system as long as the Pi is turned on.

But, there is one thing you cannot do from this file.. Each of the files and directories on your Pi have permissions. Those permissions apply where-ever you see them. So if you try to copy something from the Windows machine into the Pi and you did not set your file permissions accordingly, Windows will tell you Permission Denied. For example, here is a common ls -l.

pi@raspberrypi:/ $ cd /home/pi
pi@raspberrypi:~ $ ls
Desktop Downloads Pictures python_games Videos
Documents Music Public Templates
pi@raspberrypi:~ $ ls -l
total 36
drwxr-xr-x 2 pi pi 4096 Jul 5 07:01 Desktop
drwxr-xr-x 5 pi pi 4096 Jul 5 06:29 Documents
drwxr-xr-x 3 pi pi 4096 Aug 12 14:16 Downloads
drwxr-xr-x 2 pi pi 4096 Jul 5 07:01 Music
drwxr-xr-x 2 pi pi 4096 Jul 5 07:01 Pictures
drwxr-xr-x 2 pi pi 4096 Jul 5 07:01 Public
drwxr-xr-x 2 pi pi 4096 Jul 5 06:29 python_games
drwxr-xr-x 2 pi pi 4096 Jul 5 07:01 Templates
drwxr-xr-x 2 pi pi 4096 Jul 5 07:01 Videos

You will see as a remote user, you do not have permission to even write to the Downloads directory! You can SEE the directory on your Windows machine, you just cannot write to it. To change that:

sudo chmod 0777 Downloads

Now, Downloads has the correct permissions for the Windows machine to read, write and erase the files within.

drwxrwxrwx 3 pi pi 4096 Aug 12 14:16 Downloads

So that is all there is to it! If you see anything in this document that is incorrect or outdated, please feel free to email deve@speedprint.com. For technical questions it is a very good idea to use the Raspberry Pi Forums to ask your questions. This way more people can better explain things.

More References

http://raspberrypihq.com/how-to-share-a-folder-with-a-windows-computer-from-a-raspberry-pi/
https://forum.e3d-online.com/index.php?threads/setting-up-samba-on-the-raspberry-pi-to-make-file-transfers-simple.1763/
https://wiki.samba.org/index.php/Build_Samba_from_Source
https://wiki.debian.org/EnvironmentVariables