« Previous Next »

Thread: can't see iisstart

Last post 11-25-2008 6:08 AM by teejayuu. 2 replies.

Average Rating Rate It (5)

RSS

Page 1 of 1 (3 items)

Sort Posts:

  • 11-25-2008, 5:26 AM

    • teejayuu
    • Not Ranked
    • Joined on 11-25-2008, 5:20 AM
    • Posts 2

    can't see iisstart

    Hi

    I have a Windows 2003 Ent R2 SP2 with IIS installed 'out of the box'.  If I try to browse to http://servername/iisstart.htm I get a 'cannot display web page' error.

    I alos have a second server (same configuration) that works fine - any help with this greatly appreciated.

    Thanks

    Tony

  • 11-25-2008, 5:54 AM In reply to

    Re: can't see iisstart

    1. make sure 'servername' resolves to your web server IP address,
    2. If 'servername' resolves to shared IP of server then you can not access the iisstart.htm using http://servername/iisstart.htm as shared IP is bind to many sites, this is possible only when 'servername' have a dedicated IP.
    3. you are trying to access the link using hostname which can not accessible outside of your local network as 'servername' is not a domain name
    4. if all above 3 possibilities are fine then it may be a permission issue, make sure the folder which contain iisstart.htm have all the necessary permissions to IUSR, it should have atleast read/execute permissions

  • 11-25-2008, 6:08 AM In reply to

    • teejayuu
    • Not Ranked
    • Joined on 11-25-2008, 5:20 AM
    • Posts 2

    Re: can't see iisstart

    Thanks Gabriel, in answer to the above:

    1. Pinging servername resolves to the internal IP address

    2. I presume that you are talking about the Default webite IP address.  I have used both (all unassigned) and the IP address of the server 10.1.1.11

    3. This will be an internal website only and not accessible by the outside world.

    4. The folder C:\Inetpub\wwwroot has Read & Execute, List Folder Contents and Read permissions allowed.  Write permission is denied.

    Hope this helps

    Tony

    Stupid, stupid stupid - Windows firewall was blocking HTTP on the Internal NIC. 

Page 1 of 1 (3 items)
Microsoft Communities