We help IT Professionals succeed at work.

Check out our new AWS podcast with Certified Expert, Phil Phillips! Listen to "How to Execute a Seamless AWS Migration" on EE or on your favorite podcast platform. Listen Now


Port 80 blocked on just one site, and only from inside our firewall

shoge asked
Medium Priority
Last Modified: 2013-12-04
Here's our odd situation that cropped up today....

We have a web server sitting outside our firewall using both HTTP and HTTPS.  From inside our network I can browse using the HTTPS port, but not HTTP.  I can browse any other server, either ours or anyone elses, with HTTP just fine, and anyone outside our network can browse to our server using HTTP (or HTTPS) also just fine.

All the servers are running Win2k and IIS.  We're running RRAS using NAT as our firewall.

Telnet to port 80 inside the firewall never connects.  Telnet to port 443 inside the firewall works fine.  From anywhere else (in the world) outside the firewall (including the firewall itself), port 80 opens as is normal.

(The obligatory...) This worked fine yesterday and (also the obligatory) no, there is nothing that we are aware of that has changed in any of the server configurations.  Again, we can browse anywhere else normally, just not this server.... but it WILL connect using HTTPS.

The server appears to be correctly configured to respond to both 80 and 443 for this particular web site.

Ok, have at it! :-)

Watch Question

Apparently your firewall is blocking port 80 from the inside to this box on the outside.


But then why would I be able to browse any other site?  If port 80 were blocked, then I would expect that I wouldn't be able to browse at all.
As I said, it's probably blocking from the inside to the box on the outside.  Specifically to that box.


Ok, the RRAS service on the firewall reports no input or output filters on either the LAN or WAN interfaces.  Also, no filters defined for the adapters themselves on either the firewall or web server.  If it's being filtered, I can't find it.


portqry does report that it is FILTERED.  I just haven't a clue as to where.

Here's the other odd thing... If I connect to the web site's address inside the firewall (it has two adapters and bridges the firewall) on port 80, it opens just fine.
You'll need to access the inside adapter from inside the firewall.


Well, that's our workaround for now, but I want to understand WHY this is happening. :-)
Unlock this solution and get a sample of our free trial.
(No credit card required)
Unlock the solution to this question.
Thanks for using Experts Exchange.

Please provide your email to receive a sample view!

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.


Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.