SSL Problem

Hello. I have two separate Web sites running on one IIS server. We'll call
them server A and server B.

I purchased a verisign certificate for server A some time ago and it's been
fine. I just purchased one for server B and set it up on server B. I was
careful to use the fully qualified domain name (b.domainname.com) during the
process.

However, when I browse to server B using https, it prompts me with a warning
that I'm using the certificate from server A. If I click the view
certificate, it says I'm using server A certificate.

Any idea what's wrong? I don't believe that I pointed to the wrong .cer file
when I installed the certificate.

Thoughts on how to fix this? I don't have any idea as to where to go from
here.

Thanks
Doug

Re: SSL Problem

One more piece of information. If I go into the MMC for server B, and click
on View Certificate, it says, "Issued to: b.domainname.com".

But why are requests for that site looking at server A certificate?

Thank you!


"Doug" wrote in message
news:ircXg.21829$Ij.10409@newssvr14.news.prodigy.com...
> Hello. I have two separate Web sites running on one IIS server. We'll call
> them server A and server B.
>
> I purchased a verisign certificate for server A some time ago and it's
> been fine. I just purchased one for server B and set it up on server B. I
> was careful to use the fully qualified domain name (b.domainname.com)
> during the process.
>
> However, when I browse to server B using https, it prompts me with a
> warning that I'm using the certificate from server A. If I click the view
> certificate, it says I'm using server A certificate.
>
> Any idea what's wrong? I don't believe that I pointed to the wrong .cer
> file when I installed the certificate.
>
> Thoughts on how to fix this? I don't have any idea as to where to go from
> here.
>
> Thanks
> Doug
>
>
>

Re: SSL Problem

These are separate physical servers?

Or two separate virtual servers? (If yes on this, you need a separate IP
for each virtual web with a cert on it. Did you do that yet?)

"Doug" wrote in message
news:zucXg.21832$Ij.15915@newssvr14.news.prodigy.com...
> One more piece of information. If I go into the MMC for server B, and
> click on View Certificate, it says, "Issued to: b.domainname.com".
>
> But why are requests for that site looking at server A certificate?
>
> Thank you!
>
>
> "Doug" wrote in message
> news:ircXg.21829$Ij.10409@newssvr14.news.prodigy.com...
>> Hello. I have two separate Web sites running on one IIS server. We'll
>> call them server A and server B.
>>
>> I purchased a verisign certificate for server A some time ago and it's
>> been fine. I just purchased one for server B and set it up on server B. I
>> was careful to use the fully qualified domain name (b.domainname.com)
>> during the process.
>>
>> However, when I browse to server B using https, it prompts me with a
>> warning that I'm using the certificate from server A. If I click the view
>> certificate, it says I'm using server A certificate.
>>
>> Any idea what's wrong? I don't believe that I pointed to the wrong .cer
>> file when I installed the certificate.
>>
>> Thoughts on how to fix this? I don't have any idea as to where to go from
>> here.
>>
>> Thanks
>> Doug
>>
>>
>>
>
>