Question

I am trying to set up an HTTPS site on IIS 7. I have added the certificate, set up the appropriate bindings and the site is accesible from within my company’s intranet, however no one from the outside internet can access it. I have a 1:1 NAT forward set up for port 443 that should route requests to the IP address for my server. I have the same situation for port 80 and don’t have any issues with http sites being accessible.

Any suggestions for what I might be missing here?

UPDATE:

As it turns out, the company that manages my company’s firewall had added the exception for https and 443, and the correct routing, but hadn’t added an exception for the process that handles https.

Answer 1

For starters, from outside, use telnet to see if you can even get to the port from outside:

telnet <host name or ip> 443

Note the space before the port.
If the telnet screen goes fully black, w cursor in top left, you can connect, so it is an iis issue.

If telnet just sits there, it is trying to connect but can’t. It may finally throw “connection refused” or “could not connect.” This means the problem is on the physical firewall (which needs the inbound path opened) or on the iis server itself (in its firewall or iis config)

In this case, next step:
Do the telnet operation on the IIS server itself, and from the same network as IIS (e.g. not through the firewall).

— If this works: The problem is the network firewall config

— If this does not work, you need to check the firewall on the IIS server itself (the windows firewall), and the IIS config itself

Note, on windows 7 and vista, telnet may not be present out of the box. Google how to enable it.