damn firewalls
- Bebop0083
- Joined: Wed Oct 30, 2002 4:27 pm
- Status: That's What She Said.
damn firewalls
i was just wondering how to shut off firewalls. im using an windows xp and found out theres a built one in there. thats whats causing my problems with data transfer. with large files such as mpegs. any suggestions?? thanks in advance.
-
trythil
- is
- Joined: Tue Jul 23, 2002 5:54 am
- Status: N͋̀͒̆ͣ͋ͤ̍ͮ͌ͭ̔̊͒ͧ̿
- Location: N????????????????
Erm.
I really doubt that a firewall is causing your problems with large data transfers. There are firewalled sites that transfer gigabytes of data each day and they never have a problem with it.
Hell, I have a firewall here, and I just transferred 180 MB of data, no problem...
Before you shut down your firewall (which is like going onto a whore-infested street and screaming "I NEED TO GET SCREWED"*) I'd recommend making sure that ports 20 and 21 (ftp-data and ftp) are open, as that seems to be your primary problem. They only have to accept previously-established connections, since you're not planning on doing FTP serving.
If that doesn't do anything try checking out the rest of the firewall configuration. The system may be getting tripped up by overzealous rules that just take too long to process. You may want to consider relaxing some of those.
If THAT doesn't do anything, make sure it REALLY is the firewall. Problems with transfers are more often due to problems with other pieces of the system, both local and remote -- ISP issues, network adapter issues, and so forth.
Only shut the thing off if you REALLY have to -- and only do it for that fraction of time. Every firewall has their own killswitch; go read the manual for your specific firewall system. There really isn't much else that can be said without you telling what firewall you have.
I mean, I could tell you to do
but that wouldn't help you much if you weren't using iptables for firewalll rules...
* True, most firewalls don't provide THAT much protection unless you configure them well and watch over them, but it's better than nothing, so long as you don't get lulled into a false sense of security...
I really doubt that a firewall is causing your problems with large data transfers. There are firewalled sites that transfer gigabytes of data each day and they never have a problem with it.
Hell, I have a firewall here, and I just transferred 180 MB of data, no problem...
Before you shut down your firewall (which is like going onto a whore-infested street and screaming "I NEED TO GET SCREWED"*) I'd recommend making sure that ports 20 and 21 (ftp-data and ftp) are open, as that seems to be your primary problem. They only have to accept previously-established connections, since you're not planning on doing FTP serving.
If that doesn't do anything try checking out the rest of the firewall configuration. The system may be getting tripped up by overzealous rules that just take too long to process. You may want to consider relaxing some of those.
If THAT doesn't do anything, make sure it REALLY is the firewall. Problems with transfers are more often due to problems with other pieces of the system, both local and remote -- ISP issues, network adapter issues, and so forth.
Only shut the thing off if you REALLY have to -- and only do it for that fraction of time. Every firewall has their own killswitch; go read the manual for your specific firewall system. There really isn't much else that can be said without you telling what firewall you have.
I mean, I could tell you to do
Code: Select all
root@visions root # /etc/init.d/iptables stop
* True, most firewalls don't provide THAT much protection unless you configure them well and watch over them, but it's better than nothing, so long as you don't get lulled into a false sense of security...
- Dannywilson
- Joined: Wed Jul 31, 2002 5:36 am
- Location: In love with Dr. Girlfriend
- Hitori
- Joined: Wed Feb 06, 2002 1:10 am
- Status: I might be back.
- Location: New Mexico
- Contact:
- klinky
- Joined: Mon Jul 23, 2001 12:23 am
- Location: Cookie College...
- Contact:
Firewalls are overrated 
If you have a buggy piece of software or a trojan it's not going to save you from anything.
Most firewalls operate on a per program basis, so like it's going to tell you "PROGRAM XYZ.EXE WANTS TO RUN ON THE INTERNET. IF YOU SAY NO THINGS MAY NOT WORK PROPERLY FOR PROGRAM XYZ.EXE".
Most people are going to allow XYZ.EXE to get access to the internet, even if they don't know exactly what it is because they don't want to break something and they truely have no clue about the actual purpose of a firewall.
Basically I run w/o a firewall, I have my shares password protected and I disabled the messenger service. There are still some ports open probably that Windows services have left open that "could possibly be a vulnerability". However, I've had no problems. More problems were caused trying to get ICS, port-forwarding or certain apps to work with the firewall, then not running a firewall at all.
When I worked for Att broadband there were so many people calling up, like atleast 1 a day, who installed ZoneAlarm and locked themselves out of their internet connection. Then when they unisntall Zone Alarm, Zone Alarm wouldn't uninstall completely and would remain active and lock their internet completely, they had no recourse but to call ZoneLabs and get them to fix it.
If you're in a corporate setting and you want to make sure that only certain things are going in and out of your network a firewall is great. It's even better when you have someone who knows how to setup a network properly and is willing to maintain it. Someone who has the time to fiddle with opening and closing ports to make sure certain apps work properly.
But in the hands of Joe Schmoe who doesn't know what TCP/IP even stands for, him hitting Yes to every popup that asks if "Program XYZ.EXE" wants to run is not going to help him. Nor is a firewall that only allows port 80 transactions because he may go "Well why does program XYZ.EXE not work..." he either blames the ISP or the program maker, but rarely does he think the firewall is possibly making Program XYZ not work.
Firewalls in the hands of computer newbies = not good.
~klinky
If you have a buggy piece of software or a trojan it's not going to save you from anything.
Most firewalls operate on a per program basis, so like it's going to tell you "PROGRAM XYZ.EXE WANTS TO RUN ON THE INTERNET. IF YOU SAY NO THINGS MAY NOT WORK PROPERLY FOR PROGRAM XYZ.EXE".
Most people are going to allow XYZ.EXE to get access to the internet, even if they don't know exactly what it is because they don't want to break something and they truely have no clue about the actual purpose of a firewall.
Basically I run w/o a firewall, I have my shares password protected and I disabled the messenger service. There are still some ports open probably that Windows services have left open that "could possibly be a vulnerability". However, I've had no problems. More problems were caused trying to get ICS, port-forwarding or certain apps to work with the firewall, then not running a firewall at all.
When I worked for Att broadband there were so many people calling up, like atleast 1 a day, who installed ZoneAlarm and locked themselves out of their internet connection. Then when they unisntall Zone Alarm, Zone Alarm wouldn't uninstall completely and would remain active and lock their internet completely, they had no recourse but to call ZoneLabs and get them to fix it.
If you're in a corporate setting and you want to make sure that only certain things are going in and out of your network a firewall is great. It's even better when you have someone who knows how to setup a network properly and is willing to maintain it. Someone who has the time to fiddle with opening and closing ports to make sure certain apps work properly.
But in the hands of Joe Schmoe who doesn't know what TCP/IP even stands for, him hitting Yes to every popup that asks if "Program XYZ.EXE" wants to run is not going to help him. Nor is a firewall that only allows port 80 transactions because he may go "Well why does program XYZ.EXE not work..." he either blames the ISP or the program maker, but rarely does he think the firewall is possibly making Program XYZ not work.
Firewalls in the hands of computer newbies = not good.
~klinky
- Bebop0083
- Joined: Wed Oct 30, 2002 4:27 pm
- Status: That's What She Said.
- Hitori
- Joined: Wed Feb 06, 2002 1:10 am
- Status: I might be back.
- Location: New Mexico
- Contact:




