The HTTP protocol automatically finds and assigns a free port to that connection which then it also automatically closes once it has transmitted the files. Which is to say that is doesn't open a permanent channel, it just opens, transmits and closes (that's why you have to use JSP sometimes if you need a persistent connection).
First, I'd say that you verify that connections are actually established on port 80. To see that:
1) In a console type netstat
2) Check if the port 80 is listening
3) Try to access a webpage on your computer and inmediately type netstat
again. You should see that instead of listening
, it should established, time wait
, or something like that. It means that you had a connection (or currently have) which was established.
Once that is off the way, do the same but now with the mandrake firewall High
settings (the ones that let you see the webpage) and do the same thing. But now it should state that other port (which wasn't there in netstat before), has been opened and it's status is established, time wait
or whatever. That was the port used to send data to the client.
Up to this point you should be pretty much aware if mandrake is indeed blocking the out
port, or the problem is still on port 80.
Keep replying until it works