Difference between revisions of "Samba"

From ArchWiki
Jump to: navigation, search
m (Capital letters. Style fixes.)
(style, see Help:Style)
(9 intermediate revisions by 7 users not shown)
Line 2: Line 2:
 
[[Category:Networking]]
 
[[Category:Networking]]
 
[[cs:Samba]]
 
[[cs:Samba]]
[[de:Samba]]
 
 
[[da:Samba]]
 
[[da:Samba]]
 +
[[de:Samba]]
 
[[es:Samba]]
 
[[es:Samba]]
 
[[fr:Samba]]
 
[[fr:Samba]]
 
[[it:Samba]]
 
[[it:Samba]]
 +
[[ja:Samba]]
 
[[ru:Samba]]
 
[[ru:Samba]]
 
[[sr:Samba]]
 
[[sr:Samba]]
Line 12: Line 13:
 
[[zh-CN:Samba]]
 
[[zh-CN:Samba]]
 
[[zh-TW:Samba]]
 
[[zh-TW:Samba]]
[[ja:Samba]]
 
 
{{Article summary start|Summary}}
 
{{Article summary start|Summary}}
 
{{Article summary text|Installing, configuring and troubleshooting Samba}}
 
{{Article summary text|Installing, configuring and troubleshooting Samba}}
 
{{Article summary heading|Related}}
 
{{Article summary heading|Related}}
 +
{{Article summary wiki|Samba/Tips and tricks}}
 +
{{Article summary wiki|Samba/Troubleshooting}}
 
{{Article summary wiki|NFS}}
 
{{Article summary wiki|NFS}}
 
{{Article summary wiki|Samba Domain Controller}}
 
{{Article summary wiki|Samba Domain Controller}}
 
{{Article summary wiki|Active Directory Integration}}
 
{{Article summary wiki|Active Directory Integration}}
 
{{Article summary end}}
 
{{Article summary end}}
 +
 
'''Samba''' is a re-implementation of the SMB/CIFS networking protocol, it facilitates file and printer sharing among Linux and Windows systems as an alternative to [[NFS]]. Some users say that Samba is easily configured and that operation is very straight-forward. However, many new users run into problems with its complexity and non-intuitive mechanism. It is strongly suggested that the user stick close to the following directions.
 
'''Samba''' is a re-implementation of the SMB/CIFS networking protocol, it facilitates file and printer sharing among Linux and Windows systems as an alternative to [[NFS]]. Some users say that Samba is easily configured and that operation is very straight-forward. However, many new users run into problems with its complexity and non-intuitive mechanism. It is strongly suggested that the user stick close to the following directions.
  
Line 34: Line 37:
 
== Server configuration ==
 
== Server configuration ==
  
The {{ic|/etc/samba/smb.conf}} file must be created before starting the service. Once that is set up, users may opt for using an advanced configuration interface like SWAT.
+
The Samba server is configured in {{ic|/etc/samba/smb.conf}}. Copy the default Samba configuration file to {{ic|/etc/samba/smb.conf}}:
 
+
As root, copy the default Samba configuration file to {{ic|/etc/samba/smb.conf}}:
+
 
  # cp /etc/samba/smb.conf.default /etc/samba/smb.conf
 
  # cp /etc/samba/smb.conf.default /etc/samba/smb.conf
  
Line 68: Line 69:
  
 
This marks the named objects for automatic export to the environment of subsequently executed commands:
 
