Windows says Samba share is write protected

[aaronmac3232]

I'm tired of the slow performance of Windows file sharing, so I'm playing around with samba in FC5 as a possible replacement for my home file server. I have created a share in FC5 using the Samba configuration tool, and I am able to access it from my Windows machine. The problem is that the share is read-only even though I checked the "writeable" box in the samba config utility. When I try to write a file to the share from a Windows machine I get a message that says "Access is denied. Make sure the disk is not full or write-protected...." I can copy files from the share just fine.

The directory that I've shared is /share/test, and here are the local permissions assigned to the folder:

[root@localhost share]# pwd
/share
[root@localhost share]# ls -l
total 8
drwxrwxrwx 2 aaron aaron 4096 May 9 15:01 test
[root@localhost share]#

Through the samba config utility I have created a user named aaron, and assigned that user to the share. When I connect to the share from Windows I use the username and password I created for samba, but access is read-only.

Any thoughts?

[frharris27]

Take a look at the permissions on the linux file system, not just the samba share conf. Make sure they're writable for all the users who will be accessing it.

[webdude]

I had the same problem. There was a setting on the config in the program for samba that I have to change from User to Share. That fixed the problem.

Cheers.

[aaronmac3232]

I used chmod 777 on the directory that I am sharing, and I used chown to set the owner to aaron before I posted my problem, and it didn't make any difference. Is there a samba user that I need to assign to the directory?

[aaronmac3232]

Originally Posted by webdude

I had the same problem. There was a setting on the config in the program for samba that I have to change from User to Share. That fixed the problem.

Cheers.

I tried using share authentication instead of user authentication, but Windows still says the share is write-protected. Maybe its because I'm using active directory. The machine that I am using to connect to the samba share is my Windows Server 2003 box. I will try connecting from a Windows XP machine and report back.

[aaronmac3232]

Well, it has nothing to do with active directory, as I tried using a stand alone Windows XP machine to connect to the samba share and it was still read only. I also checked the smb.conf file and confirmed that the share is set to writeable. It must have something to do with the file permissions assigned to the directory itself, but I used chmod 777 command to give full access to all users so I'm not sure what else to try.

[frharris27]

Can you post the part of your smb.conf file that shows the share? I seem to remember that there's this issue of "writeable" versus "writable". It's very easy to mess up the spelling and I wouldn't be surprised if the config tools get it wrong.

Also, do your logs say anything abou it? I think there's a /var/log/smb directory or something like that.

[frharris27]

Oh yeah. Have you looked at Selinux regarding this? You may want to turn it off for samba.

[aaronmac3232]

SELinux was the culprit. I changed it from Enforcing to Disabled and now I can write to the share from Windows. Thanks for your help!