I'm running Wk8 R2 Sp1. I had a few things running fine on the Default Web Site under IIS 7.5 (Terminal Services RDPWeb, a user application) until a 3rd party installed a new web site for another app and left the default port for the new site as 80. As
soon as that new web site was created the Default Web Site showed a question mark inside the globe icon. I asked the 3rd party to set the port on the new site to something else (port 81) but even after that nothing works on my Default Web Site any more. I've
restarted the entire server but that hasn't helped.
When I try to browse to any of the URLs hosted by the Default Web Site IE simply says "Internet Explorer cannot display the webpage". No error numbers nothing. There are no new logs appearing either so it's as if the clients aren't getting to the IIS server
at all.
I'm not quite sure what you mean checking the folder is correct. Do you mean is it pointing to C:\inetpub\wwwroot? If so then yes it is. I can browse to the IIS7 default page fine, it's all the other sites and apps running under it that don't work.
The new site was added by a 3rd party. They did it manually by clicking "Add Web Site" and linking it to a directory on the server. They left the default binding as port 80, clicked OK and as soon as they did I saw the question mark appear on the Default Web
Site.
Fixed it. Looked at the site bindings for https and there was no certificate specified. I selected the certificate I installed from the drop-down and hey presto! it all works again.
broonster27
5 Posts
Default Web Site No Longer Working
May 02, 2012 01:47 AM|LINK
I'm running Wk8 R2 Sp1. I had a few things running fine on the Default Web Site under IIS 7.5 (Terminal Services RDPWeb, a user application) until a 3rd party installed a new web site for another app and left the default port for the new site as 80. As soon as that new web site was created the Default Web Site showed a question mark inside the globe icon. I asked the 3rd party to set the port on the new site to something else (port 81) but even after that nothing works on my Default Web Site any more. I've restarted the entire server but that hasn't helped.
When I try to browse to any of the URLs hosted by the Default Web Site IE simply says "Internet Explorer cannot display the webpage". No error numbers nothing. There are no new logs appearing either so it's as if the clients aren't getting to the IIS server at all.
HostingASPNe...
736 Posts
Re: Default Web Site No Longer Working
May 02, 2012 06:05 AM|LINK
Hello,
Check if the default web site folder is correct. Also, how did you add the new site?
Regards
Free ASP.NET Examples and source code.
broonster27
5 Posts
Re: Default Web Site No Longer Working
May 02, 2012 09:18 PM|LINK
I'm not quite sure what you mean checking the folder is correct. Do you mean is it pointing to C:\inetpub\wwwroot? If so then yes it is. I can browse to the IIS7 default page fine, it's all the other sites and apps running under it that don't work.
The new site was added by a 3rd party. They did it manually by clicking "Add Web Site" and linking it to a directory on the server. They left the default binding as port 80, clicked OK and as soon as they did I saw the question mark appear on the Default Web Site.
broonster27
5 Posts
Re: Default Web Site No Longer Working
May 02, 2012 10:16 PM|LINK
Actually, after a reboot it's only the Terminal Services site/app RDWeb that's no longer working now. Still have the question mark though.
broonster27
5 Posts
Re: Default Web Site No Longer Working
May 02, 2012 10:59 PM|LINK
Fixed it. Looked at the site bindings for https and there was no certificate specified. I selected the certificate I installed from the drop-down and hey presto! it all works again.
Patrick1972
282 Posts
Re: Default Web Site No Longer Working
May 03, 2012 08:13 AM|LINK
Good to hear and thanks for sharing the resolution!! Please mark your question as solved.