strange server / client prob. with samba using SuSEfirewall2 /etc/hosts
Hi list! I already googled and grouped for that strange problem, so I hope to find here some answers. Since I updated to SuSE 7.3/ SuSEfirewall2 / protect from internal = yes ... Port 139 internally open, it somethimes occurs a problem connecting to the samba server (domain master) from any windows client: There is even nohting about a connection in the smb /nmb logs except if the hosts were listed in /etc/hosts. ^^^^^^ In the firewall log I've found some drops from the client ips connecting to the server (PROTO = UDP; SPT = 137), but this should nothing had to do with it? So I finally solved a part of it, but don't understand it... is this SuSEs understanding of security? Please excuse my very bad english. best regards, Vincent Kurtz
I already googled and grouped for that strange problem, so I hope to find here some answers. Since I updated to SuSE 7.3/ SuSEfirewall2 / protect from internal = yes ... Port 139 internally open, it somethimes occurs a problem connecting to the samba server (domain master) from any windows client: There is even nohting about a connection in the smb /nmb logs except if the hosts were listed in /etc/hosts. ^^^^^^ In the firewall log I've found some drops from the client ips connecting to the server (PROTO = UDP; SPT = 137), but this should nothing had to do with it? So I finally solved a part of it, but don't understand it... is this SuSEs understanding of security?
Hi Kröte for sure are some udp port related to smb/netbios traffic. There is an option according samba in the config file for samba, but i wouldnt suggest to use it, cauze it opens the samba to outa world too. If you grep /sbin/SuSEfirewall2 for samba you'll see, that udp 137/138 are involved too. So open it to internal NIC. Further comments welcome what services that are. Think broadcast and browsing. Michael Appeldorn
for sure are some udp port related to smb/netbios traffic. There is an option according samba in the config file for samba, but i wouldnt suggest to use it, cauze it opens the samba to outa world too.
I've allready done this, if you mean: FW_SERVICE_SAMBA="yes" ... it's not a sec. problem, because this server is running behind a firewall.
If you grep /sbin/SuSEfirewall2 for samba you'll see, that udp 137/138 are involved too. So open it to internal NIC.
HTH hope it helps ;-)
Michael Appeldorn Thank you very much, Vincent Kurtz
participants (2)
-
die schildkroete -
Michael Appeldorn