Configuring Built in Redhat Firewall

[CovertCow]

When installing redhat, I chose only MAIL, FTP, and HTTP to be accepted through the built-in firewall. I want SAMBA to be able to work. I followed a howto (http://samba.netfirms.com/sambconf.htm) and logically it should be working. However, when I find the workgroup with the samba server in it, WinXP, it says:

"//webserver1 is not accessible. You might not have permission to use this network resource. Contact the administrator of this server to find out if you have access permissions

The network path was not found."

This makes me think that the redhat built-in firewall is passing one of the ports necessary to use SAMBA, but not the ports necessary for authentication or whatever other port is necessary to get at the network resources.

If you have any ideas as to how I could change the built-in redhat firewall without the gui I would really appreciate it.

 

[FUBAR]

Well I don't know how to change it, because I don't run the redhat way, but I do know how you can troubleshoot it. IMO, their config style is a mess, or at least it looked like it when I created a dump of my active rules...

Anyway, you can shut the firewall off then you'd be able to test if it's the firewall getting in the way, since you don't seem to know FOR SURE yet. Just type, as root,

/etc/init.d/iptables stop

and see if things come to life.

 

[Buddha Bart]

fyi: you might have to use /etc/init.d/ipchains stop, depending on what version you're using and all

if it turns out that is your problem... editing it is gonna be... interesting. Those auto-generated firewalls, along with redhats setup and configuration scritps make for a lot more factors to deal with than are gonna be covered in your basic howto's & FAQ's

bart

 

[FUBAR]

Actually, since RH has included the built in firewall, they've been on the 2.4 kernel, hence iptables, but they do include scripts for both now that I think of it.. don't know why they'd go back tho

Assuming that RH sticks with their own defined standard, the iptables config should be something like /etc/sysconfig/iptables and boy is it messy... I can't get into the FW at work right now to post the crap that it spews, but it's a far cry from the nice purdy scripts I created...err...downloaded and hacked up...

At any rate, if you can decipher them, you just need to turn off the port 137/139 blocking, or add a rule for them to be allowed. You only really need one of those in there, but I can't remember which it is, again, I'm away from the box now.