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 08:55:06 -0500


I don't think that's it, because when I do the same thing for the production
server (that is, browse the home page using a machine name or IP address) I
get exactly what you expect, that is, the certificate warning. I'm using
IE6. If I ignore the warning, I can continue browsing the site using HTTPS
as you would expect. You can try it yourself - the production site is
https://www.esimulation.com (works OK) and https://207.207.29.154 (gives
warning). I have it set up exactly the same on *.155 (as far as I can
tell), but I get a server error instead. I need to be able to point the
domain name at *.155, so I have to at least be able to get the cert warning.

I'm at a loss to why I'm getting 404-type error messages for https: when
everything seems to be configured correctly. The TechNet and MS articles
have been no help yet.

Thanks,
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: New Users (accounts) cant see/get to My Docs or Email
    ... certificate was listed as 'not to be trusted'. ... All SBS issued certificates are going to toss a warning. ... My Outlook can't conect to the server. ... Is there a recommended way to delete the Exchange user from the ...
    (microsoft.public.windows.server.sbs)
  • Re: Digital signature
    ... the user has set their 'macro' security level to High. ... set 'macro' security to Low will unsigned apps run without warning messages. ... GlobalSign digital certificate is a forgery and should be deleted without ... > server using Access 2003. ...
    (microsoft.public.access.developers.toolkitode)
  • Re: Suppressing mail server security certifcate warning
    ... Do you still think there is something that could inhibit the warning even ... using SSL and you could determine it with the actual server? ... a certificate. ... receive from Windows Live Mail every time I start the application, ...
    (microsoft.public.windows.vista.mail)
  • Re: Outlook RPC over HTTp deosnt work
    ... A red Address Bar and a certificate warning appear. ... Click the Certificate Error button to open the information window. ... when you try to use RPC over HTTP to connect the Exchange Server. ... we don't have to manually configure RPC over HTTP. ...
    (microsoft.public.windows.server.sbs)
  • Re: iis 6.0 on win 2003 certificate problem
    ... >I can create a certificate request. ... >but the problem is that the server is in production and it does not seem to ... You can make the request from another server then export the ...
    (microsoft.public.inetserver.iis)