Thanks for the reply My filter rule is allow http from any to internal network my NAT rule is this from any to external interface/http forward to (web server)
I use identical rules for ftp and https(same server) and they both access with no problems
It's really wierd...I'm using version 4. I can ping it and I can access https and ftp from the outside. The rules for all 3 services(http, https, ftp) are the exact same.
I can access all 3 services from the inside, so I'm 99% sure it's not the web server.
I have also tried it with the proxy off and it still shows the http port closed and the other 2 open.
-stumped
ps. your probably right, Rick...
but it doesn't seem logical to close 80, but allow 443 and 21
I know some ISP's closing ports like 25 en 80 incoming so people can not run servers. Maybe the figured out that if they close port 80 incoming people will not run servers and therefore they do not close the other http ports?
I figured out why the port is not open.... when i create the rule to open port 80 with the GUI it does not really create one.. When I open the "Packet Filter Live Log" my rules is not there...
Can I edit the script manually to add the rule? If so, where can I find the firewall script?
I figured out why the port is not open.... when i create the rule to open port 80 with the GUI it does not really create one.. When I open the "Packet Filter Live Log" my rules is not there...
Can I edit the script manually to add the rule? If so, where can I find the firewall script?