Difference between revisions of "Samba"
(→Accessing a Samba share from the shell: merge from Windows Network Share) |
m (→Allowing users to mount: fix ln to smbnetfs) |
||
Line 170: | Line 170: | ||
{{Note|The option is {{codeline|user'''s'''}} (plural). For other filesystem types handled by mount, this option is usually ''user''; sans the "'''s'''".}} | {{Note|The option is {{codeline|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 aslong 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]]. | + | This will allow users to mount it aslong 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]]. |
== Tips and tricks == | == Tips and tricks == |
Revision as of 15:24, 1 January 2010
Template:I18n links start Template:I18n entry Template:I18n entry Template:I18n entry Template:I18n entry Template:I18n entry Template:I18n entry Template:I18n entry Template:I18n entry Template:I18n entry Template:I18n entry Template:I18n entry Template:I18n links end
Samba is a re-implementation of the SMB/CIFS networking protocol, it facilitates file and printer sharing between Linux and Windows systems or Linux-to-Linux systems as an alternative to Nfs. Samba is easily configured and operation is very straight-forward. See: Windows Network Share for more information about accessing Windows shares.
Contents
Installation
To install the Samba server, install the Template:Package Official package:
# pacman -S samba
A daemon is installed with the package and it must be started for Samba to begin working. Samba typically uses FAM to monitor the file-system for changes, yet Gamin has almost completely replaced FAM as of recent, mainly because the latter is poorly maintained and generally an inferior, unpopular choice.
To install Gamin:
# pacman -S gamin
If using FAM, start the Template:Codeline daemon before Template:Codeline. Gamin does not need a daemon since it automatically starts when needed.
Without rebooting, FAM and Samba can be started with the commands:
# /etc/rc.d/fam start # /etc/rc.d/samba start
Add Template:Codeline and Template:Codeline to the DAEMONS line in Template:Filename to automatically start the daemons at boot.
Note: Before Starting samba the file /etc/samba/smb.conf must be created, see Configuration Below.
Configuration
smb.conf
As root, copy the default Samba configuration file to Template:Filename:
# cp /etc/samba/smb.conf.default /etc/samba/smb.conf
Open Template:Filename and edit it to suit your needs. The default file creates a share for each user's home directory. It also creates a share for printers.
SWAT: Samba Web Administration Tool
SWAT is a facility that is part of the Samba suite. The main executable is called swat and is invoked by the internetworking super daemon, inetd.
There are many and varied opinions regarding the usefulness of SWAT. No matter how hard one tries to produce the perfect configuration tool, it remains an object of personal taste. However, SWAT is a very useful tool that allows Web-based configuration of Samba. It has a wizard that may help to get Samba configured quickly, it has context-sensitive help on each Template:Filename parameter, it provides for monitoring of current state of connection information, and it allows network-wide MS Windows network password management.
To use SWAT, first install xinetd:
# pacman -Sy xinetd
Edit Template:Filename using your favorite text editor. To enable SWAT, change the Template:Codeline line to Template:Codeline.
Additionally, edit Template:Filename if remote administration is needed.
The web interface can be accessed on port 901 by default,
http://localhost:901/
Adding users
To log into a Samba share you'll need to add a user:
# smbpasswd -a <user>
The user must already have a account on the server. If the user does not exist you will receive the error:
Failed to modify password entry for user "<user>"
You can add a new user to the Linux host with adduser. This article does not cover adding users to Windows systems.
KDE and Gnome have the ability to browse Samba shares. You therefore do not need any additional packages if using either of these DEs. If however you plan to use the share solely from a shell, you will need an additional package.
From a Nautilus/Dolphin/Konqueror window, hit Template:Keypress+Template:Keypress or go to the "Go" menu and select "Location..." -- both actions will allow you to type in the "Go to:" blank. Enter Template:Codeline and press enter.
For a GUI in the KDE System Settings you have to install the kdenetwork-filesharing package from [extra].
There are several alternatives for easy share browsing.
smbnetfs
1. Install Template:Package Official:
# pacman -S smbnetfs
2. Add the following line to Template:Filename:
user_allow_other
3. Load the Template:Codeline kernel module:
# modprobe fuse
4. Start the Template:Codeline daemon:
# /etc/rc.d/smbnetfs start
All shares in the network are now automatically mounted under Template:Filename.
Add the following to Template:Filename to access the shares at boot:
MODULES=(... fuse ...) DAEMONS=(... smbnetfs ...)
fusesmb
1. Install the Template:Package AUR package from the AUR using yaourt or other AUR Helpers:
$ yaourt -S fusesmb
2. Create a mount point:
# mkdir /mnt/fusesmb
3. Load Template:Codeline module:
# modprobe fuse
4. Mount the shares:
# fusesmb -o allow_other /mnt/fusesmb
For mounting shares at boot, add the command above to Template:Filename and add Template:Codeline module to Template:Filename:
MODULES=(... fuse ...)
Autofs
Autofs is a kernel-based automounter for Linux. See: Autofs for details.
1. Use smbclient to browse shares from the shell. To list any public shares on a server:
$ smbclient -L <hostname> -U%
2. Create the mount point for the share:
# mkdir /mnt/MOUNTPOINT
3. Mount the share using Template:Codeline. Keep in mind that not all options may be needed nor desirable, such as Template:Codeline:
# mount -t cifs //SERVER/SHARENAME MOUNTPOINT -o user=USERNAME,password=PASSWORD,workgroup=WORKGROUP,ip=SERVERIP
- Template:Codeline
- The Windows system's name
- Template:Codeline
- The shared directory
- Template:Codeline
- The local directory where the share will be mounted to
- Template:Codeline
- Specifies options for Template:Codeline
- Template:Codeline
- Username used to mount the share
- Template:Codeline
- The shared directory's password
- Template:Codeline
- Used to specify the workgroup
- Template:Codeline
- The IP address of the server -- if the system is unable to find the Windows computer by name (DNS, WINS, hosts entry, etc.)
4. To unmount the share, use:
# umount /mnt/MOUNTPOINT
Add the following to Template:Filename for easy mounting:
//SERVER/SHARENAME /mnt/MOUNTPOINT cifs noauto,noatime,username=USER,password=PASSWORD,workgroup=WORKGROUP 0 0
The Template:Codeline option disables mounting it automatically at boot and Template:Codeline increases performance by skipping inode access times.
After adding the previous line, the syntax to mount files becomes simpler:
# mount /mnt/MOUNTPOINT
If adding a Samba share to Template:Filename, the Template:Codeline daemon should also be added to Template:Filename, somewhere after the network daemon. The Template:Codeline daemon will mount network partitions at boot and, more importantly, unmount network partitions at shutdown. Even if using the Template:Codeline option in Template:Filename, the Template:Codeline daemon should be used. Without it any network share that is mounted when shutting down will cause the Template:Codeline daemon to wait for the connection to time out, considerably extending poweroff time.
Allowing users to mount
Before enabling access to the mount commands, Template:Filename needs to be modified. Add the Template:Codeline options to the entry in Template:Filename:
//SERVER/SHARENAME /path/to/SHAREMOUNT cifs users,noauto,noatime,username=USER,password=PASSWORD,workgroup=WORKGROUP 0 0
This will allow users to mount it aslong 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.
Tips and tricks
Edit Template:Filename and change the following line:
security = user
to
security = share
If you want to restrict the shares data to a specific interface replace:
; interfaces = 192.168.12.2/24 192.168.13.2/24
with:
interfaces = lo eth0 bind interfaces only = true
(changing eth0 to the local network you want share with.)
If you want to edit the account that access the shares, edit the following line:
; guest account = nobody
The last step is to create share directory (for write access make writable = yes):
[Public Share] path = /path/to/public/share available = yes browsable = yes public = yes writable = no
Sample configuration file
The configuration that worked for one user:
[global] workgroup = WORKGROUP server string = Samba Server netbios name = PC_NAME security = share ; the line below is important! If you have permission issues make sure the user here is the same as the user of the folder you want to share guest account = mark username map = /etc/samba/smbusers name resolve order = hosts wins bcast wins support = no
[public] comment = Public Share path = /path/to/public/share available = yes browsable = yes public = yes writable = no
If nothing is known about other systems on the local network, and automated tools such as smbnetfs are not available, the following methods allow one to manually probe for Samba shares. See also: Windows Network Share.
1. First, install Template:Package Official and Template:Package Official using pacman:
# pacman -S nmap smbclient
2. Template:Codeline checks which ports are open:
# nmap -sT 192.168.1.*
In this case, a scan on the 192.168.1.* IP address range has been performed, resulting in: Template:Command
The first result is another system; the second happens to be the client from where this scan was performed.
3. Now that systems with port 139 open are revealed, use Template:Codeline to check for NetBIOS names: Template:Command
Regardless of the output, look for <20>, which shows the host with open services.
4. Use Template:Codeline to list which services are shared on PUTER. If prompted for a password, pressing enter should still display the list: Template:Command
This shows which folders are shared and can be mounted locally. See: #Accessing Samba shares
Troubleshooting
If you are having trouble accessing a password protected share from Windows, try adding this to Template:Filename:[1]
[global] # lanman fix client lanman auth = yes client ntlmv2 auth = no
Getting a dialog box up takes a long time
I had a problem that it took ~30 seconds to get a password dialog box up when trying to connect from both Windows XP/Windows 7. Analyzing the error.log on the server I saw:
[2009/11/11 06:20:12, 0] printing/print_cups.c:cups_connect(103) Unable to connect to CUPS server localhost:631 - Interrupted system call
I don't have any printer connected to this server, so I added this to the global section:
load printers = no printing = bsd disable spoolss = yes printcap name = /dev/null
Not sure if all of them are necessary, but at least it works now.
Changes in Samba version 3.4.0
Major enhancements in Samba 3.4.0 include:
The default passdb backend has been changed to 'tdbsam'! That breaks existing setups using the 'smbpasswd' backend without explicit declaration!
If you would like to stick to the 'smbpasswd' backend try changing this in Template:Filename:
passdb backend = smbpasswd
or convert your smbpasswd entries using:
sudo pdbedit -i smbpasswd -e tdbsam
Error: Value too large for defined data type
With some applications you could get this error whith every attempt to open a file mounted in smbfs/cifs:
Value too large for defined data type
The solution[2] is to add this options to your smbfs/cifs mount options (in /etc/fstab for example):
,nounix,noserverino
It works on Arch Linux up-to-date (2009-12-02)