FedoraThis forum is for the discussion of the Fedora Project.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I just installed Fedora 4 at home and am having one hard time getting Samba to work properly. All I want is to create the homes directories and I want one folder that is public.
Now, for the Home directories, I simply used the default configurations. Samba allows me to authenticate okay (I see my user's home directory) but it won't allow me to write to it.
In another instance, I can view the files in windows, but I cannot open the file. Winblows just tells me that the network location cannot be found.
I went throught the exact same problems. I spent alot of time trying to track down the cause of the newly eratic behavior of Samba in FC4. FC2 and 3beta worked perfectly for me, but after the switch, permissions went nuts.
After some serious reading, I stumbled into a change in the SELinux policies affecting Samba.
Disable SELinux, or downgrade your policy strength, and you should get control of Samba back.
The default firewall installed by fedora stops netbios from working. It blocks ports 137 and 138 which are the ports used by the SMB protocol. I think FC needs to look at this and provide a much better way of setting up a firewall.
I think fedora realized they'd made some mistakes and made some allowances for samba to run. You can disable the SELinux protection for smdb, nmdb, and winbind from within the SELinux setup. That works to correct the problem. More in depth is under discussion here: http://www.linuxquestions.org/questi...=samba+SELinux
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.