Hmm, from your description you have the correct configuation and a good idea
how this should be set up.
A couple things to check:
- what does the properties of each site say in the GUI? (You shouldn't need
to mess with the metabase to do what you are doing, why did you do that?)
- Is either of the sites, or the default site have "All unassigned" active?
If yes, either change it or just stop that site.
- Does "443" appear on the main page (NOT the properties window) of the host
headers area for "SSL port"?
- Do both sites work OK with port 80? (Http?) From an outside machine, do
both sites ping to the proper IPs? (IP "a" and IP "b")
- Do you have a router or firewall doing address translation?
- Go into the "Security" tab, then in the Certificate assignment, you should
be able to view and re-assign what cert to use in there. Does it have the
correct one? (If yes, try just re-assigning it)
I might try a reboot too...
<gointern DeleteThis @gmail.com> wrote in message
news:1192608866.256124.190740@i13g2000prf.googlegroups.com...
> Hello, could somebody help me out with my problem?
>
> I have a dedicated server. Hosting one website. In IIS I have created
> two websites named www.domainname.com and domainname.com. Two
> different IPs, different host headers, same ports. I assigned a SSL
> certificate for each of them accordingly. There are two certificates
> www.domainname.com and domainname.com (I cannot get a wildcard
> certificate). The problem I am having is that there is a certificate
> mismatch if I access the site by domainname.com. The certificate shows
> up as www.domainname.com. I rechecked if the certificate was correct
> for each website. What am I doing wrong? Is there a better way to go
> about this? Could anybody advise me on how to solve this?
>
> IIS
> 215.215.215.215:80:www.domainname.com
> 215.215.215.216:80:domainname.com
>
> I changed SSL host headers in IIS metabase:
> 443:www.domainname.com
> 443:domainname.com
>
FAQ
Profile
Private Messages
Log in
