SAMBA SMB Server 3, on FC5, Hosting a shared folder to Windows client but can only read and not write

G'day All,

For the life of me! Samba has been a pain. Have been following three books on it and the web and still can't get it to work.
I have Fedora Core 5, with Samba 3.0.21b-2, with a folder I would like to share to some windows clients.
For starters for some reason SWAT can't change my passwords because it says it can't find the accounts in the smbpasswd file, the file is there. But over the CLI I can add the passwords to the accounts and works fine. Don't know why SWAT just does not want to play.
Secondly, after finally managing to get a folder hosted on the windows network, it turns out that I can only read from it. No matter what I do, change permission on the folders, on SAMBA, users, force masks, force users , every body read and write, no good. I cannot get the shared folders to write from the windows clients. I've tried using other peoples configuration files with no luck. been checking the conf file with testparm and reloading the service.

Does any one have a smb.conf file which has been tested and works. I just need to be able to share a folder to a windows network and have ready write access to it. And also the permissions on the linux folders.

Any assistance very much apreciated!!!

thank you all!!

Who is Participating?
ibu1Connect With a Mentor System AdministratorCommented:
Follow this example

comment = share
path = /Downloads
readonly = no
browsable = yes
writeable = yes
create mask = 0777
directory mask = 0777
force create mode = 0777
force directory mode =  0777

Check that the shared directory has the permission of 777.If it is not do this

# chmod -R  777 /Download

Best of luck

Arthur_MinoAuthor Commented:
G'day ibu1 and all,

Ok it took me all night but I found the cause of my mistake.

Your config file ibu1 is correct and it works.

But it turns out that because I had SWAT running and I was modifying the smb.conf file as well, this would cause a conflict between the two. There fore not just loading in my edited CLI smb.conf file but the SWAT file as well.

I noticed this when I was running the testparm smb.cnf, it would only show part of my settings. With a better look it all fell in to place.

I strongly suggest for people running SWAT to make sure you don't go back to the CLI to change the SMB file.

Thank you for getting back to me.


Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.