Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm having an issue with my Windows Server 2008. I can successfuly connect to it with FTP(port 21), remote desktop(whatever the port number is), https but not with simple http or port 80, from the outside of my LAN.

Is there some settings I don't know about regarding this special port on the firewall or on IIS7?

For your information, I can connect to port 80 as long as I'm on the same LAN, but as soon as the request come from the outside, I get nothing...

Please help
Thank you

share|improve this question
I know some ISPs block this port, but I can't imagine they'd allow HTTPS and FTP but not HTTP. Have you verified there's nothing on your hardware firewall or router blocking port 80? Did you tell IIS to listen on the correct IP address? Perhaps you could try binding it to a non-standard port and then try to access it from an external source. – Kyle Buser Sep 14 '10 at 22:56
It sounds crazy, but that's exactly what the local ISP does, to residential customers at least. They allow all ports inbound except 25 and 80... sigh – BenGC Jan 8 '11 at 18:44
@Kyle That's what I had to do when I was with Cox. (worst company name ever :P) Verizon doesn't seem to block it though, so yay. I found that it was pointless to use a nonstandard port since they block them at work anyway :( It has to do with their service agreement: I think most ISPs have a "no server" clause ... they want you to use their business products. It's dumb. – Daniel B. Jul 26 '11 at 12:36
up vote 0 down vote accepted

As mentioned in comments, if you are using an ISP's residential plan, there's a good chance they're blocking port 80. Try using a nonstandard, or even just 8080, and see if you can get to it from an external source.

share|improve this answer
To be clear, are you accessing this from outside your network, or are there other private networks you've tried to access from? – Daniel B. Jul 26 '11 at 12:40

Could be the firewall on the server, you have the "Scope" option in Windows firewall, usually set to localnet.. which you would need to change to any.

You could read this post in regards to windows app firewalls: is 2003 Server Firewall appropriate Or this Windows Firewalls + GPO's As you might be setting your firewall via GPO (If you are in a domain)

share|improve this answer

It sounds to me like there is some ACL between your connection to the Internet and to the server. Perhaps ask whoever administers your firewall to double check the policy to that machine?

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.