View Full Version : Samba and Firestarter
panama
15th March 2005, 12:55 PM
The problem is whenever I have firestarter enabled on my linux server, I cannot access any of the samba shares from my windows 2000 system. I have the latest version of firestarter installed. I granted access to the samba ports inbound as as well as outbound in firestarter. I still cannot access the share drives on my linux server. But as soon as I disable firestarter, I can view share on my linux server from my win2k system. What am I missing? :confused:
jayemef
15th March 2005, 03:40 PM
Just look at the events/hits tab while you are trying to access these directories. It will tell you exactly what is getting blocked. From there you can set a policy to allow for those ports. My guess is that you need to open 137 and/or 139.
panama
15th March 2005, 05:45 PM
jayemef there is nothing listed in the event/hits tab. The policy is set to allow those ports access, It shows as 137-139 and I think the other is 445. I thought these ports are open because it was granted access via firestarter, Is that correct????
jayemef
15th March 2005, 06:57 PM
What version of firestarter are you using? The most up-to-date version is quite different from the original ones. Go to Edit > Preferences, and go to Events. Do you have anything listed in here? If you look, it says "Do not log events for the following," meaning that anything in here will not show up on the events tab. When I updated firestarter, I made the mistake of making all of my policies in here. The effect was that, not only were the ports still closed that I wanted to open, but firestarter wouldn't tell me if it was blocking them. Took me a while to realize what was going on. In order to actually open ports, you need to go back to the main interface and select the Policy tab. In here, go to the bottom area, where it says "Allow service | Port | For," right click, and add your rules. Once they are set, click on the Add Policy button at the top.
panama
15th March 2005, 08:24 PM
I have done everything you listed
jayemef
15th March 2005, 09:25 PM
Then what is the exact method you are using to access these shares, and what are the exact error messages, if any, that you get? Also, which computer is the client machine and which is the server? It's hard to tell from your description.
panama
16th March 2005, 12:05 AM
Samba is running on linux server, the client is running win2k and when I try to access samba with firestarter enabled I get the following "The network path was not found"
panama
16th March 2005, 12:16 AM
These are the steps that I am trying to access the samba share on my linux system from client win2k:
Clicked on My Network Places
Clicked on Entire Network
Clicked on Microsoft Windows Network
Clicked on Workgroup
Then I see my samba server which is called lacasadepaz
When I click on lacasadepaz then I get "The network path was not found." but as soon as I disable the firewall I can access the share on samba server with no problems
panama
16th March 2005, 12:24 AM
This is the correct error message
\\Lacasadepaz is not accessibe
The network path was not found.
[B]
ginotech
16th March 2005, 12:57 AM
i get the same thing.
jayemef
16th March 2005, 01:51 AM
What happens when you do it by IP? Go to Start > Run and enter
\\your_linux_ip
jsn
16th March 2005, 11:52 AM
Hi,
My configuration: w2k machine has static ip: 192.168.0.2 and linux has 2 nics one of those has static ip: 192.168.0.1 for LAN. Firestarter worked nicely with it until i updated it to 1.0 (1.0.3 at the moment). I followed the hits that came from
W2K machine when trying to access samba shares from there and following them made me do this kind of setup:
[policy] - editing [inbound traffic policy]: Allow connections from host 192.168.0.2
Allow service: Samba (SMB) port: 138-139 445 for: 192.168.0.2
Allow service: Samba (SMB) port: 138-139 445 for: 192.168.0.1
Policy was added with: rigth click Add rule -> allow service [name: samba] and entered ip's manually.
I think main reason for it did not work was i had not setup allow connections from 192.168.0.1 for it.
This is my current setup, the 'allow connections from host 192.168.0.2' may not be neccesary i just added
it there later on. Anyway this is working setup for me for samba with W2K and FC3.
panama
16th March 2005, 12:18 PM
My LAN configuration is simular to jsn with the exception of static ip. win2k 192.168.8.4 and linux Samba server is 192.168.8.2 Here is my setting [inbound traffice policy] Allow service: Samba (SMB) port: 138-139 445 for: everyone. I did set and allowed service for specifically for linux box, I will add it and see what happens.
jsn
16th March 2005, 01:13 PM
Hehehe, never mess up with the settings that work. Here's what i did after my message: I edited some rules
for fun of it (yea), all the sudden nothing worked anymore. I rebooted my linux box (nice habit from windows times),
and my internet connection worked but not to any secure websites (bank etc). What i did next was just to erase whole
firestarter and it rules /etc/firestarter totally.
Re-installed, re booted launched the firestarter and net worked again in good way in a moment (it took some time). Internet connection sharing worked (after wizard). but not the SAMBA :) i checked what happens when w2k client tries to access samba clients. For some reason it tried to connect 192.168.0.255 then i did set "allow connections from host: 192.168.0.2" which is the w2k machine ip. after some time (took a bit) the samba shares started to work again. (I have had auto apply policy change immediatly on.)
panama
17th March 2005, 12:43 PM
jsn when you made changes to "allowed connections from host: 192.168.0.2" how ling did it take, in minutes, before you were able to access your samba shares
jsn
17th March 2005, 02:06 PM
Only a moment, less than minute.
panama
18th March 2005, 12:37 AM
After several weeks I finally got it to work. For some reason, when I try to access linux server via My Network places it would say access denied. When I enter \\l192.168.0.2, linux server ip, from my win2k machine I was able to connect with no problems. Thanks for everyone's input this has been a great learning experience.
GrahamB
19th March 2005, 03:44 AM
The problem is whenever I have firestarter enabled on my linux server, I cannot access any of the samba shares from my windows 2000 system. I have the latest version of firestarter installed. I granted access to the samba ports inbound as as well as outbound in firestarter. I still cannot access the share drives on my linux server. But as soon as I disable firestarter, I can view share on my linux server from my win2k system. What am I missing? :confused:
Hi Panama!
Sorry for this simple question, but:
Are you perhaps ALSO using NFS and /etc/exports to share your directories. And then blocking these with your firewall?
????????????
GrahamB
19th March 2005, 03:49 AM
Hi you All!
Sorry, I answered this without reading page two!. :rolleyes:
Oh, well!
tiberiu
19th March 2005, 07:28 PM
Hi!
I have the same problem, but I will try the idea with typing the ip.
tiberiu
20th March 2005, 09:36 PM
Yes, now it works just typing th ip...
Thanks for the tip!
03giant
23rd June 2005, 12:47 AM
Has anyone figured out why you can connect from the w2k machine using the IP addy of the Linux share and not the name?
03giant
23rd June 2005, 12:59 AM
nevermind, i figured it out.
to use the names, turn off "Block broadcasts from external network".
this is located in Firestarter under:
Edit --> Preferences --> Firewall --> Advanced Options
vBulletin® v3.8.7, Copyright ©2000-2013, vBulletin Solutions, Inc.