Comments on Fedora 18 Samba Standalone Server With tdbsam Backend
Fedora 18 Samba Standalone Server With tdbsam Backend This tutorial explains the installation of a Samba fileserver on Fedora 18 and how to configure it to share files over the SMB protocol as well as how to add users. Samba is configured as a standalone server, not as a domain controller. In the resulting setup, every user has his own home directory accessible via the SMB protocol and all users have a shared directory with read-/write access.
3 Comment(s)
Comments
Thanks for the tutorial. It got me up and running with my network scanner, which uses a shared folder to store scanned documents.
I was struggling with Samba for almost a day and couldn't get it working. I was just missing the "add the user to the Samba user database" part.
One thing I did have to do to get my set up working that's not in this tutorial is:
Create the system startup links for the NetBIOS name server daemon and start it:
systemctl enable nmb.service
systemctl start nmb.service
Please note that on a clean F18 install, there is no smbpasswd utility.
You should really use the pdbedit, which has the additional benefit of always working independent of the underlying password database.
Example, to add user anders
$ pdbedit -a -u anders
Whenever I'm training people who are new to Linux, I like to point out that among the very few reasons to reboot a linux server is to upgrade the kernel - and even then, they're working on that problem.
To that end, the steps to change selinux enforcement (as well as editing the selinux config, which affects behaviour upon reboot) are as follows:
setenforce Permissive
or
setenforce 0
depending on whether or not you want to see the errors (to see what would be denied) or just to turn it all off. Point is, no reboot required.
You can check the status of a running system via "getenforce"
I hope that helps.