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

hello
 

another jchapman

looking to figure out howto get freebsd going when i stumbled in a search upon this Wow! Holler atcha!