Problems with IIS6 & 2 SSL certs on one site

I'm moving from a wild card cert and am having some issues.

Previously I had my server set up like so

www.site.foo
admin.site.foo
resources.site.foo

I now have 2 EV certs (for www & resources) and a regular cert (for admin)

I've imported the certs into cert store and installed them on each site.
I've changed the sites to my new IP's and have them all set up to use 443.
I've viewed the certs in IIS and they are apparently correct
I've removed the old wildcard cert from the cert store
I've restarted IIS and each of the sites
I've run SSL diags and the sites look correct

All media & scripts from resources.site.foo load fine when browsing on www.site.foo port 80

But when I browse to a secure part of www.site.foo which has content from resources.site.foo

I get a connection rest error (shows aborted in firebug)

When I try to view any media over SSL i get the following.

resources.site.foo uses an invalid security certificate.
The certificate is only valid for www.site.foo

(this would be the reason for the aborted I'm sure)

So for some reason the certs are not working as expected. Why is IIS loading the cert for www when it should load the resources cert?




 the admin site works fine
LVL 36
SidFishesAsked:
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.

AnuroopsunddCommented:
seems your certificate binding is not done correctly.

http://www.digicert.com/ssl-support/configure-iis-host-headers.htm
0
AnuroopsunddCommented:
To configure the SecureBindings metabase property for SSL host headers
1. Click Start, click Run, type
cmd
in the Open box, and then click OK.
 
2.  Type the following command at the command prompt:

cscript.exe adsutil.vbs set /w3svc/<site identifier>/SecureBindings ":443:<host header>"

where host header is the host header for the Web site, for example, site2.contoso.com or site4.contoso.com.
 


http://www.microsoft.com/technet/prodtechnol/WindowsServer2003/Library/IIS/8d9f2a8f-cd23-448c-b2c7-f4e87b9e2d2c.mspx?mfr=true
0
SidFishesAuthor Commented:
got it fixed

I'd actually done that (but did it again and that fixed the connection reset - but only after i shut down all sites and restarted them)

The other thing I hadn't done was to point the website 443 port to the correct IP

A bit more info from SSL Diag pointed me  in the right direction

When I refreshed the view i get


[ W3SVC/1834383756 ]
ServerComment = resources.site.foo
ServerAutoStart = True
ServerState = Server started
#Impersonated server account
SSLCertHash = XXXXXXXXXXX
SSLStoreName = XX
#CertName = resources.site.foo

However when I click on #CertName = resources.site.foo and do an SSL Probe I get the following


System time: Mon, 09 Apr 2012 18:42:42 GMT
Connecting to 64.34.106.3:443
Connected
Handshake: 51 bytes sent
Handshake: 5121 bytes received
Handshake: 566 bytes sent
Handshake: 43 bytes received
Handshake succeeded
Verifying server certificate, it might take a while...
Server certificate name: www.site.foo

So while it showed correct, when I run the probe it pointed to the wrong cert.

Going back into inetmgr I had a look at the IP settings and what I had forgotten to do was go into Advanced and change the settings to 443 -  it was using the default IP address in the Multiple SSL identities box.

So I changed that to point to the sites new IP (same as on 80), stopped all the site, reran the binding and I'm back in business
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
SidFishesAuthor Commented:
site binding was only part of the problem. The forgetting to change the SSL IP was the real root. Splitting points for the help.
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
Microsoft IIS Web Server

From novice to tech pro — start learning today.