SAMBA Shares read but no write

**MyD0j0** · November 26th, 2012

Hi all and TIA for the assistance!

I have an Ubuntu 11.04 server running samba (cifs) with several shares. After following this Ubuntu community wiki MountWindowsSharesPermanently as well as several forum threads dealing with permissions on samba shares, there is something not going correctly. That is, I am doing something wrong.

On shares that are owned by "nobody:nogroup" and supposedly rw, I can mount the shares as read in a laptop running Ubuntu 11.04, but immediately following the creation of any folder or file, that folder or file is locked and I can no longer make any changes to the folder or file. I also have shares that are owned by specific users that I can't mount at all.

These are the users/groups and directories on the remote server:

Code:


root@SambaServer:~# ls -al /srv/SambaShares/NetUsers
total 24
drwxrwxrwx 6 root      users     4096 2012-01-18 08:20 .
drwxr-xr-x 4 root      root      4096 2012-01-18 08:21 ..
drwxrwxrwx 2 user3   user3   4096 2012-01-13 22:58 User3
drwxrwxrwx 2 user2 user2 4096 2012-01-13 22:58 User2
drwxrwxrwx 5 user1      user1      4096 2012-04-27 12:56 User1
drwxrwxrwx 3 user4   user4   4096 2012-03-16 16:13 User4

root@SambaServer:~# ls -al /srv/SambaShares/MultiMedia
total 64
drwxrwxrwx    7 root   nogroup  4096 2012-11-26 12:04 .
drwxr-xr-x    4 root   root     4096 2012-01-18 08:21 ..
drwxrwxrwx   10 nobody nogroup  4096 2012-11-26 10:12 Movies
drwxrwxrwx 1337 nobody nogroup 40960 2012-11-16 20:36 Music
drwxrwxrwx    7 nobody nogroup  4096 2012-11-17 05:29 Pictures
drwxrwxrwx    2 nobody nogroup  4096 2012-04-27 14:19 Playlists
drwxrwxrwx    4 nobody nogroup  4096 2012-04-27 14:51 Podcasts

root@SambaServer:~# cat /etc/passwd | grep 100
libuuid:x:100:101::/var/lib/libuuid:/bin/sh
user1:x:1000:1000:,,,:/home/user1:/bin/bash
user4:x:1001:1001:,,,:/home/user4:/bin/bash
user3:x:1002:1002:,,,:/home/user3:/bin/bash
user2:x:1003:1003:,,,:/home/user2:/bin/bash

root@SambaServer:~# cat /etc/group | grep 100
users:x:100:user2,user1,user4,user3
user1:x:1000:
user4:x:1001:
user3:x:1002:
user2:x:1003:

In /usr/bin I have a file that is invoked on my Ubuntu laptop at login that runs these mount commands:

Code:


user1@MyD0j0:~$ cat /usr/bin/mountsambashares
#!/bin/bash
sleep 30
mount -t cifs //SambaServer/MovieD0j0  /mnt/MovieD0j0 -o guest,rw,iocharset=utf8,file_mode=0777,dir_mode=0777
mount -t cifs //SambaServer/PictureD0j0  /mnt/PictureD0j0 -o guest,rw,iocharset=utf8,file_mode=0777,dir_mode=0777
mount -t cifs //SambaServer/MusicD0j0  /mnt/MusicD0j0 -o guest,rw,iocharset=utf8,file_mode=0777,dir_mode=0777
mount -t cifs //SambaServer/User1 /mnt/User1 -o user=user1,password=user1passwd,rw,iocharset=utf8,file_mode=0777,dir_mode=0777

A few things to note:

I use soft links from /home/user1 to the /mnt/<directory> locations.
user1 has the same user id and group id on both machines, being the first user added to either.
These shares will also be used with 2 Windows machines and a Mac.

Once again, thanks for the assistance and happy computing!

MyD0j0

**dannyboy79** · November 26th, 2012

we need to see the smb.conf file from the server that is doing the sharing.

**MyD0j0** · November 27th, 2012

Originally Posted by dannyboy79

we need to see the smb.conf file from the server that is doing the sharing.

DOH! I had that and meant to include it...

Code:

#
# 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
	wins support = true
	dns proxy = no
	server string = %h server (Samba, Ubuntu)
	unix password sync = yes
	workgroup = workgroup
	os level = 20
	syslog = 0
	security = share
	panic action = /usr/share/samba/panic-action %d
	usershare allow guests = yes
	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.

# 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 <<kahan@informatik.tu-muenchen.de> 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

[MusicD0j0]
	comment = SambaShares Music Library
	path = /srv/SambaShares/MultiMedia/Music
	guest ok = yes
        public = yes
	browsable = yes
	writable = yes
	create mask = 0777
	directory mask = 0777
	force user = nobody
	force group = nogroup

[PictureD0j0]
	comment = SambaShares Picture Library
	path = /srv/SambaShares/MultiMedia/Pictures
	guest ok = yes
	public = yes
	browsable = yes
	writable = yes
	create mask = 0777
	directory mask = 0777
	force user = nobody
	force group = nogroup

[MovieD0j0]
	comment = SambaShares Movie & Video Library
	path = /srv/SambaShares/MultiMedia/Movies
	guest ok = yes
	public = yes
	browsable = yes
	writable = yes
	create mask = 0777
	directory mask = 777
	force user = nobody
	force group = nogroup

[user1]
	comment = SambaShares Personal Share for user1
	path = /srv/SambaShares/NetUsers/user1
	browsable = yes
	guest ok = no
	read only = no
	create mask = 0755

[user2]
	comment = SambaShares Personal Share for user2
	path = /srv/SambaShares/NetUsers/user2
	browsable = yes
	guest ok = no
	read only = no
	create mask = 0755

[user4]
	comment = SambaShares Personal Share for user4
	path = /srv/SambaShares/NetUsers/user4
	browsable = yes
	guest ok = no
	read only = no
	create mask = 0755

[user3]
	comment = SambaShares Personal Share for user3
	path = /srv/SambaShares/NetUsers/user3
	browsable = yes
	guest ok = no
	read only = no
	create mask = 0755

**MyD0j0** · November 27th, 2012

Just an update...but for grins, I used ES File Manager from both my Nexus 7 tablet and my motorola android phone. Both were able to create a new folder and a new file in that folder. The file and folder permissions were maintained so that I could then go to another machine and update both without any problems.

Also, if I use nautilus to "browse network" then I can also mount the folders as read/write.

What am I doing wrong with the mount commands that is preventing me from being able to mount the folders as read/write?!?!

Thanks!

**dannyboy79** · November 27th, 2012

try removing the guest option from your mount command. You are using "share" level security which is the lightest form of security for SAMBA.

ALso, I believe the ; is not commenting out lines. So the line
# This might need tweaking when using external authentication schemes
; valid users = %S

is specifying valid users being only %S. Is that what you want?

**MyD0j0** · December 11th, 2012

bump

Any more ideas...anyone?

**dannyboy79** · December 11th, 2012

once you create a file or folder within the mounted directories, you say you can't edit it or write a file to the folder, what are the permissions of that folder or file? Is that user part of the nogroup group?

Also, you're mounting them with guest, so why are you also forcing user nobody and nogroup within the share options?

Also, you have map to guest = bad user which makes things much harder to debug