Home / server / Questions / 54623
Accepted
Rob Bell
Asked: 2009-08-16 11:15:44 +0800 CST

Sites in IIS not available externally

  • 772

I'm trying to access my IIS test site using the server IP. Internally I have no problems, but externally it tries for a while and then times out.

I've run Shields Up and it shows that there are no open ports. It's a 1&1 VPS server running Windows Server 2003 so I assume there would be no firewall blocking in the middle. I've read somewhere that I may have to make changes in Administrative Tools > Local Admin Settings to allow access to port 80, but I don't know where to begin looking in here.

Edit:

I am accessing the server using its external IP address, the same I use to log into RDP. 1&1 also provide all VPSs with a subdomain which resolves to the server, which again is fine for RDP but fails with IIS over port 80. Using both the IP and subdomain on the server itself return the site successfully.

windows-server-2003

6 Answers

  1. Best Answer

    Have you checked is Windows Firewall is on? If it is, you should either disable it or (better) allow incoming traffic to port 80.

    Also, are you behind some NAT? You can check it quite easily: run IPCONFIG on the server and have a look at its IP address; if it's different from the external one, then there's some NAT in te middle, and you need your provider to properly configure it.

    Last chance, even if you have no firewall on your server and it's actually sitting on its public IP address, there actually could be some firewall in the middle, so you should check that with your provider, too.

    • 5

  2. The first basic test is to use telnet.exe to connect to the port:

            telnet <ip address> 80

    If you get a 'Connection refused' error then the port is not open.

    Also WS 2003 has a firewall: type firewall.cpl and you should see the local control panel.

    • 3

  3. I have a 1&1 VPS as well, and what I did was run the Security Configuration Wizard

    http://www.microsoft.com/windowsserver2003/technologies/security/configwiz/default.mspx

    After going through all of this, and setting everything up how I wanted, I was able to have complete control over everything on the server.

    I'm sure there is a more complicated way of doing this, but I was impressed with this tools ease of use.

    • 1

  4. Your access your web site via a subdomain, like aaa.stackoverflow.com/Default.aspx or direcly via ip adresse like x.x.x.x/Default.aspx ?

    If you access via a sub domain, your binding is it correct. Did your URL in IIS is set to the correct IP adresse or is set to All IP Adreses ?

    Your external IP adress is it NAT to an internal ip adresse ?

    Can you make a telnet on port 80 from the external ?

    • 0

  5. Try with opening IIS management console, right click on the web site, properties, click on the "Directory Security" tab, then pick Edit button for "IP address and domain name restrictions".

    BTW, you can check if IIS is listening on the external address with netstat -a -p tcp -n within command prompt on the server in question.

    • 0

  6. Aside from the other answers, check your network interface bindings to make sure that IIS is bound to your external interface.

    1. You can do this by going to the website properties, click the Website tab, and then making sure that the IP address text is: (All Unassigned).
    2. Also, make sure that the port is listening on 80 (or 443 for SSL).
    3. Click on the Advanced button. Make sure that the host header value is equal to the domain that you're wanting to reach. For example, if you want your website reachable at http://blog.waynehartman.com, you would have to make sure that blog.waynehartman.com is in the host header.
    • 0