Samba and Firestarter issues. Not playing together.

[Dave]

Ok, Im running samba on my Pc in ubuntu. Im also running firestarter
for the firewall. Im sitting behind a router and all my "3" computers
are on dhcp with reserved ip's so i can use port forwarding to the
ubuntu pc for ssh. "too lazy to set it up static" shouldnt matter i
dont think???

My problem is, I can ssh from my laptop running windows xp pro to the
server/ubuntu no problem after setting a rule in firestarter. I can
also ping the server and my router no problem. I start the xp laptop
and try to connect to the server so i can copy files back and forth
and no go. I disable firestarter and it connects to the ubuntu pc no
problem.

Ok, ive tried everything with firestarter all the way to just opening
up the ubuntu server to all incoming connections from the laptop and
its a no go connecting to samba untill i shut down firestarter. Once
connected, I can turn firestarter back on and i dont have to worry
again untill i reboot the laptop and then it starts over.

Does anyone have any suggestions as to what the problem is? I know
this has to be something simple that i am overlooking.

Thanks.

[Odie]

Dave schreef:

<cut>
Problems with samba and firestarter firewall
</cut>

First basic thing i could think off: Have you set a rule in firestarter
to allow samba traffic? You have to set a rule that allows incoming
traffic on port 137,138,139 and 445. There is also a special samba entry
in the pull-down menu if you add a new rule.

[dave]

Odie wrote:

> Dave schreef:
>
> <cut>
> Problems with samba and firestarter firewall
> </cut>
>
> First basic thing i could think off: Have you set a rule in firestarter
> to allow samba traffic? You have to set a rule that allows incoming
> traffic on port 137,138,139 and 445. There is also a special samba entry
> in the pull-down menu if you add a new rule.

Yes, that was the first thing I did was set up the rules for Samba. The
first time I tried to connect the firewall complained about me trying to
connect from my other computer and refused. Then I set the rules to
allow the connection and tried to connect again. The firewall wasnt
showing a blocked connection anymore but it still wasnt allowing a
connection. Thats the part that is confusing me a little. Once I turn
the firewall off it connects fine.

[Toby Newman]

On 2006-03-31, Dave <bl@w.me> wrote:

> Ok, Im running samba on my Pc in ubuntu. Im also running firestarter
> for the firewall. Im sitting behind a router and all my "3" computers
> are on dhcp with reserved ip's so i can use port forwarding to the
> ubuntu pc for ssh. "too lazy to set it up static" shouldnt matter i
> dont think???
>
> My problem is, I can ssh from my laptop running windows xp pro to the
> server/ubuntu no problem after setting a rule in firestarter. I can
> also ping the server and my router no problem. I start the xp laptop
> and try to connect to the server so i can copy files back and forth
> and no go. I disable firestarter and it connects to the ubuntu pc no
> problem.
>
> Ok, ive tried everything with firestarter all the way to just opening
> up the ubuntu server to all incoming connections from the laptop and
> its a no go connecting to samba untill i shut down firestarter. Once
> connected, I can turn firestarter back on and i dont have to worry
> again untill i reboot the laptop and then it starts over.
>
> Does anyone have any suggestions as to what the problem is? I know
> this has to be something simple that i am overlooking.

Wow, I have exactly the same problem! I can ssh, serve http, etc all
fine from Kubuntu to my XP box but the samba server is blocked.

If I click "stop" in Firestarter and wait a moment, then I can connect
from XP for file sharing fine. If I click "start" in firestarter then I
can still connect fine, until XP reboots.

'Tis most queer.

Firestarter is the last firewall I settled on since trying Guarddog and
KMyFirewall (both still installed) so I suspected this may be caused by
their settings interfering with Firestarter.

Are Firestarter, Guarddog and KMyFirewall all simply frontends to
IPTables? Perhaps this could be solved by 'looking under the hood'?

--
-Toby, who...
Add the word afiduluminag to the subject
field to circumvent my email filters.
Ignore any mail delivery error.