• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 303
  • Last Modified:

How to get multiple SSL sites working on IIS5 with NLB.

I am running 2 x Win2k Adv. Servers with NLB. I have multiple sites on the servers, most sharing an IP address.
I now need a few of those sites to use SSL, so I have got SSL certs from VeriSign, and moved those sites to a unique IP address.

However, I have NAT going on in the firewall, which points the external IP addresses to a single NLB IP address inside. I think however, that IIS may want the SSL sites to have a unique internal IP address as well, I'm not sure.
When I enable SSL for a site, it only works if I get it to use the (All Unassaigned) IP address. After that, all SSL traffic for all sites ends up at the one that catches the Unassagined IP's.
Assigning SSL to it's unique external IP address doesn't seem to do the trick, prob. because the external IP address is now only available in the hostname, which is encrypted in SSL, and unavailable?

I think the solution lies in mapping the unique external IP's to unique internal IP's. Unfortunately, there is only 1 NLB IP address, so unless I can add more, I don't know what to do.

Anyone know how to get around this?
0
roddy
Asked:
roddy
1 Solution
 
dredgeCommented:
listening.
0
 
TTomCommented:
Can you map the (many) external IP addresses to the (single) internal IP address, but using different ports and configure IIS for each of the sites to use the same IP address, but a different port?

(Not sure I really understand the problem, so this may be off base.)

Tom
0
 
dredgeCommented:
perhaps when the internal user wants to log onto the secure port, you'll simply have to send them through your firewall and allow them to point at the public IP address.
0
Introducing Cloud Class® training courses

Tech changes fast. You can learn faster. That’s why we’re bringing professional training courses to Experts Exchange. With a subscription, you can access all the Cloud Class® courses to expand your education, prep for certifications, and get top-notch instructions.

 
meverestCommented:
SSL requires a unique IP address/port because the protocol does not support http1.1-like hostname headers to identify the virtual host.

now if you are using a port map on the NAT router, then you can only have one address per port, so to get multiple ssl sites working on your internal web server, you have two options:

1. use a different port for each virtual server, and then set up additional port-to-internal-address maps on the NAT, eg,
assuming your NAT router address is 1.2.3.4 and the internal web server is 192.168.1.1, add these maps:

1.2.3.4 port 443 -> 192.168.1.1 port 443
1.2.3.4 port 1443 -> 192.168.1.1 port 1443
1.2.3.4 port 2443 -> 192.168.1.1 port 2443

2.  set up the NAT with multiple public addresses, and map port 443 to multiple virtual servers on the internal; network, eg:

assuming your NAT router address has 1.2.3.4, 1.2.3.5, and 1.2.3.6 and the internal web server has 3 virtual servers mapped to 192.168.1.1, 192.168.1.2, 192.168.1.3, add these maps:

1.2.3.4 port 443 -> 192.168.1.1 port 443
1.2.3.5 port 443 -> 192.168.1.2 port 443
1.2.3.6 port 443 -> 192.168.1.3 port 443

your main problem is to get access to additional address space, or you will need to use different ports, so that when accessing, it will look like this in the browser:

https://server1.domain.com
https://server2.domain.com:1443
https://server3.domain.com:2443

etc.

cheers.


 
0
 
roddyAuthor Commented:
I'm going to try using different ports for each external IP address. Just looking at this idea makes me very confident it will work.
IIS actually seems designed with this in mind, now that I look at it this way. Specifying your secure port is very easy.

This will take me a few hours to implement, so points will be given afterwards.

TTom got in first with this answer, and while meverest gave a very complete answer, it wasn't exactly what I wanted. These are the mappings that TTom had in mind, and is what I'll be trying.

1.2.3.4 port 443 -> 192.168.1.1 port 443
1.2.3.5 port 443 -> 192.168.1.1 port 1443
1.2.3.6 port 443 -> 192.168.1.1 port 2443
0
 
roddyAuthor Commented:
Yep, this is working fine. I just feel stupid I didn't think of it myself...

Anyway, thanks for your help. Sorry for the delay in giving points.

Rod
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now