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.
alright, i restarted and yeah, the firewall does tell me "warning: detected samba running, starting FW_SERVICE_SMB."
i noticed that in the shutdown process, it was attempting to shutdown the SMB and NMB daemons, but they weren't running. this kinda makes sense because earlier swat told me that they weren't running either, then when i tried to start and restart them, the page refreshed but they still weren't running. does any of that sound familiar?
Not really. The very next line after the one that mentions FW_SERVICE_SMB is the one that tells me I need to enable port 139. On the other hand, I know the samba daemon is running, because I have absolutely no problem with the firewall off (I don't remember, but I think SWAT reports it as active).
Let me know if it still seems the same to you. Regardless, good luck.
i went to etc/sysconfig/SuSEfirewall2 and changed the following:
FW_SERVICE_INT_TCP: "137:139"
FW_SERVICE_SAMBA: "yes"
and now i'm no longer getting the error messages during boot, but:
-my workgroup still isn't visible on my suse machine
-during boot, i get an error that says "interface eth0 is not (yet?) active Warning /etc/resolv.conf not found"
-smbd and nmbd are still not running despite being enabled in boot via yast
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.