Sharing folders over the network using Samba in Ubuntu

24

May 8, 2011 by Milind Padalkar


Hi everyone!!!

This time I’ll demonstrate how to setup Folder Sharing over the network in Ubuntu with appropriate permissions for each user. This shall be applicable to other linux distributions as well. The shared content will be available on both Microsoft systems as well as on Linux systems. We will be using the Samba package for this purpose. We start with downloading Samba.

Open the terminal (shortcut : Alt+Ctrl+t) and install the samba package

sudo apt-get install samba smbfs system-config-samba

On prompting enter your password to start the download and install process.

Now create the users who you wish to use the shared folders. Say, I want a user shareuser1 to access the shared folder from anywhere on the network. In such a case I will have to create the user shareuser1 on the machine having the shared folders and then connect to the share from other machines on the network using the username shareuser1.

For this tutorial I will create 8 such users.

sudo useradd -m shareuser1
sudo useradd -m shareuser2
sudo useradd -m shareuser3
sudo useradd -m shareuser4
sudo useradd -m shareuser5
sudo useradd -m shareuser6
sudo useradd -m shareuser7
sudo useradd -m shareuser8

To check if the users are successfully created, check the /etc/passwd file

cat /etc/passwd

cat /etc/passwd

If the usernames are not mentioned here, then something went wrong. Read the man useradd page in the terminal and do the needful. If you get the output similar to the above then go ahead.

Let us assign the newly created users to various groups as follows.

shareuser1, shareuser2  in sharegroup1
shareuser1, shareuser2, shareuser3  in sharegroup2
shareuser4, shareuser5, shareuser6  in sharegroup3
shareuser4, shareuser7, shareuser8  in sharegroup4
shareuser2, shareuser5, shareuser6  in sharegroup5

First create the groups using sudo groupadd <groupname>.

sudo groupadd sharegroup1
sudo groupadd sharegroup2
sudo groupadd sharegroup3
sudo groupadd sharegroup4
sudo groupadd sharegroup5

Now assign users to these groups using the format sudo usermod -G <group list separated by comma(,)> <username>.

sudo usermod -G sharegroup1,sharegroup2 shareuser1
sudo usermod -G sharegroup1,sharegroup2,sharegroup5 shareuser2
sudo usermod -G sharegroup2 shareuser3
sudo usermod -G sharegroup3,sharegroup4 shareuser4
sudo usermod -G sharegroup3,sharegroup5 shareuser5
sudo usermod -G sharegroup3,sharegroup5 shareuser6
sudo usermod -G sharegroup4 shareuser7
sudo usermod -G sharegroup4 shareuser8

Check if the groups are properly assigned to each user using the format groups username. Here I show it for shareuser2.

groups shareuser2

Output :

groups shareuser2

To enable a user to use a share, an entry must be made in the local smbpasswd file. For each user we create a such an entry using sudo smbpasswd -a <username>.

sudo smbpasswd -a shareuser1
sudo smbpasswd -a shareuser2
sudo smbpasswd -a shareuser3
sudo smbpasswd -a shareuser4
sudo smbpasswd -a shareuser5
sudo smbpasswd -a shareuser6
sudo smbpasswd -a shareuser7
sudo smbpasswd -a shareuser8

Output:

sudo smbpasswd -a shareuser1

sudo smbpasswd -a shareuser1

Now that the users and groups are set up, we can move to configuring Samba. Make sure that the partitions consisting the folders to be shared are mounted with proper permissions. You may read the post on Auto-mounting NTFS partitions at boot time. Before configure the shares, I suggest to backup the original samba configuration file.

sudo cp /etc/samba/smb.conf /etc/samba/smb.conf.bkp

We are now ready to configure our shares.

Start the terminal and open the smb.conf file. This file consists the configuration for the shares.

sudo nano /etc/samba/smb.conf

Go to the end of this file (Shortcut : press and hold Ctrl+v till you reach the end of the file). Use the following skeleton to configure the shares.

[Share-name] # A name that you want to display for this share
<tab>path = # path to the folder to be shared
<tab>valid users = # list of valid users. ( ex. @administrators, @users, administrator ). Those starting with @ are groups.
<tab>writeable = # yes/no
<tab>browseable = # yes/no
<tab>read list = # list of users and groups who are allowed to read this share.
<tab>write list = # list of user and groups who are given permission to write to this share.
<tab>guest ok = # yes/no
 

You may refer SambaConf file as a complete guide for shares and available options. In my case I want permissions to various shares as follows.

/media/sda7/Videos to be readable by sharegroup1 and writable by shareuser1.

