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.
This question could have probably been asked on the networking forum but I am asking it here because I believe it is an FC5 problem. I am networking three computers at home, one Ubuntu box, a Winxp laptop, and the FC5 box. When I set the network up, I have enabled NFS and Samba shares in SELinux. My router assigns IP addresses. The printer is connected to the FC5 box. I can print from the Ubuntu box (though I have to change the IP address each time I boot.)
My problem is this: I can connect to each of the other two computers from the FC5 box, but neither of them will connect to the FC5 box. On both I get errors saying I do not have permission. I have changed SElinux to allow NFS and Samba shares, and I have tried with the firewall on and off. The FC5 shows up on the network on the laptop in Network places, but I cannot open it because of permissions. The printer does not even show up on the laptop.
Does anyone have any ideas? Any help greatly appreciated.
I'm a beginner but am running FC 4 on one machine and FC5 on another. An article that made all of the difference for me was at: http://www.reallylinux.com/docs/sambaserver.shtml. I just followed it step-by-step and I had samba running perfectly and this when they had the firewall conflict.
One difference that I noticed with FC5 is that when you go under the "Security and Firewall" option, unlike with FC4, now you don't make the NIC a trusted device but rather you have to check SAMBA as a trusted device.
Thank you for that. I was beginning to think I was not going to get a hit on this one. I have bookmarked the site you mention and will try that. This one has really had me stumped because I do not have this problem in either FC4 or Slackware. I did find that, as you also mentioned, eth0 is not a choice for trusted devices in FC5 and I have already tried ticking the Samba box. I disabled SElinux and the firewall (just long enough for testing to see if that was the problem) with no result.
Like everything else in Linux, I will eventually figure this one out, too.
Be sure to read the FAQ on the Fedora site. Also check out;
$ man samba_selinux
You don't have to disable SELinux, for samba, just go the the SELinux section in the firewall/security app, drill down to the samba section add disable the items there.
Also, you'll need to use mount.cifs rather than smbmount in FC5 to connect to the outside. What I did was chmod u+s /sbin/mount.cifs & umount.cifs. Then ln -s /sbin/mount.cifs ~/bin/cifsmount... etc...
The cifs is a little different than the old smb* items.
Thank you for your response. However, I have no trouble mounting the windows machineon FC5, it is the FC5 machine which cannot be seen by the other two computers (one ubuntu and the winxp laptop). Your information is very good, though, and I have learned how to do this.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.