Arch Linux

HoZ

Member

Registered: 2008-03-30

Posts: 45

[Solved] No write access to samba share

I have an external usb drive shared via samba from my primary computer.  I am accessing the share from another Arch box.  I use fstab to mount the share, and I can browse the contents without issue.  However, I do not have write access to the share (access denied).  I would just use NFS, but I also have a windows laptop that needs accces to the share as well. 

Here is my fstab entry:

//10.50.100.130/share /mnt/share cifs users,noatime,rw,username=******,password=********,workgroup=Mygroup,ip=10.50.100.130, 0 0

Here is my smb.conf:

# Samba config file created using SWAT
# from UNKNOWN (127.0.0.1)
# Date: 2012/02/20 16:27:59

[global]
	workgroup = Mygroup
	server string = Samba Server
	log file = /var/log/samba/%m.log
	max log size = 50
	dns proxy = No
	hosts allow = 192.168.1. 10.50.100. 127.
	idmap config * : backend = tdb

[printers]
	comment = All Printers
	path = /var/spool/samba
	printable = Yes
	print ok = Yes
	browseable = No

[share]
	comment = Shared Folder
	path = /media/c9641ee4-363e-4cc5-960d-e608cf34ddad/share
	valid users =*******
	write list = *******
	writable = yes
	read only = No

Any idea what the issue might be?

Last edited by HoZ (2012-02-22 14:39:20)

brenix

Member

From: California

Registered: 2008-03-05

Posts: 185

Re: [Solved] No write access to samba share

Hmm, I'm not a samba expert, but here is a snippet of my smb.conf which allows an authenticated user to have write access..

Maybe this will help point you in the right direction..

[global]
workgroup = WORKGROUP
server string = Samba Server
netbios name = ******
security = user
username map = /etc/samba/smbusers

[external]
comment = External Drive
path = /mnt/external/
available = yes
browsable = yes
public = yes
writable = yes

HoZ

Member

Registered: 2008-03-30

Posts: 45

Re: [Solved] No write access to samba share

Turned out to be a permission error with the directory on the share.  I was sure I had already checked this, but evidently I missed it.