> That would be SELinux. Run System Settings | Security Level and change > what SELinux allows Samba to do. Failing that you can use getsebool and > setsebool to manipulate the policy booleans in the same manner. I tried several combinations of SELinux options, and eventually just disabled SELinux protection for all the Samba-related daemons. That fixed it. Should this be considered a bug/something to be fixed? It seems to me that the average user just wanting to share a few files won't know how to/want to mess with the security settings. What do you think? --Dane -- fedora-test-list mailing list fedora-test-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-test-list