Discussion Locked

Dual SSL on IIS4.0

0 helpful
6 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Anyone knows what options are there to have 2 SSL certs running on IIS 4.0? Have anyone tried before? I was thinking of an additional nic.
Not moving yet (sigh) to W2K & IIS 5.0.

6 replies

by joseph moore

From what I can find on Technet, IIS4 can work with multiple certificates on the same server, providing you are running at least Service Pack 4. Schannel.dll (the file that handles certificates in IIS) does not work with multiple certs if you are SP3 or lower.
And there are other certificate errors all the way up to SP6a, so I suggest that you run this last Service Pack for NT4 (SP6a) just to be safe. Otherwise, you should be fine.

hope this helps

by ah beng

Hi Joseph, Thanks for the answer but it did not really help.
More info is that to have 2 ssl running you will need 2 separate ips for the web sites i.e 2 nics.
But the server i have, did not have any more free slots, so i am unable to add another nic to it.
Say do u know if NT4 supports virtual ip addressing?

by jim p. barber

The answer to you question really depends on how you wish to implement it. There are two basic methods of doing it, the simple and the hard. These are listed below.

The easiest way is just to add another IP address to you nic card. Multiple bindings on a single card are simple. I have implemented this many times and it works well, and have hosted over 30 certificates on the same server. Once you have added the IP address to the card you will need to bind the certificate to that IP addressand port. You will then need to set up the virtual server to answer requests for the new IP address only. You will also need to set up the existing site that answers to your current requests as static, not the default of any.

This will work even with a single site is answering multiple IP addreses. You will just need to set the server to answer for both ip addresses on port 443, I have also done it this way, but it is a pain. The best way is to use multiple virtual server, though not a requirement.

The more complicated way is to use the advanced button on the ip page to enter the IP address and host header bindings. You will have to set the ip address you currenly have to answer requests on a separate port for ssl. I. E. 192.168.254.100:444, then you would have to bind the certificate to the same IP address and the new port. The problem with this is that you will have to direct people to the port in any links you may have that will use that port. I. E. https://www.somedomain.com:444/yourpage.htm. This of course is the least preffered method.

You can email me for more detailed instructions, on how to do this if you are unsure.

by ah beng

Hi Jim, Sorry for the long silence in between. Was caught up with alot of backlog stuff to clear. Will email u and discuss more with u on this subject.
Thanks for the help.

This discussion is closed to new replies.