Configuring SSL Host Headers in IIS 6 W2K3 SP1

Hi,

I can't quite figure out why I am having such a hard time with this. I got
it to work ONCE on about the 4th attempt, left it alone overnight and checked
that it was still working in the morning, but then it stopped working when I
attempted to add a third site and I haven't been able to duplicate it at all
since, even with changing IP addresses, host headers, everything. Any ideas?

I'm trying to follow
http://www.microsoft.com/technet/prodtechnol/WindowsServer20 03/Library/IIS/596b9108-b1a7-494d-885d-f8941b07554c.mspx?mfr =true

After I enable the SecureBindings on my two sites, SSL just stops working.
Trying to go to either site via https just immediately fails with a "Page not
Found" error in I.E. (Firefox gives a Page was Interrupted message) . In
each case, the browser pauses while it asks if I want to accept the
self-signed cert so I know it is getting to port 443 via the host headers in
DNS). Has anyone been able to make this work reliably? The machine is W2K3
SP1 and I am using a self-signed wildcard cert for testing. My CNAME records
are in DNS and working. I know the wildcard cert is working because after I
install it on the first site, SSL works. It's just after installing it on
the second site and doing the rest of the steps in the document that both
stop working.

I did find one response on a newsgroup that suggested using
"xxx.xxx.xxx.xxx:443:site1.domain.com" instead of just
":443:site1.domain.com" but this didn't seem to work either. I got the same
results.

I know I am probably just missing something simple, but it is not jumping
out at me. Any ideas? Thanks.

Ryan

Re: Configuring SSL Host Headers in IIS 6 W2K3 SP1

My previous test work with ip.ip.ip.ip:443:a.aa.com. after you configure
the securebindings, try restart https and iis admin services.

--
Regards,
Bernard Cheah
http://www.iis.net/
http://www.iis-resources.com/
http://msmvps.com/blogs/bernard/


"Ryan" wrote in message
news:827AE134-DDC8-40C9-9477-12CA1E9B5883@microsoft.com...
> Hi,
>
> I can't quite figure out why I am having such a hard time with this. I
> got
> it to work ONCE on about the 4th attempt, left it alone overnight and
> checked
> that it was still working in the morning, but then it stopped working when
> I
> attempted to add a third site and I haven't been able to duplicate it at
> all
> since, even with changing IP addresses, host headers, everything. Any
> ideas?
>
> I'm trying to follow
> http://www.microsoft.com/technet/prodtechnol/WindowsServer20 03/Library/IIS/596b9108-b1a7-494d-885d-f8941b07554c.mspx?mfr =true
>
> After I enable the SecureBindings on my two sites, SSL just stops working.
> Trying to go to either site via https just immediately fails with a "Page
> not
> Found" error in I.E. (Firefox gives a Page was Interrupted message) . In
> each case, the browser pauses while it asks if I want to accept the
> self-signed cert so I know it is getting to port 443 via the host headers
> in
> DNS). Has anyone been able to make this work reliably? The machine is
> W2K3
> SP1 and I am using a self-signed wildcard cert for testing. My CNAME
> records
> are in DNS and working. I know the wildcard cert is working because after
> I
> install it on the first site, SSL works. It's just after installing it on
> the second site and doing the rest of the steps in the document that both
> stop working.
>
> I did find one response on a newsgroup that suggested using
> "xxx.xxx.xxx.xxx:443:site1.domain.com" instead of just
> ":443:site1.domain.com" but this didn't seem to work either. I got the
> same
> results.
>
> I know I am probably just missing something simple, but it is not jumping
> out at me. Any ideas? Thanks.
>
> Ryan