Re: Firewall problems with Samba
- From: ibuprofin@xxxxxxxxxxxxxxxxxxxxxx (Moe Trin)
- Date: Thu, 15 Mar 2007 19:25:03 -0500
On 15 Mar 2007, in the Usenet newsgroup alt.os.linux.suse, in article
<45f8da38$0$495$815e3792@xxxxxxxxxxxxxx>, Will Honea wrote:
All the non-Linux boxes see each other and their shares. They also see
the Linux boxes and the shares are usable. Problem is that none of
the Linux boxes can see anything UNLESS I drop the firewall. Drop the
firewall and all is well, so the problem has to be in the firewall
somehow.
No idea, but fire up a packet sniffer and see what the traffic is, or
turn on the logs in the firewall and see what is being dropped. It sounds
like an overly broad firewall issue. Remember that your firewall can
allow certain addresses/address ranges, and you don't have to open a port
to the entire world - you can restrict it to specific hosts if you want
to. Generally, what ever you are using as a gateway to the world should
be dropping ALL windoze crap in or outbound to the world, but that should
not be effecting packets between hosts on your local network.
I've tried everything I could find with the firewall - opened ports 135,
137:139, and 445 for both tcp and udp but nothing seems to stick.
There are three very simple rules about services and open ports:
#1 - if you don't know what it is, disable it, and see if anything breaks.
#2 - if nothing breaks, then you didn't need that.
#3 - if it appears to have 'broken' some function or service, look in the
logs, and identify the specific problem.
Sounds as if you're on the third step.
Old guy
.
- References:
- Firewall problems with Samba
- From: Will Honea
- Firewall problems with Samba
- Prev by Date: Re: Firewall problems with Samba
- Next by Date: Re: Firewall problems with Samba
- Previous by thread: Re: Firewall problems with Samba
- Next by thread: Name for desktop in stead of number
- Index(es):
Relevant Pages
|
