Samba and Firewall

Brian Marr cabernet at internode.on.net
Tue Dec 10 14:38:58 CST 2002


Suse 8.0 
Using SuSEfirewall2. For my LAN I have got this in the script. 
FW_SERVICES_INT_TCP="139 631 4559"
The 139 is my Samba port. I have found it necessary to start the SuSEfirewall2 
script manually if I shut down my system for some reason.
This script is found in /etc/sysconfig.
Brian Marr

On Tuesday 10 December 2002 13:00, Matthew Geddes wrote:
> On Tue, 2002-12-10 at 09:02, Ralf Brandt wrote:
> > Hi Methew,
> > I've tried to follow your suggestions. I've entered all the commands
>
> [snipped long line]
>
> It's probably best that you double-check the firewall rules against the
> other rules you have, to make sure that all of the fields are correct
> and that you're not blocking something important from either the client
> or the server.
>
> Without knowing the exact error message, it's difficult to tell what the
> problem is, but it could be that browse traffic and/or netbios name
> resolution traffic are still being blocked. If you're comfortable with a
> packet sniffer, I'd suggest that you watch the network and see what it
> is that the client (XP) seems to be sending to the server repeatedly and
> not getting a reply. You should then be able to create a quick iptables
> rule to allow that traffic.
>
> thx,
> Matt

-- 
LinuxSA WWW: http://www.linuxsa.org.au/ IRC: #linuxsa on irc.openprojects.net
To unsubscribe from the LinuxSA list:
  mail linuxsa-request at linuxsa.org.au with "unsubscribe" as the subject



More information about the linuxsa mailing list