Re: multiple certificates
From: Stephen L Nicoud (firstname.lastname@example.org)
From: "Stephen L Nicoud" <email@example.com> Date: Tue, 11 Mar 2003 18:11:00 -0500
For the site with SSL on port 444 are you accessing this way:
You have to add the port number if you are using anything other than the default of 443.
Since most folks (users, developers and admins) don't like to do that most administrators just set up each SSL site with its own unique IP address and let the default port of 443 govern.
"Sam" <firstname.lastname@example.org***> wrote in message news:email@example.com...
> Hi BB.
> Your analysis is correct.
> The certificate you get accessing the second site is from
> the first site.
> There are 2 certificates installed in the different sites
> in IIS, I changed the IP address in proporties of each
> site from <all unassigned> to the actual IP address and
> changed the SSL port for secure to 444 (the first site is
> defaulted on 443).
> After restarting the websites the problem stayed the same.
> I restarted IIS and the problem stays the same!
> I have a feeling that somehow the first certificate is
> taking priority....
> Please help me again!
> >-----Original Message-----
> >When you deploy second cert, is it binding on
> >difffernt IP or ports ?
> >the reason you get those prompt, because the
> >url and the cert common name not matching.
> >click to view what cert was retrieve and
> >company with the url you visiting.
> >I suspect that you accessing the 2nd sites
> >but the 1st cert was retrieved.
> >to solve this, ensure you running 2 certs
> >either on same IP diff ports or 2 different
> >IPs. SSL default port is 443.
> >"Sam" <firstname.lastname@example.org****> wrote in message
> >> Hi,
> >> We run a webservers with IIS 5 and are hosting various
> >> domains. For one customer I installed a 40 bits Verisign
> >> certificate (1024) and that worked OK.
> >> I installed another certificate for a new site and ran a
> >> test by putting a simple default.htm in the secure
> >> directory and tried to access it.
> >> Imagine my surprise when I got a warning that the name
> >> not match the website and was redirected to the secure
> >> section of the first site. I checked the certificate at
> >> the warning and it was the certificate for the first
> >> The certificates are installed in two different webs and
> >> have a different folder structure.
> >> Anyone saw this before? KB, Technet and Verisign do not
> >> give me any hints!
> >> Thanks and regards,
> >> Sam