Configuring IIS

I've done this many, many times... now I can't get a website to come up.

Using IIS I am trying to get a simple site up and running.

Domain is secured (GoDaddy) and forwarded to my public IP ( Pinging verifies this. shows

Server 2008 R2.
I have binded and to the site.
Port 80 is open ( and (local IP) and [::]: are listening on port 80
Local IP is reserved... has port 80 forwarded.

If I try to "browse" the home page through IIS I get a "This webpage is not available" error
"Browsing" the site from IIS shows same thing

Sheldon LivingstonConsultantAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

John EastonDirectorCommented:
If you are browsing the site locally (i.e. through IIS) and getting a page cannot be displayed error then we need to start there.

Going right back to basics have you checked the IIS Service and World Wide Web Service are both running.

If so, check the Default documents settings.  I.e. you may have an index.php as your home page but IIS is configure to look only for index.html etc.
Sheldon LivingstonConsultantAuthor Commented:
Tried that... I created the site in the InetPub\wwwroot directory... default doc is index.html and both services are running...
John EastonDirectorCommented:
If you stop the Default Website, and start it again do you get an errors?

You will usually get an error if something else is trying to listen on port 80.
Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

Sheldon LivingstonConsultantAuthor Commented:
I have deleted the default site...
John EastonDirectorCommented:
I assume therefore you have create a new site which also points to the InetPub\wwwroot directory.

If so, is this site running, and if you start and stop it do you get any error messages?

Also, check the file permission on the InetPub\wwwroot directory.  If the site is using anonymous authentication you should make sure the IUSR_computername account has permission to at least read from the folder.
Sheldon LivingstonConsultantAuthor Commented:
I created a new site sitting in wwwroot.

The site is running... no errors on starting or stopping it.

IUSR_computername has read / execute / list folders permissions.
John EastonDirectorCommented:
Ok, that is all the obvious reasons I can think of.  Can you add an additional binding (which we will delete later).

For IP Address leave it set to 'All Unassigned' and a random port (I usually go for something like 801, 8090 etc).  Avoid ports you know to be in use.

Then on the server browse to http://localhost:801 (or whatever port you have used).  If it loads the issue is with the bindings, otherwise the issue is with the config of IIS or the site.
Sheldon LivingstonConsultantAuthor Commented:
From the server, localhost and localhost:801 work.
John EastonDirectorCommented:
Ok.  It looks like the Site is setup, so the issue is likely to be with the binding or permissions.  You can delete the extra bindings from the last reply.

With the current bindings remove (again just for now) the host name for all the bindings.  This should leave one of the binding being for IP Address, port 80.  Then try to access the site from another computer on the local network using

If the above worked this should work too.
Sheldon LivingstonConsultantAuthor Commented:
I have one binding... no host name.  I CAN hit the site now (using IP) from another computer on the network.
John EastonDirectorCommented:
Ok.  So we are making some progress.  Now if we add the host header back you will stop being able to access it on the local network because you won't be sending the host name of (unless you have set this up on your local network's DNS).

When I access the site I get another site - - is this also setup on your server?

If so, what are the bindings for this site?  I wouldn't expect another site to load unless it was set to reply to all requests on port 80 which could be conflicting with this site.
Sheldon LivingstonConsultantAuthor Commented:
I assume that you are seeing "" in the title... if so then that is good!  That what we want.

There is only going to be one site on this server.

So it sounds like you can hit
Sheldon LivingstonConsultantAuthor Commented:
I just remoted into another computer and can hit mission... I cannot from my computer that is on the same network.  This isn't the end of the world though...
John EastonDirectorCommented:
Ah.  That explain's my confusion.  If I access either the domain name or the IP Address then I get a site advertising a 30 day free trial with a title of

Is this the site you are hosting?  If so, it looks good from the outside world.  All that leaves therefore is allowing you to access it from inside the network.

This is an internal DNS issue.  Do you have a DNS server inside your network - in particular one which is not used by public internet.  If you have an active directory site you will almost certainly have DNS servers associated with it.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Sheldon LivingstonConsultantAuthor Commented:
No internal DNS... in fact using Google (
Sheldon LivingstonConsultantAuthor Commented:
Thank you for the assist!
John EastonDirectorCommented:
Hm.  Does that mean you can't access local computers by name - i.e. Server1 rather than (for example).

Normally what I would do is setup internal DNS to point to the local address of the server and the public DNS to point to the public IP of the server.

Generally, accessing the public IP address from inside the router doesn't seem to work.  Why I've never been entirely sure,  It may be possible to set the router up to route traffic from the internal network to mission.. back to your internal server - but this would depend on the router.  Unfortunately this start to go beyond my knowledge without being sat in front of it anyway.
Sheldon LivingstonConsultantAuthor Commented:
I can view other computer via computer name...

Not a big deal...

Thank you for your help.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft IIS Web Server

From novice to tech pro — start learning today.