/media/sda7/Docs to be readable by sharegroup2, sharegroup3, sharegroup4, sharegroup5 and writable by sharegroup3 and shareuser1.

/media/sda6/Pics to be readable by sharegroup5, shareuser7 and writable by shareuser7.

/media/sda6/Desktop to be readable to all.

To achieve the this I add the following lines to the end of /etc/samba/smb.conf file.

[Videos]
    path = /media/sda7/Videos/
    valid users = @sharegroup1, shareuser1
    browseable = yes
    writeable = yes
    read list = @sharegroup1, shareuser1
    write list = shareuser1
#    guest ok =

[Docs]
    path = /media/sda7/Docs/
    valid users = @sharegroup2, @sharegroup3, @sharegroup4, @sharegroup5, shareuser1
    browseable = yes
    writeable = yes
    read list = @sharegroup2, @sharegroup3, @sharegroup4, @sharegroup5, shareuser1
    write list = shareuser1, @sharegroup3
#    guest ok =

[Pics]
    path = /media/sda6/Pics/
    valid users = @sharegroup5, shareuser7
    browseable = yes
    writeable = yes
    read list = @sharegroup5, shareuser7
    write list = shareuser7
#    guest ok =

[Desktop]
    path = /media/sda6/Desktop/
    browseable = yes
    writeable = no
    guest ok =yes

Here’s my attached smb.conf file. Now restart the samba service.

sudo service smbd restart

And you are done!!! You should be able to access your shares from your Windows as well as Linux machines, giving the correct username and password for the shares in mapping the network drive. ๐Ÿ™‚

Note : To remove a user from the local smbpasswd file enter the command

sudo smbpasswd -x shareuser1

To remove a user account from your system enter,

sudo userdel -r shareuser1

To remove a group, enter

sudo groupdel sharegroup1

๐Ÿ™‚ ๐Ÿ™‚ ๐Ÿ™‚

You may also have a look at a helpful suggestion by Emre.

Advertisements

