SSL on multiple sites on same IIS server

I'm trying to configure SSL on multiple sites on the same server.  By default they all try to use port 443 as the SSL port and when I try to go to any of the sites using the https url I'm directed to the first site that I added SSL to no the server.  How can I accomplish this?  Do I have to enable other ports on the firewall and use those?  Is there a way to do this in the host headers?  Do I have to assign different IPs to the SSL sites?  Any help would be greatly appreciated.
LVL 3
smueller72Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

gidds99Commented:
Yes you need different ip's for each site:

http://www.winnetmag.com/Web/Article/ArticleID/21205/Web_21205.html
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
jimcplCommented:
smueller,

I'm assuming that this is with IIS and a Windows Server?

First of all, host headers don't work with SSL.

Assuming that that this is a server, you have (at least) 2 choices:

1) You can assign more than 1 IP address to the NIC (go to Network, TCP/IP Properties, then click on Advanced, then add your IP addresses).  Then, in the IIS manager, "bind" each website to one of the IP addresses.  OR...

2) You can assign a different port # for the SSL port for each website.  If you took this approach, and, say, assigned ports 4430 and 4431 for two different websites, this would mean that the URLs for the sites would be, for example, https://mysite.com:4430, https:/mysite.com:4431, etc.

BTW, option #1 can only be done with Windows Servers (e.g., Windows 2000 Server, but not Windows 2000 Pro).

Jim
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
OS Security

From novice to tech pro — start learning today.

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.