Hey . I am running a samba server for some windows clients, but i also want to secure the server with SuSEFirewall2. What port on the server do I have to open, to let the windows clients access the samba share ? Thanks. -- Vh Peter á Rógvu
I am running a samba server for some windows clients, but i also want to secure the server with SuSEFirewall2. What port on the server do I have to open, to let the windows clients access the samba share ?
Depending on the services provided: port 137 is used for NetBIOS browsing port 138 is for NetBIOS name service port 139 is for sharing (file and printer) port 445 is used by Win2K/XP clients when NetBIOSoverTCPIP is disabled SWAT admin uses port 901 I would guess you do not enable 445 nor 901 and you might be able to drop 138 if you do no use (NetBIOS) name service. Of course one can check with "netstat -an" before and after starting the samba related scripts (rcsmb, rcnmb). After rcnmb the UDP ports 137 and 138 are open. Running "rcsmb start" adds the TCP port 139 to this list. This probably means that: TCP 137 and 138 probably can be closed UDP 137 and 138 probably need to be open TCP 139 needs to be open The SMB/CIFS protocol may have some extra requirements too (but I guess not). If you can experiment with using iptables logging then you might find out the exact behaviour - of course books will help too. regards, timo
On 05/29/2003 06:18 PM, Peter á Rógvu wrote:
What port on the server do I have to open, to let the windows clients access the samba share ?
UDP 137 138 and TCP 139 -- Joe Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Web Address: http://www.mydestiny.net/~joe_morris Registered Linux user 231871 God said, I AM that I AM. I say, by the grace of God, I am what I am.
participants (3)
-
Joe Morris (NTM)
-
Peter á Rógvu
-
timo