"Tas" <tas***@gmail.com> wrote in message
news:1163718099.006600.99220@h54g2000cwb.googlegroups.com...
>I just purchased and setup an SSL certificate for an MS OWA server.
> The certificate works great for me from multiple computers I have
> tested it on.  I can go to the secure page with no errors or pop-ups at
> all.
>
> But, a client who is trying to access OWA gets this error: Security
> Alert: The Name of the Security Certificate Is Invalid or Does Not
> Match the Name of the Site
>
> Here's the strange part.  When he views the certificate, it's not the
> certificate I installed at all!!  It's for a different domain
> completely, one I've never heard of before: www.lbow.com
> Of course the name doesn't match, it's not the correct certificate!
>
>
> It seems his IE is trying to use some other certificate it has
> somewhere.  Does anyone know why/how this could happen?? Any way to
> "clear" the certificate information in IE?  I've tried clearing the
> cookies and files, but didn't help.
>

> Mmm.. funny. Is the client really browsing your site?
> have you test it locally and it is working at local site at least?
>
>
> --
> Regards,
> Bernard Cheah
> http://www.iis.net/
> http://www.iis-resources.com/
> http://msmvps.com/blogs/bernard/
>
>
> "Tas" <tas***@gmail.com> wrote in message
> news:1163718099.006600.99220@h54g2000cwb.googlegroups.com...
> >I just purchased and setup an SSL certificate for an MS OWA server.
> > The certificate works great for me from multiple computers I have
> > tested it on.  I can go to the secure page with no errors or pop-ups at
> > all.
> >
> > But, a client who is trying to access OWA gets this error: Security
> > Alert: The Name of the Security Certificate Is Invalid or Does Not
> > Match the Name of the Site
> >
> > Here's the strange part.  When he views the certificate, it's not the
> > certificate I installed at all!!  It's for a different domain
> > completely, one I've never heard of before: www.lbow.com
> > Of course the name doesn't match, it's not the correct certificate!
> >
> >
> > It seems his IE is trying to use some other certificate it has
> > somewhere.  Does anyone know why/how this could happen?? Any way to
> > "clear" the certificate information in IE?  I've tried clearing the
> > cookies and files, but didn't help.
> >

"Tas" <tas***@gmail.com> wrote in message
news:1163772585.730443.141350@k70g2000cwa.googlegroups.com...
> Thanks for your reply, Bernard, but we got it figured out.  The client
> was typing in the URL incorrectly.  He was putting in
> "https://www.domain.com/exchange" instead of
> "https://mail.domain.com/exchange".  I'm still unsure why that other
> certificate was coming up on our domain, but it doesn't matter now.
>
> Thanks!!
>
>
> Bernard Cheah [MVP] wrote:
>> Mmm.. funny. Is the client really browsing your site?
>> have you test it locally and it is working at local site at least?
>>
>>
>> --
>> Regards,
>> Bernard Cheah
>> http://www.iis.net/
>> http://www.iis-resources.com/
>> http://msmvps.com/blogs/bernard/
>>
>>
>> "Tas" <tas***@gmail.com> wrote in message
>> news:1163718099.006600.99220@h54g2000cwb.googlegroups.com...
>> >I just purchased and setup an SSL certificate for an MS OWA server.
>> > The certificate works great for me from multiple computers I have
>> > tested it on.  I can go to the secure page with no errors or pop-ups at
>> > all.
>> >
>> > But, a client who is trying to access OWA gets this error: Security
>> > Alert: The Name of the Security Certificate Is Invalid or Does Not
>> > Match the Name of the Site
>> >
>> > Here's the strange part.  When he views the certificate, it's not the
>> > certificate I installed at all!!  It's for a different domain
>> > completely, one I've never heard of before: www.lbow.com
>> > Of course the name doesn't match, it's not the correct certificate!
>> >
>> >
>> > It seems his IE is trying to use some other certificate it has
>> > somewhere.  Does anyone know why/how this could happen?? Any way to
>> > "clear" the certificate information in IE?  I've tried clearing the
>> > cookies and files, but didn't help.
>> >
>