> Samba is on the same server that is attached to the router and it
> was hacked before.
>

Options:

Get a better router/firewall

Get a firewall dedicated (Smoothwall pfSense IPCop)

Put two NICs in the samba machine (one to the router one to the internal
network) Firewall the one to the router

>
> >>> "Robert Mortimer"

> 11:03:45 pm 27/03/2006 >>>
> Name resolution for windows machines is by WINS or Broadcast. Broadcast is
> not going to like the firewall. Wins could be configured if you
> look up the
> ports to allow and run the SAMBA wins server on the linux machine. My only
> question is what do you not trust on your local network (why the
> firewall?)
>
> Robert
>
> > -----Original Message-----
> > From: samba-bounces+rmortimer=bluechiptechnology.co.uk@lists.s amba.org
> > [mailto:samba-bounces+rmortimer=bluechiptechnology.co.uk@lists.s amba.org
> > ]On Behalf Of Jon Miller
> > Sent: 27 March 2006 14:09
> > To: samba@lists.samba.org
> > Subject: [Samba] cannot see the samba server when browsing
> >
> >
> > I would like to know if there is a rule that can be created in
> > iptables that would allow a samba server shares to be seen on the
> > internal LAN. The interface is on eth0 the ip address of eth0 is
> > 192.168.0.1. It seems that when I applied a firewall I have
> > blocked smb from showing up. Now the users cannot see any shares
> > via Network Neighborhood , but I can map a drive via
> > Start->Run->\\192.168.0.1\sharename.
> > This is on a Debian 3.1 server.
> >
> > Thanks
> >
> > Jon
> >

>


--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/listinfo/samba