Using SAMBA

The SuSE 8.2 firewall system partly recognizes the presence of SAMBA servers. It will auto-detect the presence of a Samba server, but examining /var/log/boot.msg shows that port 139 needs to be opened explicitly. Ports 137 and 138 need to be opened as well. Ports 445 (used by Windows clients when NetBIOS over TCP is disabled) and 901 (SWAT admin, whatever that is) help with NetBIOS. However, the firewall still needs to be modified by looking at the file `/etc/sysconfig/SuSEfirewall2' (which can also be modified via YaST2/System/SysConfig editor)...

1. Make sure FW_SERVICE_SAMBA=''yes''. This option may be associated with FW_SERVICE_AUTODETECT and FW_SERVICE_DNS.
2. FW_ALLOW_FW_BROADCAST=''yes''
3. FW_IGNORE_FW_BROADCAST=''no''
4. FW_ALLOW_INCOMING_HIGHPORTS_TCP=''yes'' (or perhaps just `139')
5. FW_ALLOW_INCOMING_HIGHPORTS_UDP=''yes'' (or perhaps just `DNS')

If the broadcasts are ignored, then some SAMBA will work, but the name recognition (?Netbios) does not seem to work.

SuSE 9.1 does not seem to have any of the above configuration requirements.