IP Cop and port fowarding

[mooseracing]

I have the basic green and red interface. 192.168.0.x is the Green.

I have a port fowarding rule for a web server set for port 80 to 192.168.0.100, my web server. The web server has windows firewall turned off.

In the firewall logs of IPCop I am getting:
09:39:07 NEW not SYN? eth1 TCP 99.148.x.x 5179 ::::: 192.168.0.100 80(HTTP)

which seems right except for the NEW not SYN?

I'm not familiar with that output. The web server works internally fine. So I feel IPCop is blocking it somwhere. When I opened RDP port all it took was fowarding it, but that doesn't seem to be working for HTTP.

Edit: just tried an FTP port as well.... same problem.
here is the fowarding rule for web traffic:

TCP DEFAULT IP : 80(HTTP) 192.168.0.100 : 80(HTTP) Web

 

[RadiclDreamer]

May want to remove that if its your real IP.

Some isps block port 80, do you know if this is the case with yours?

 

[mooseracing]

Thanks, not my IP but I removed it anyway.


I wouldn't think my ISP is blocking it if it reaches the firewall on IPCop?

edit: also tried canyouseeme.org and it says for port 80:
Error: I could not see your service on 24.236.254.200 on port (80)
Reason: Connection timed out

So that still leads me to believe IPCop is stopping it.