24 thoughts on “Sharing folders over the network using Samba in Ubuntu

  1. […] Sharing folders over the network using Samba in Ubuntu (milindpadalkar.wordpress.com) […]

  2. tobylevel9 says:

    great post. thanks! worked just like you said.

  3. Bob Robertson says:

    Thanks for the summary. I’ve worked through the samba docs previously working out the correct steps. After trashing my OS I re-installed and your page saved me some serious time.

  4. You may want to remove the login permission from these share users, just edit the /etc/passwd file and change the end of the users line to /bin/false to do so.

  5. Ed says:

    Milind Padalkar,
    Very thanks for the post, it was very useful.
    Best regards,
    Ed.

  6. irshaad says:

    great article (Y)
    thanks milind

  7. Nama says:

    Sooperu…

  8. Ian says:

    Another thank you from me… I followed it on XUbuntu and it worked perfectly.

  9. Ryan Holmes says:

    Thanks very much-

    I setup my file share system with your help, however my only one issue is that from my windows clients all i get is ‘\\****\** is not accessible’ error

    Any suggestions?

    • Dear Ryan,

      Thanks for writing to me.
      I believe that both your machines are connected on the same network. Yet, you may recheck the connectivity. Are you able to ping the Ubuntu machine from you Windows client? Is the location \\****\** accessible from any other Ubuntu machine? If pinging is successful then I would like to inspect your smb.conf file.

      Regards,
      Milind

      • Ryan Holmes says:

        Heya – i can access some of the files now using their usernames/passwords. But no one can write to the folders for some reason. Here is my conf file to look at

        #
        # 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.
        # A well-established practice is to name the original file
        # “smb.conf.master” and create the “real” config file with
        # testparm -s smb.conf.master >smb.conf
        # This minimizes the size of the really used smb.conf file
        # which, according to the Samba Team, impacts performance
        # However, use this with caution if your smb.conf file contains nested
        # “include” statements. See Debian bug #483187 for a case
        # where using a master file is not a good idea.
        #

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

        [global]
        log file = /var/log/samba/log.%m
        passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* .
        obey pam restrictions = yes
        map to guest = bad user
        encrypt passwords = true
        passwd program = /usr/bin/passwd %u
        passdb backend = tdbsam
        dns proxy = no
        netbios name = File Server
        server string = File Server
        unix password sync = yes
        workgroup = OFFICE
        os level = 20
        auto services = global
        security = user
        syslog = 0
        usershare allow guests = yes
        panic action = /usr/share/samba/panic-action %d
        max log size = 1000
        pam password change = yes

        ## Browsing/Identification ###

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

        # server string is the equivalent of the NT Description field

        # 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.

        # What naming service and in what order should we use to resolve host names
        # to IP addresses
        ; name resolve order = lmhosts host wins bcast

        #### 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

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

        # 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.

        # Do something sensible when Samba crashes: mail the admin a backtrace

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

        # “security = user” is always a good idea. This will require a Unix account
        # in this server for every user accessing the server. See
        # /usr/share/doc/samba-doc/htmldocs/Samba3-HOWTO/ServerType.html
        # in the samba-doc package for details.
        # security = user

        # You may wish to use password encryption. See the section on
        # ‘encrypt passwords’ in the smb.conf(5) manpage before enabling.

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

        # 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.

        # For Unix password sync to work on a Debian GNU/Linux system, the following
        # parameters must be set (thanks to Ian Kahan < for
        # sending the correct chat script for the passwd program in Debian Sarge).

        # 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’.

        # This option controls how unsuccessful authentication attempts are mapped
        # to anonymous connections

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

        # Is this machine able to authenticate users. Both PDC and BDC
        # must have this setting enabled. If you are the BDC you must
        # change the ‘domain master’ setting to no
        #
        ; domain logons = yes
        #
        # The following setting only takes effect if ‘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” -d /var/lib/samba -s /bin/false %u

        # 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

        ########## Printing ##########

        # If you want to automatically load your printer list rather
        # than setting them up individually then you’ll need this
        # load printers = yes

        # lpr(ng) printing. You may wish to override the location of the
        # printcap file
        ; printing = bsd
        ; printcap name = /etc/printcap

        # CUPS printing. See also the cupsaddsmb(8) manpage in the
        # cupsys-client package.
        ; printing = cups
        ; printcap name = cups

        ############ 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

        # Most people will find that this option gives better performance.
        # See smb.conf(5) and /usr/share/doc/samba-doc/htmldocs/Samba3-HOWTO/speed.html
        # for details
        # You may want to add the following on a Linux system:
        # SO_RCVBUF=8192 SO_SNDBUF=8192
        # socket options = TCP_NODELAY

        # The following parameter is useful only if you have the linpopup package
        # installed. The samba maintainer and the linpopup maintainer are
        # working to ease installation and configuration of linpopup and samba.
        ; message command = /bin/sh -c ‘/usr/bin/linpopup “%f” “%m” %s; rm %s’ &

        # Domain Master specifies Samba to be the Domain Master Browser. If this
        # machine will be configured as a BDC (a secondary logon server), you
        # must set this to ‘no’; otherwise, the default behavior is recommended.
        # domain master = auto

        # 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

        # The following was the default behaviour in sarge,
        # but samba upstream reverted the default because it might induce
        # performance issues in large organizations.
        # See Debian bug #368251 for some of the consequences of *not*
        # having this setting and smb.conf(5) for details.
        ; winbind enum groups = yes
        ; winbind enum users = yes

        # 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

        #======================= Share Definitions =======================

        # Un-comment the following (and tweak the other settings below to suit)
        # to enable the default home directory shares. This will share each
        # user’s home director as \\server\username
        ;[homes]
        ; comment = Home Directories
        ; browseable = no

        # 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. Un-comment the following parameter
        # to make sure that only “username” can connect to \\server\username
        # The following parameter makes sure that only “username” can connect
        #
        # 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

        # A sample share for sharing your CD-ROM with others.
        ;[cdrom]
        ; comment = Samba server’s CD-ROM
        ; read only = yes
        ; locking = no
        ; path = /cdrom
        ; guest ok = yes

        # The next two parameters show how to auto-mount a CD-ROM when the
        # cdrom share is accesed. For this to work /etc/fstab must contain
        # an entry like this:
        #
        # /dev/scd0 /cdrom iso9660 defaults,noauto,ro,user 0 0
        #
        # The CD-ROM gets unmounted automatically after the connection to the
        #
        # If you don’t want to use auto-mounting/unmounting make sure the CD
        # is mounted on /cdrom
        #
        ; preexec = /bin/mount /cdrom
        ; postexec = /bin/umount /cdrom

        [Management]
        writeable = yes
        path = /opt/fileserver/management
        write list = @level4,@level5
        create mask = 0755
        comment = Administrative documents for Management
        valid users = @level4,@level5
        user = @level4,@level5

        [Support]
        delete readonly = yes
        valid users = @level4,@level3
        writeable = yes
        path = /opt/fileserver/support
        write list = @level4,@level3
        # guest ok = no

        [User Documents]
        read list = @level1
        valid users = @level5,@level4,@level3,@level2,@level1
        writeable = yes
        path = /opt/fileserver/documents
        write list = @level5,@level4,@level3,@level2
        # guest ok =

        [Pending Process]
        writeable = yes
        valid users = @level5,@level4,@level3,@level2,@level1
        public = yes
        user = @level5,@level4,@level3,@level2,@level1
        path = /opt/fileserver/pending
        write list = @level5,@level4,@level3,@level2,@level1

        The pending proccess folder should be a open public/guest share where everyone can write, but only level2,3,4 and level 5 can delete..

        How can i achieve this?

      • Hi Ryan,

        Thanks for your smb.conf file.

        I would suggest avoiding spaces in share names. I believe there are some issues with spaces in share names.

        Next, I may check the permission for /opt/fileserver/. Please notice that for my shares i.e. /media/sda6/ I had used umask=000 while auto-mounting at boot time. So I had no problems while writing.

        You may use the following in your smb.conf file.

        [Management]
        	comment = Administrative documents for Management
        	path = /opt/fileserver/management
        	valid users = @level4, @level5
        	browseable = yes
        	writeable = yes
        	read list = @level4, @level5
        	write list = @level4, @level5
        	create mask = 0755
        [Support]
        	path = /opt/fileserver/support
        	valid users = @level4, @level3
        	browseable = yes
        	writeable = yes
        	read list = @level4,@level3
        	write list = @level4,@level3
        	delete readonly = yes
        
        [User-Documents]
        	path = /opt/fileserver/documents
        	valid users = @level5, @level4, @level3, @level2, @level1
        	browseable = yes
        	writeable = yes
        	read list = @level5, @level4, @level3, @level2, @level1
        	write list = @level5, @level4, @level3, @level2
        
        [Pending-Process]
        	path = /opt/fileserver/pending
        	browseable = yes
        	writeable = yes
        	guest ok = yes
        	create mask = 1777
        

        Please beware of the tabs and space. I did have issues with tabs before I created this post.

        Presently I do not have an environment to test the above. I will try to test it myself and let you know if I am successful.

  10. Ryan Holmes says:

    Heya- OK, I have changed the .conf file as requested.

    here is permissions for \fileserver:

    drwxrwxr-x 7 root users 4096 Oct 21 00:10 fileserver

    her is permissions for files within \fileserver\;

    drwxrwxrwx 2 root root 4096 Oct 20 23:29 documents
    drwxrwx— 2 root root 4096 Oct 20 23:34 management
    drwxrwxrwx 2 root root 4096 Oct 21 00:28 pending
    drwxrwxrwx 2 root root 4096 Oct 20 23:04 support

    Also- the folders: documents, pending and support are highlighted green

    after applying changes, i can write to the folders pending and documents, but cannot open support and management: it gives me access denied errors when i put in usernames.

    • Hi Ryan,

      I am glad to know that you are able to write into some folders. Since pending and documents are working fine, a quick solution to work with support and management would be to use settings similar to pending and documents. Thus, you may remove the lines “delete readonly = yes” and “create mask = 0755” from settings for support and management folders, respectively.

      However, I still have doubt about the management folder since you have drwxrwx— and all are owned by root. You may therefore change the permissions of management folder using

       sudo chmod 777 /opt/fileserver/management 

      Let me know if this works.

      Regards,
      Milind

      • Ryan Holmes says:

        After applying the above changes i’m still unable to login from a windows machine. I get to the login prompt, i enter username and password, and then it gives me errors, and wont open the folder.

        I think the problem has something to do with authentication??
        Any ideas?

        (PS thanks for all your help!!)

      • Hi Ryan!

        Thanks for appreciating. ๐Ÿ™‚

        I believe it is the an issue with permissions of the /opt/filerserver folder. In what way are you connecting to the server? Is it by “map network drive” with your server’s username and password, or is it by some other method?

        PS: If you are facing this problem, even I may face it some day. It only means that something lacks in my understanding of the samba system, and I need to update it before I face a similar situation.

        Regards,
        Milind

  11. This is my first time pay a visit at here and i am truly
    impressed to read all at one place.

  12. Danuta says:

    I got this website from my buddy who told me regarding this website
    and now this time I am visiting this web site and reading very
    informative articles or reviews at this place.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

Milind Padalkar

Milind Padalkar

Blog Stats

  • 55,177 hits

Top rated

Enter your email address to follow this blog and receive notifications of new posts by email.

Join 120 other followers

Add This

Facebook Twitter More...

Flag Counter

free counters

%d bloggers like this: