Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
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`ve configured the smb.conf in all the ways I can think of, but even though I see my server (running fedora 4) listed in the Windows-network workgroup, I still can`t get in to it.
I`m a newbie, so I guess it is a simple mistake, but haven`t figured it out by reading around on several pages
Anybody?
What happens when you access the computer through the workgroup?
Does it give a password prompt? Can you login?
Do you have SELinux or a firewall set up on Fedora that prevents Samba?
You can run "system-config-security" to check on whether the Firewall is enabled/disabled, and also how SELinux is configured, (firewall will be enabled by default and may be blocking the needed ports). Also you can use the command "testparm" to check your smb.conf file for errors & configuration. Also there is "system-config-samba" for a nice GUI front-end to the smb.conf file. You might also check the samba log files in "/var/log/samba/" for more clues as to why it is failing to connect.
Got it!
It was the firewall.
I configured it by running the command "system-config-securitylevel", and then allowing all traffic in eth0. Guess this is allright as long as I have a ruter with firewall.
(The "service"-commmand is not found..neither "ifconfig". Are these not common commands in fedora-linux running bash?)
There commands are in /sbin which is not in the default $PATH for regular user accounts. You need to be root to run those. I'm not sure if exporting a new path will allow these commands to run correctly under a regular user account priviliges.
Try and tweak iptables more specifically to your needs, it's not usually good practice to allow ALL traffic from a device. If you need some pointers i'm sure aynone here would be glad to help. Just my two cents
Turned out that when I was logged on as "root" through a regular account, I cuold not run those commands, but when I logged on directly as "root" it was ok..bit strange, not? But the important thing is that I now can do the magic, thanks guys
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.