Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have the need to receive requests for and on the same IIS webserver.

This webserver has two internal IP addresses which host each of these two subdomains.

Is anyone able to suggest how I might go about using the Cisco ASA 5505 I have implemented to redirect queries for each URL through to the corresponding private internal IP hosted on the web server?

Both websites are hosted on port 443 using the same digital (wildcard) certificate.

I am able to do this using host headers and updating the SecureBindings attribute in the metabase but this has killed off ActiveSync's ability to push emails.

share|improve this question

migrated from Jul 4 '11 at 7:53

This question came from our site for professional and enthusiast programmers.

You can't have two different secure (https) websites hosted on the same IP address.

I see you have addressed this on the webserver by having two internal IPs. However the traffic passing through the firewall will be encrypted, so the ASA can't read the host header, so can't redirect to the correct internal IP.

The simplest solution is to have two external IPs, each NATed to an internal IP on the webserver.

share|improve this answer
"You can't have two different secure (https) websites hosted on the same IP address." -- yes you can, it's called SNI, documented in RFC6066. – womble Jul 4 '11 at 8:48
@womble - in an ideal world, yes. But it's not exactly globally supported, hence SSL's "one-site-one-ip" rule still (sadly) exists: – Coops Jul 4 '11 at 8:56
You can host two https websites on the same IP address using IIS. Here is an example of how if anyone is interested:… – Lance Jul 5 '11 at 6:46
@Lance From your link: "But doing it this way requires that you always visit the site using the port number and always reference it in links with the port number". That sucks :-) – Coops Jul 5 '11 at 8:40
Coops - if your read the page the whole way down it is pointing out a failure of one approach (the one where you have to put the port number) and a way around it. I can access and no ports required. The next line after that quote states "There is a more elegant method, if you have IIS 6.0 or later. That method is to use SSL Host Headers". IE: You can have two hosts same external IP same port. I believe the failure of this issue is in adding host headers to the default website. – Lance Jul 5 '11 at 23:01

First of all - this is not something a Cisco ASA or NAT can solve for you.

I can see 3 potential solutions:

  1. Install a load balancer/frontend/proxy on your inside network on a different server, and re-route requests to the correct internal IP on the IIS based on the hostname requested
  2. Get another external IP and use port forwarding or one-to-one NAT to the secondary internal IP
  3. Re-configure your IIS to use a single IP (You're already using the same wildcard certificate)

EDIT: I wasn't aware of the SNI restrictions. I can't see any other solution than getting a second external IP

share|improve this answer
up vote 0 down vote accepted

ASA is not the answer for certain.

OK so the answer is that it can be done but no host headers on the default website. As it is the default website the traffic still flows there but headers on the other sites allow hosting them on the same IP. Host headers on default website breaks Exchange Active Sync.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.