SSL works internally but not externally

We've installed an SSL certificate and it works fine internally but
not externally. We host our own site so if I type https://servername
the site will pull up. When we switch to external, https://www.sitename.com
just hangs and nothing pulls up and no errors. In mmc, i can look at
the snap-in for the certificate and it has the correct external domain
name. Don't know what to do. Can anyone help?

Thanks,

Matt

Re: SSL works internally but not externally

On Sep 14, 11:54 am, MattM wrote:
> We've installed an SSL certificate and it works fine internally but
> not externally. We host our own site so if I typehttps://servername
> the site will pull up. When we switch to external,https://www.sitename.com
> just hangs and nothing pulls up and no errors. In mmc, i can look at
> the snap-in for the certificate and it has the correct external domain
> name. Don't know what to do. Can anyone help?
>
> Thanks,
>
> Matt



If it works internally and externally, then the problem is not with
IIS but with your network configuration outside of the IIS server
itself.

You will have to perfectly configure networking to route external
traffic to https://www.sitename.com to your internal website in order
to have request to https://www.sitename.com work. https://servername
works through magic that is not available on the general Internet --
now you know.

Plenty of external documents/HOWTO show how this is done. Please
search for them. The answer likely has nothing to do with any
configuration on your IIS server.

For example, you have to verify that:
1. www.sitename.com routes to your external IP in DNS
2. Port 443 is not blocked by the ISP where you host the IIS server
3. Your NAT/Router forwards requests from the external IP to internal
IP
4. Firewall on your IIS Server allows traffic on the internal IP and
Port
5. IIS has Website binding to that internal IP and Port

Basically, you have to make sure every bit of networking is perfectly
configured, or else the symptoms look like "website is not available".
And obviously, "website is not available" hardly means the issue has
anything to do with the web server...


//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//