The sharing of port 80 isn't the issue. It's more likely that the new web site has specified a host header in its configuration with the same name as the DNS name of the server, i.e. myserver1.domain.com. With a host header in place, it will be "stealing" your original traffic which would have otherwise gone to the default web site. You can verify this behaviour in one of two ways (or both): Check the log file for the new web site. You'll probably find your client requests for the RDP web directory and user application in this location rather than in the log files for the default web site.Open up IIS Manager, right-click on the new web site and choose "Bindings" and check whether it has provided a value for "Host Name". If it has - and I expect it has, then that's your problem right there. If it is the host name issue, then you're going to have to look at working with CNAMEs to resolve this issue, as each web site needs its own host name value to avoid this kind of conflict unless it's on a different port. For clarity, it's better practice to use different host names than different ports. Users don't copy well (or almost at all, I'd say) with having to specify full URLs with the http prefix and a port suffix. It just gets ugly fast. Cheers, Lain It was actually the certificate in the bindings. After the new site was created there wasn't one specified for the default web site. I updated the certificate on the bindings all was fine.Hibs Ya Bass!

Can't find an IIS 7.5 forum so I'll post here. 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. Hibs Ya Bass!

IIS forums are here. http://forums.iis.net/ Regards, Dave Patrick .... Microsoft Certified Professional Microsoft MVP [Windows] Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

The sharing of port 80 isn't the issue. It's more likely that the new web site has specified a host header in its configuration with the same name as the DNS name of the server, i.e. myserver1.domain.com. With a host header in place, it will be "stealing" your original traffic which would have otherwise gone to the default web site. You can verify this behaviour in one of two ways (or both): Check the log file for the new web site. You'll probably find your client requests for the RDP web directory and user application in this location rather than in the log files for the default web site.Open up IIS Manager, right-click on the new web site and choose "Bindings" and check whether it has provided a value for "Host Name". If it has - and I expect it has, then that's your problem right there. If it is the host name issue, then you're going to have to look at working with CNAMEs to resolve this issue, as each web site needs its own host name value to avoid this kind of conflict unless it's on a different port. For clarity, it's better practice to use different host names than different ports. Users don't copy well (or almost at all, I'd say) with having to specify full URLs with the http prefix and a port suffix. It just gets ugly fast. Cheers, Lain