Re: IIS SSL Config - 404 Error

From: Chris V (chris_velazquez@hotmail.com)
Date: 09/11/02


From: "Chris V" <chris_velazquez@hotmail.com>
Date: Wed, 11 Sep 2002 09:50:12 -0500


OK, I figured it out. I was creating a .CER file from the *.154 computer,
exporting it and importing it to the *.155 computer. That didn't work, and
I got the 404 error. Instead, I exported the certificate with the private
key as a .PFX file, then loaded that file into the *.155 certificate store.
When I installed that certificate on the web server it worked just great,
first try.

Chris

"JC" <johncleveland@hotmail.com> wrote in message
news:db7d01c25940$e75ee490$37ef2ecf@TKMSFTNGXA13...
> Your problem is with a certificate mismatch error not
> being handled by the client browser properly.
>
> The SSL cert is issued for a common name that is the
> site's URL (iw www.yoursite.com) but you are browsing to
> 207.207.29.155. The two don't match and this causes an
> error.
>
> What you SHOULD get is a certificate warning saying the
> certificate is valid but the name doesn't match. What I've
> found though ie IE5.5 pre SP2 (especially on an NT4 OS)
> does not handle this correctly and just displays a 404.
> Solution is to upgrade to IE6 or IE5.5sp2 with the latest
> patches. An alternative is to add a host file entry in
> your PC that resolves www.yousite.com to 207.207.29.155 so
> you can browse to the test site using the valid URL.
>
> JC
>
> >-----Original Message-----
> >OK, here is one for ya...
> >
> >I installed the SSL certificate from Verisign, but I get
> a 404 error when I try to access the website using
> https://207.207.29.155 , even though I can access the site
> fine using plain old http://207.207.29.155 .. I'm not
> sure what the problem is. The port is set up correctly on
> 443. I did this on our production server and it worked OK.
> >
> >I tried restarting IIS, dblchecked the config, the SSL
> certificate is good, it looks OK.
> >
> >
> >
> >In the secure communications dialog, there is nothing
> checked, and we ignore client certificates.
> >
> >



Relevant Pages

  • Re: Removing certificates on MS Windows.
    ... <MIG> ... Simply exporting does not affect the certificate or linked key. ... Default behaviour should have been to remove linked private key also. ...
    (microsoft.public.platformsdk.security)
  • Re: Exporting/ importing certificates
    ... Are you just exporting the public certificate, ... You should be able to export any public certificate from your Windows ... "Certificate Stores" via IE Windows certs panels. ...
    (microsoft.public.security)
  • Re: Removing certificates on MS Windows.
    ... On Mon, 10 Apr 2006, Mitch Gallant wrote: ... Simply exporting does not affect the certificate or linked key. ... RSA keypairs, so you should definitely NOT blanket nuke them all :-) ...
    (microsoft.public.platformsdk.security)
  • Re: Can exchange key pair be exported and used on another machine?
    ... Specifying CRYPT_EXPORTABLE when generating the key and then exporting the ... Did you specify the flag CRYPT_EXPORTABLE when you first generated the key ... PRIVATEKEYBLOB as dwBlobType. ... must create a certificate associated with this key pair (the certificate ...
    (microsoft.public.platformsdk.security)
  • IIS SSL Config - 404 Error
    ... The SSL cert is issued for a common name that is the ... What you SHOULD get is a certificate warning saying the ... you can browse to the test site using the valid URL. ...
    (microsoft.public.inetserver.iis.security)