Link to home
Start Free TrialLog in
Avatar of Sheldon Livingston
Sheldon LivingstonFlag for United States of America

asked on

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 (68.200.212.14). Pinging missioncomponents.com verifies this.  Myipaddress.com shows 68.200.212.14

Server 2008 R2.
I have binded www.missioncomponents.com and missioncomponents.com to the site.
Port 80 is open (http://www.canyouseeme.org)
0.0.0.0 and 10.1.1.178 (local IP) and [::]: are listening on port 80
Local IP is reserved...

10.1.1.178 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

Thoughts?
Avatar of John Easton
John Easton
Flag of United Kingdom of Great Britain and Northern Ireland image

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.
Avatar of Sheldon Livingston

ASKER

Tried that... I created the site in the InetPub\wwwroot directory... default doc is index.html and both services are running...
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.
I have deleted the default site...
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.
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.
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.
From the server, localhost and localhost:801 work.
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 10.1.1.178, port 80.  Then try to access the site from another computer on the local network using http://10.1.1.178

If the above worked this should work too.
I have one binding... no host name.  I CAN hit the site now (using IP) from another computer on the network.
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 missioncomponents.com (unless you have set this up on your local network's DNS).

When I access the site I get another site - LawnAccounting.com - 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.
I assume that you are seeing "LawnAccounting.com" 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 www.missioncomponents.com...
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...
ASKER CERTIFIED SOLUTION
Avatar of John Easton
John Easton
Flag of United Kingdom of Great Britain and Northern Ireland image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
No internal DNS... in fact using Google (8.8.8.8)
Thank you for the assist!
Hm.  Does that mean you can't access local computers by name - i.e. Server1 rather than 10.0.0.1 (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.
I can view other computer via computer name...

Not a big deal...

Thank you for your help.