I'm running server 2003 with IIS. The server has multiple sites, each using host headers. Two of the sites have SSL enabled, one using the default port and another using a custom port. When attempting to connect to the site using the custom port if I do not explicitly use the FQDN, ie just "sitename:port" it loads fine. If I use the FQDN, ie "sitename.domain.domain:port" it does not load and gives no specific error message, stating only that IE cannot display the page. The host header of the site is "sitename.domain.domain" and works on port 80 and http just fine. http://sitename does not work and gives http 400. Pinging the site with either "sitename" or "sitename.domain.domain" results in the same IP responding, and when pinging "sitename" it automatically apends ".domain.domain" so gives the impression that it is connecting to the same thing in both cases. So why does specifying the port connect properly when just using "sitename:port" but fail when specifing the fqdn and port "sitename.domain.domain:port", and how do I get it to respond when the fqdn and port are specified?

Hello, for IIS related questions better use the IIS forum: http://forums.iis.net/Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.