Hi Kurt, i had the same problem as Thorsten, and in my case, the only thing I had to do, was to putt he Broadcast to yes. Every other option did not work for me, even if i typed in the correct smb name. As far as i know, the FW Broadcast is a Kernel 2.4 thing, and necessary for the correct work of samba. If i am wrong please correcgt me. Regards, Daniel Schulz -----Ursprüngliche Nachricht----- Von: Kurt Minder [mailto:kurtminder@bluewin.ch] Gesendet: Donnerstag, 14. November 2002 11:36 An: Suse-Security (E-Mail) Betreff: AW: [suse-security] Samba - Suse firewall
-----Ursprüngliche Nachricht----- Von: Daniel Schulz [mailto:bugtraq@i-smo.de] Gesendet: Donnerstag, 14. November 2002 08:26 An: 'Torsten Schaefer'; suse-security@suse.com Betreff: AW: [suse-security] Samba - Suse firewall
Hi,
i think you should enable FW_ALLOW_FW_BROADCAST in your Firewallconfig and set FW_IGNORE_FW_BROADCAST to "no". In order you set ports 137:129 free this should work.
Thats not nessecary when samba is running on the fw box. AFAIK this option is used when netbios should traverse sub-nets through the firewall. Maybe you can not browse the servers. But when you type in the a smb name of a server you can connect. I think Togan goes to the right direction. Why does the fw block a paket that is allowed in the roules? Cheers Kurt -- Check the headers for your unsubscription address For additional commands, e-mail: suse-security-help@suse.com Security-related bug reports go to security@suse.de, not here