> Hi,
>
> I just installed an SSL Cert issued  by Thawte to a web site in IIS, which
> was created by SharePoint.
>
> For some reason, I can get to this via http, but get: (INVALID HOSTNAME) in
> IE6, and
> "There is a problem with this website's security certificate.
>
>  The security certificate presented by this website was issued for a
> different website's address.
>
> Security certificate problems may indicate an attempt to fool you or
> intercept any data you send to the server.  " in IE7.
>
> Any ideas what is up with this?  I followed to a T,  the instructions for
> installing the cert.
>
> Thanks.
>
> --
> David

"David Wang" wrote:

> On Apr 15, 1:14 pm, David <Da***@discussions.microsoft.com> wrote:
> > Hi,
> >
> > I just installed an SSL Cert issued  by Thawte to a web site in IIS, which
> > was created by SharePoint.
> >
> > For some reason, I can get to this via http, but get: (INVALID HOSTNAME) in
> > IE6, and
> > "There is a problem with this website's security certificate.
> >
> >  The security certificate presented by this website was issued for a
> > different website's address.
> >
> > Security certificate problems may indicate an attempt to fool you or
> > intercept any data you send to the server.  " in IE7.
> >
> > Any ideas what is up with this?  I followed to a T,  the instructions for
> > installing the cert.
> >
> > Thanks.
> >
> > --
> > David
>
>
> What certificate did IE6/IE7 get from the server?
>
> Setting up certificates for SSL on IIS is pretty easy - import the
> certificate and bind it to a website.
>
> Your issue sounds like networking misconfiguration/confusion, but
> we'll have to step-by-step figure out what your configuration is.
>
> For example, you need to provide the HTTPS hostname you typed into the
> browser URL Address Bar, as well as the Certificate Subject returned
> by IE6/IE7 for the server certificate that is "not trusted". Your
> error says that the hostname does not match the Certificate Subject.
> Assuming you got the right certificate/subject from Thawte and put the
> right hostname in IE, such mismatch indicates some other network
> configuration that is terminating the SSL endpoint before it reaches
> IIS, which would be a networking misconfiguration issue -- even if you
> only notice it by trying to contact the web server -- because the
> issue has nothing to do with the web server.
>
>
> //David
> http://w3-4u.blogspot.com
> http://blogs.msdn.com/David.Wang
> //
>