This marks the named objects for automatic export to the environment of subsequently executed commands:
{{bc|<nowiki># export USERSHARES_DIR="/var/lib/samba/usershares"
+
 
# export USERSHARES_GROUP="sambashare"</nowiki>}}
+
# export USERSHARES_DIR="/var/lib/samba/usershares"
 +
# export USERSHARES_GROUP="sambashare"
 +
 
 
This creates the usershares directory in var/lib/samba:
 
This creates the usershares directory in var/lib/samba:
{{bc|<nowiki># mkdir -p ${USERSHARES_DIR}</nowiki>}}
+
 
 +
# mkdir -p ${USERSHARES_DIR}
 +
 
 
This makes the group sambashare:
 
This makes the group sambashare:
{{bc|<nowiki># groupadd ${USERSHARES_GROUP}</nowiki>}}
+
 
 +
# groupadd ${USERSHARES_GROUP}
 +
 
 
This changes the owner of the directory and group you just created to root:
 
This changes the owner of the directory and group you just created to root:
{{bc|<nowiki># chown root:${USERSHARES_GROUP} ${USERSHARES_DIR}</nowiki>}}
+
 
 +
# chown root:${USERSHARES_GROUP} ${USERSHARES_DIR}
 +
 
 
This changes the permissions of the usershares directory so that users in the group sambashare can read, write and execute files:
 
This changes the permissions of the usershares directory so that users in the group sambashare can read, write and execute files:
{{bc|<nowiki># chmod 1770 ${USERSHARES_DIR}</nowiki>}}
+
 
 +
# chmod 1770 ${USERSHARES_DIR}
 +
 
 
Set the following variables in {{ic|smb.conf}} configuration file:  
 
Set the following variables in {{ic|smb.conf}} configuration file:  
{{hc|/etc/samba/smb.conf|2=...
+
 
[global]
+
{{hc|/etc/samba/smb.conf|2=
  usershare path = /var/lib/samba/usershares
+
...
  usershare max shares = 100
+
[global]
  usershare allow guests = yes
+
  usershare path = /var/lib/samba/usershares
  usershare owner only = False
+
  usershare max shares = 100
...
+
  usershare allow guests = yes
 +
  usershare owner only = False
 +
  ...
 
}}
 
}}
 +
 
Save the file and then add your user to the group sambashares replacing "your_username" with the name of your  user:
 
Save the file and then add your user to the group sambashares replacing "your_username" with the name of your  user:
 +
 
  # usermod -a -G ${USERSHARES_GROUP} your_username
 
  # usermod -a -G ${USERSHARES_GROUP} your_username
  
 
Restart Samba.
 
Restart Samba.
 +
 +
# systemctl restart smbd nmbd
  
 
Log out and log back in. You should now be able to configure your samba share using GUI. For example, in [[Thunar]] you can right click on any directory and share it on the network.
 
Log out and log back in. You should now be able to configure your samba share using GUI. For example, in [[Thunar]] you can right click on any directory and share it on the network.
Line 105: Line 122:
  
 
To change a user's password, use {{ic|smbpasswd}}:
 
To change a user's password, use {{ic|smbpasswd}}:
 +
 
  # smbpasswd ''username''
 
  # smbpasswd ''username''
 
=== Web-based configuration (SWAT)===
 
 
'''SWAT''' (Samba Web Administration Tool) is a facility that is part of the Samba suite. Whether or not to use this tool remains a matter of personal preference. It does allow for quick configuration and has context-sensitive help for each {{ic|smb.conf}} parameter. SWAT also provides an interface for monitoring of current state of connection(s), and  allows network-wide MS Windows network password management.
 
 
{{Warning|Before using SWAT, be warned that SWAT will completely replace {{ic|/etc/samba/smb.conf}} with a fully optimized file that has been stripped of all comments, and only non-default settings will be written to the file.}}
 
 
To use SWAT, two [[systemd]] unit files come with the samba package that allow for socket activation. The SWAT service will be called automatically should a user call on the configured socket. In this case, a TCP connection on a specific port.
 
 
First, review the socket configuration:
 
{{hc|/usr/lib/systemd/system/swat.socket|<nowiki>
 
[Unit]
 
Description=SWAT Samba Web Admin Tool
 
 
[Socket]
 
ListenStream=127.0.0.1:901
 
Accept=true
 
 
[Install]
 
WantedBy=sockets.target
 
</nowiki>}}
 
 
{{Note|By default SWAT will only be available from the localhost, the system the SWAT service is installed on. If SWAT should be available for external connections, copy the unit to {{ic|<nowiki>/etc/systemd/system/swat.socket</nowiki>}}, and replace 127.0.0.1 with your system's LAN ip. i.e. {{ic|<nowiki>192.168.1.80:901</nowiki>}}.}}
 
 
When satisfied with the configuration, start the socket:
 
# systemctl start swat.socket
 
 
Or, should you want to enable SWAT during boot, enable:
 
# systemctl enable swat.socket
 
 
The web interface can now be accessed on port 901 by default:
 
{{ic|http://localhost:901/}}
 
 
{{Note|An all-encompasing [[Webmin]] tool is also available, and the SWAT module can be loaded there.}}
 
  
 
== Client configuration ==
 
== Client configuration ==
Line 149: Line 133:
 
=== Manual mounting ===
 
=== Manual mounting ===
  
Install {{Pkg|smbclient}} from the official repositories.
+
Install {{Pkg|smbclient}} from the official repositories. If you want a lighter approach and do not need the ability to list public shares, you need only install {{Pkg|cifs-utils}} to provide {{ic|/usr/bin/mount.cifs}}.
  
 
To list  public shares on a server:
 
To list  public shares on a server:
 +
 
  $ smbclient -L ''hostname'' -U%
 
  $ smbclient -L ''hostname'' -U%
  
 
Create a mount point for the share:
 
Create a mount point for the share:
 +
 
  # mkdir /mnt/''mountpoint''
 
  # mkdir /mnt/''mountpoint''
  
 
Mount the share using the {{ic|mount.cifs}} type. Not all the options listed below are needed or desirable (ie. {{ic|password}}).
 
Mount the share using the {{ic|mount.cifs}} type. Not all the options listed below are needed or desirable (ie. {{ic|password}}).
 +
 
{{bc|<nowiki>
 
{{bc|<nowiki>
 
# mount -t cifs //SERVER/SHARENAME /mnt/MOUNTPOINT -o user=USERNAME,password=PASSWORD,workgroup=WORKGROUP,ip=SERVERIP
 
# mount -t cifs //SERVER/SHARENAME /mnt/MOUNTPOINT -o user=USERNAME,password=PASSWORD,workgroup=WORKGROUP,ip=SERVERIP
 
</nowiki>}}
 
</nowiki>}}
{{ic|'''SERVER'''}}
+
 
 +
{{ic|SERVER}}
 
:The Windows system name.
 
:The Windows system name.
{{ic|'''SHARENAME'''}}
+
 
 +
{{ic|SHARENAME}}
 
:The shared directory.
 
:The shared directory.
{{ic|'''MOUNTPOINT'''}}
+
 
 +
{{ic|MOUNTPOINT}}
 
:The local directory where the share will be mounted.
 
:The local directory where the share will be mounted.
{{ic|'''-o <nowiki>[options]</nowiki>'''}}
 
:See {{ic|man mount.cifs}} for more information:
 
{{Note|Abstain from using a trailing '''/'''. {{ic|//SERVER/SHARENAME'''/'''}} will not work.}}
 
  
====Add Share to /etc/fstab====
+
{{ic|<nowiki>-o [options]</nowiki>}}
 +
:See {{ic|man mount.cifs}} for more information.
 +
 
 +
{{Note|
 +
* Abstain from using a trailing {{ic|/}}. {{ic|//SERVER/SHARENAME'''/'''}} will not work.
 +
* If your mount does not work stable, stutters or freezes, try to enable different SMB protocol version with {{ic|1=vers=}} option. For example, {{ic|1=vers=2.0}} for Windows Vista mount.
 +
}}
 +
 
 +
==== Add Share to /etc/fstab ====
  
 
The simplest way to add an fstab entry is something like this:
 
The simplest way to add an fstab entry is something like this:
 +
 
{{hc|/etc/fstab|<nowiki>
 
{{hc|/etc/fstab|<nowiki>
 
//SERVER/SHARENAME /mnt/MOUNTPOINT cifs username=USER,password=PASSWORD,workgroup=WORKGROUP,ip=SERVERIP 0 0
 
//SERVER/SHARENAME /mnt/MOUNTPOINT cifs username=USER,password=PASSWORD,workgroup=WORKGROUP,ip=SERVERIP 0 0
 
</nowiki>}}
 
</nowiki>}}
However, storing passwords in a world readable file is not recommended! A safer method would be to use a credentials file. As an example, create a file and {{ic|chmod 600 <filename>}} so only the owning user can read and write to it. It should contain the following information:
+
 
 +
However, storing passwords in a world readable file is not recommended! A safer method would be to use a credentials file. As an example, create a file and {{ic|chmod 600 ''filename''}} so only the owning user can read and write to it. It should contain the following information:
 +
 
 
{{hc|/path/to/credentials/sambacreds|<nowiki>
 
{{hc|/path/to/credentials/sambacreds|<nowiki>
 
username=USERNAME
 
username=USERNAME
 
password=PASSWORD
 
password=PASSWORD
 
</nowiki>}}
 
</nowiki>}}
 +
 
and the line in your fstab should look something like this:
 
and the line in your fstab should look something like this:
 +
 
{{hc|/etc/fstab|<nowiki>
 
{{hc|/etc/fstab|<nowiki>
//SERVER/SHARENAME /mnt/MOUNTPOINT cifs credentials=/path/to/credentials/sambacreds,workgroup=WORKGROUP,ip=SERVERIP 0 0</nowiki>}}
+
//SERVER/SHARENAME /mnt/MOUNTPOINT cifs credentials=/path/to/credentials/sambacreds,workgroup=WORKGROUP,ip=SERVERIP 0 0
 +
</nowiki>}}
 +
 
 
If using '''systemd''' (modern installations), one can utilize the '''comment=systemd.automount''' option, which speeds up service boot by a few seconds. Also, one can map current user and group to make life a bit easier, utilizing '''uid''' and '''gid''' options ('''warning:''' using the uid and gid options may cause input ouput errors in programs that try to fetch data from network drives):
 
If using '''systemd''' (modern installations), one can utilize the '''comment=systemd.automount''' option, which speeds up service boot by a few seconds. Also, one can map current user and group to make life a bit easier, utilizing '''uid''' and '''gid''' options ('''warning:''' using the uid and gid options may cause input ouput errors in programs that try to fetch data from network drives):
{{hc|/etc/fstab|<nowiki>//SERVER/SHARENAME /mnt/MOUNTPOINT cifs credentials=/path/to/smbcredentials,comment=systemd.automount,uid=USERNAME,gid=USERGROUP 0 0</nowiki>}}
+
 
{{note|space in sharename should be replaced by \040 (ASCII code for space in octal). For example, //SERVER/SHARE\ NAME on the command line should be //SERVER/SHARE\040NAME in fstab.}}
+
{{hc|/etc/fstab|<nowiki>
 +
//SERVER/SHARENAME /mnt/MOUNTPOINT cifs credentials=/path/to/smbcredentials,comment=systemd.automount,uid=USERNAME,gid=USERGROUP 0 0
 +
</nowiki>}}
 +
 
 +
{{Note|Space in sharename should be replaced by {{ic|\040}} (ASCII code for space in octal). For example, {{ic|//SERVER/SHARE\ NAME}} on the command line should be {{ic|//SERVER/SHARE\040NAME}} in ''fstab''.}}
  
 
==== User mounting ====
 
==== User mounting ====
Line 194: Line 200:
 
//SERVER/SHARENAME /mnt/MOUNTPOINT cifs users,credentials=/path/to/smbcredentials,workgroup=WORKGROUP,ip=SERVERIP 0 0
 
//SERVER/SHARENAME /mnt/MOUNTPOINT cifs users,credentials=/path/to/smbcredentials,workgroup=WORKGROUP,ip=SERVERIP 0 0
 
</nowiki>}}
 
</nowiki>}}
{{note|Note: The option is user'''s''' (plural). For other filesystem types handled by mount, this option is usually ''user''; sans the "'''s'''".}}
 
  
This will allow users to mount it as long as the mount point resides in a directory controllable by the user; i.e. the user's home. For users to be allowed to mount and unmount the Samba shares with mount points that they do not own, use [[Samba#smbnetfs|smbnetfs]], or grant privileges using [[sudo]].
+
{{Note|Note: The option is user'''s''' (plural). For other filesystem types handled by mount, this option is usually ''user''; sans the "'''s'''".}}
 +
 
 +
This will allow users to mount it as long as the mount point resides in a directory controllable by the user; i.e. the user's home. For users to be allowed to mount and unmount the Samba shares with mount points that they do not own, use [[#smbnetfs|smbnetfs]], or grant privileges using [[sudo]].
  
 
=== Automatic mounting ===
 
=== Automatic mounting ===
Line 207: Line 214:
  
 
Add the following line to {{ic|/etc/fuse.conf}}:
 
Add the following line to {{ic|/etc/fuse.conf}}:
{{bc|user_allow_other}}
+
 
 +
user_allow_other
 +
 
 
and load the {{ic|fuse}} [[kernel module]]:
 
and load the {{ic|fuse}} [[kernel module]]:
{{bc|# modprobe fuse}}
 
  
If a username and a password are required to access some of the shared folders, edit /etc/smbnetfs/.smb/smbnetfs.conf and uncomment the line starting with "auth":
+
# modprobe fuse
 +
 
 +
If a username and a password are required to access some of the shared folders, edit {{ic|/etc/smbnetfs/.smb/smbnetfs.conf}} and uncomment the line starting with "auth":
  
 
{{hc|/etc/smbnetfs/.smb/smbnetfs.conf|
 
{{hc|/etc/smbnetfs/.smb/smbnetfs.conf|
Line 248: Line 258:
 
==== Nautilus ====
 
==== Nautilus ====
  
In order to access samba shares through Nautilus, install the {{pkg|gvfs-smb}} package, available in the [[Official Repositories]].
+
In order to access samba shares through Nautilus, install the {{Pkg|gvfs-smb}} package, available in the [[Official Repositories]].
  
 
Press {{ic|Ctrl+l}} and enter {{ic|smb://servername/share}} in the location bar to access your share.
 
Press {{ic|Ctrl+l}} and enter {{ic|smb://servername/share}} in the location bar to access your share.
Line 256: Line 266:
 
==== Thunar and PCManFM ====
 
==== Thunar and PCManFM ====
  
For access using Thunar or pcmanfm, install {{pkg|gvfs-smb}}, available in the Official Repositories.  
+
For access using Thunar or PCManFM, install {{Pkg|gvfs-smb}}, available in the official repositories.  
  
 
Go to {{ic|smb://servername/share}}, to access your share.
 
Go to {{ic|smb://servername/share}}, to access your share.
Line 262: Line 272:
 
==== KDE ====
 
==== KDE ====
  
KDE, has the ability to browse Samba shares built in. Therefore do not need any additional packages. However, for a GUI in the KDE System Settings, install the {{pkg|kdenetwork-filesharing}} package from the [[Official Repositories]]
+
KDE, has the ability to browse Samba shares built in. Therefore do not need any additional packages. However, for a GUI in the KDE System Settings, install the {{Pkg|kdenetwork-filesharing}} package from the official repositories.
  
 
==== Other graphical environments ====
 
==== Other graphical environments ====
Line 268: Line 278:
 
There are a number of useful programs, but they may need to have packages created for them. This can be done with the Arch package build system. The good thing about these others is that they do not require a particular environment to be installed to support them, and so they bring along less baggage.
 
There are a number of useful programs, but they may need to have packages created for them. This can be done with the Arch package build system. The good thing about these others is that they do not require a particular environment to be installed to support them, and so they bring along less baggage.
  
* {{pkg|pyneighborhood}} is available in the [[Official Repositories]].
+
* {{Pkg|pyneighborhood}} is available in the official repositories.
 
* LinNeighborhood, RUmba, xffm-samba plugin for Xffm are not available in the official repositories or the [[AUR]]. As they are not officially (or even unofficially supported), they may be obsolete and may not work at all.
 
* LinNeighborhood, RUmba, xffm-samba plugin for Xffm are not available in the official repositories or the [[AUR]]. As they are not officially (or even unofficially supported), they may be obsolete and may not work at all.
  
 
== See also ==
 
== See also ==
  
* [[{{FULLPAGENAME}}/Tips and tricks|Tips and tricks]] - Dedicated page for alternate configurations and suggestions.
 
* [[{{FULLPAGENAME}}/Troubleshooting|Troubleshooting]] - Dedicated page for solving common (or not so common) issues.
 
 
* [http://www.samba.org/samba/docs/SambaIntro.html Samba: An Introduction]
 
* [http://www.samba.org/samba/docs/SambaIntro.html Samba: An Introduction]
 
* [http://www.samba.org/ Official Samba site]
 
* [http://www.samba.org/ Official Samba site]

Revision as of 17:50, 11 November 2013

Summary help replacing me
Installing, configuring and troubleshooting Samba
Related
Samba/Tips and tricks
Samba/Troubleshooting
NFS
Samba Domain Controller
Active Directory Integration

Samba is a re-implementation of the SMB/CIFS networking protocol, it facilitates file and printer sharing among Linux and Windows systems as an alternative to NFS. Some users say that Samba is easily configured and that operation is very straight-forward. However, many new users run into problems with its complexity and non-intuitive mechanism. It is strongly suggested that the user stick close to the following directions.

Required packages

Server

To share files with Samba, install samba, from the official repositories.

Client

Only smbclient is required to access files from a Samba/SMB/CIFS server. It is also available from the official repositories.

Server configuration

The Samba server is configured in /etc/samba/smb.conf. Copy the default Samba configuration file to /etc/samba/smb.conf:

# cp /etc/samba/smb.conf.default /etc/samba/smb.conf

Creating a share

Edit /etc/samba/smb.conf, scroll down to the Share Definitions section. The default configuration automatically creates a share for each user's home directory. It also creates a share for printers by default.

There are a number of commented sample configurations included. More information about available options for shared resources can be found in man smb.conf. Here is the on-line version.

On Windows side, be sure to change smb.conf to the Windows Workgroup. (Windows default: WORKGROUP)

Be sure that your machine is not named Localhost, since it will resolve on Windows to 127.0.0.1.

Starting services

Start smbd and nmbd to provide basic file sharing through SMB:

# systemctl start smbd
# systemctl start nmbd

To enable the services on bootup:

# systemctl enable smbd
# systemctl enable nmbd
Note: Or you can enable Samba socket so the daemon is started on the first incoming connection:
systemctl disable smbd.service
systemctl enable smbd.socket

Creating user share path

This marks the named objects for automatic export to the environment of subsequently executed commands:

# export USERSHARES_DIR="/var/lib/samba/usershares"
# export USERSHARES_GROUP="sambashare"

This creates the usershares directory in var/lib/samba:

# mkdir -p ${USERSHARES_DIR}

This makes the group sambashare:

# groupadd ${USERSHARES_GROUP}

This changes the owner of the directory and group you just created to root:

# chown root:${USERSHARES_GROUP} ${USERSHARES_DIR}

This changes the permissions of the usershares directory so that users in the group sambashare can read, write and execute files:

# chmod 1770 ${USERSHARES_DIR}

Set the following variables in smb.conf configuration file:

/etc/samba/smb.conf
...
[global]
  usershare path = /var/lib/samba/usershares
  usershare max shares = 100
  usershare allow guests = yes
  usershare owner only = False
  ...

Save the file and then add your user to the group sambashares replacing "your_username" with the name of your user:

# usermod -a -G ${USERSHARES_GROUP} your_username

Restart Samba.

# systemctl restart smbd nmbd

Log out and log back in. You should now be able to configure your samba share using GUI. For example, in Thunar you can right click on any directory and share it on the network. When the error You are not the owner of the folder appears, simply try to reboot the system.

Adding a user

To log into a Samba share, a samba user is needed. The user must already have a Linux user account with the same name on the server, otherwise running the next command will fail:

# pdbedit -a -u user
Note: As of version 3.4.0, smbpasswd is no longer used by default. Existing smbpasswd databases can be converted to the new format

Changing a password

To change a user's password, use smbpasswd:

# smbpasswd username

Client configuration

Shared resources from other computers on the LAN may be accessed and mounted locally by GUI or CLI methods. The graphical manner is limited since most lightweight Desktop Environments do not have a native way to facilitate accessing these shared resources.

There are two parts to share access. First is the underlying file system mechanism, and second is the interface which allows the user to select to mount shared resources. Some environments have the first part built into them.

Manual mounting

Install smbclient from the official repositories. If you want a lighter approach and do not need the ability to list public shares, you need only install cifs-utils to provide /usr/bin/mount.cifs.

To list public shares on a server:

$ smbclient -L hostname -U%

Create a mount point for the share:

# mkdir /mnt/mountpoint

Mount the share using the mount.cifs type. Not all the options listed below are needed or desirable (ie. password).

# mount -t cifs //SERVER/SHARENAME /mnt/MOUNTPOINT -o user=USERNAME,password=PASSWORD,workgroup=WORKGROUP,ip=SERVERIP

SERVER

The Windows system name.

SHARENAME

The shared directory.

MOUNTPOINT

The local directory where the share will be mounted.

-o [options]

See man mount.cifs for more information.
Note:
  • Abstain from using a trailing /. //SERVER/SHARENAME/ will not work.
  • If your mount does not work stable, stutters or freezes, try to enable different SMB protocol version with vers= option. For example, vers=2.0 for Windows Vista mount.

Add Share to /etc/fstab

The simplest way to add an fstab entry is something like this:

/etc/fstab
//SERVER/SHARENAME /mnt/MOUNTPOINT cifs username=USER,password=PASSWORD,workgroup=WORKGROUP,ip=SERVERIP 0 0

However, storing passwords in a world readable file is not recommended! A safer method would be to use a credentials file. As an example, create a file and chmod 600 filename so only the owning user can read and write to it. It should contain the following information:

/path/to/credentials/sambacreds
username=USERNAME
password=PASSWORD

and the line in your fstab should look something like this:

/etc/fstab
//SERVER/SHARENAME /mnt/MOUNTPOINT cifs credentials=/path/to/credentials/sambacreds,workgroup=WORKGROUP,ip=SERVERIP 0 0

If using systemd (modern installations), one can utilize the comment=systemd.automount option, which speeds up service boot by a few seconds. Also, one can map current user and group to make life a bit easier, utilizing uid and gid options (warning: using the uid and gid options may cause input ouput errors in programs that try to fetch data from network drives):

/etc/fstab
//SERVER/SHARENAME /mnt/MOUNTPOINT cifs credentials=/path/to/smbcredentials,comment=systemd.automount,uid=USERNAME,gid=USERGROUP 0 0
Note: Space in sharename should be replaced by \040 (ASCII code for space in octal). For example, //SERVER/SHARE\ NAME on the command line should be //SERVER/SHARE\040NAME in fstab.

User mounting

/etc/fstab
//SERVER/SHARENAME /mnt/MOUNTPOINT cifs users,credentials=/path/to/smbcredentials,workgroup=WORKGROUP,ip=SERVERIP 0 0
Note: Note: The option is users (plural). For other filesystem types handled by mount, this option is usually user; sans the "s".

This will allow users to mount it as long as the mount point resides in a directory controllable by the user; i.e. the user's home. For users to be allowed to mount and unmount the Samba shares with mount points that they do not own, use smbnetfs, or grant privileges using sudo.

Automatic mounting

There are several ways to easily browse shared resources:

smbnetfs

Install smbnetfs from the official repositories.

Add the following line to /etc/fuse.conf:

user_allow_other

and load the fuse kernel module:

# modprobe fuse

If a username and a password are required to access some of the shared folders, edit /etc/smbnetfs/.smb/smbnetfs.conf and uncomment the line starting with "auth":

/etc/smbnetfs/.smb/smbnetfs.conf
auth			"hostname" "username" "password"

Make sure to chmod 600 /etc/smbnetfs/.smb/smbnetfs.conf, and any include files for smbnetfs to work correctly.

To mount the network

smbnetfs mount_point

To browse the network

smbtree
Daemon

Start and enable the smbnetfs daemon.

If you want to start it at boot, enable it. It will be mounted on /mnt/smbnet/.

fusesmb

Note: Because smbclient 3.2.X is malfunctioning with fusesmb, revert to using older versions if necessary. See the relevant forum topic for details.
  1. Install fusesmbAUR, available in the AUR.
  2. Create a mount point: mkdir /mnt/fusesmb
  3. Load fuse kernel module.
  4. Mount the shares:
    fusesmb -o allow_other /mnt/fusesmb

autofs

See Autofs for information on the kernel-based automounter for Linux.

File manager configuration

Nautilus

In order to access samba shares through Nautilus, install the gvfs-smb package, available in the Official Repositories.

Press Ctrl+l and enter smb://servername/share in the location bar to access your share.

The mounted share is likely to be present at /run/user/your_UID/gvfs in the filesystem.

Thunar and PCManFM

For access using Thunar or PCManFM, install gvfs-smb, available in the official repositories.

Go to smb://servername/share, to access your share.

KDE

KDE, has the ability to browse Samba shares built in. Therefore do not need any additional packages. However, for a GUI in the KDE System Settings, install the kdenetwork-filesharing package from the official repositories.

Other graphical environments

There are a number of useful programs, but they may need to have packages created for them. This can be done with the Arch package build system. The good thing about these others is that they do not require a particular environment to be installed to support them, and so they bring along less baggage.

  • pyneighborhood is available in the official repositories.
  • LinNeighborhood, RUmba, xffm-samba plugin for Xffm are not available in the official repositories or the AUR. As they are not officially (or even unofficially supported), they may be obsolete and may not work at all.

See also