| Ken Schaefer 2004-09-22, 9:26 pm |
| Suggest you run SSLDiag:
http://www.microsoft.com/downloads/...&displaylang=en
to see if there are any issues with the certificate and SSL generally on the
server.
When you say "it just acts like the site doesn't exist" could you be a
little more precise please? That description is not very helpful. What are
you doing and from where, what exactly happens, and what exactly do you see?
Since there are a fair few pieces of the puzzle that need to fit together to
get SSL working, we need to know what things we can cross off. For an
overview of how SSL works:
http://support.microsoft.com/defaul...kb;EN-US;257591
Description of the Secure Sockets Layer (SSL) Handshake
http://support.microsoft.com/defaul...kb;EN-US;257587
Description of the Server Authentication Process During the SSL Handshake
http://support.microsoft.com/defaul...kb;EN-US;257586
Description of the Client Authentication Process During the SSL Handshake
Cheers
Ken
"Ed" <Ed@discussions.microsoft.com> wrote in message
news:54DB5F22-D5D5-4A84-B3B9-456851666C41@microsoft.com...
>I have an exchange server which is running Enterprise Exchange 2003 and
>it's
> sitting a 2003 standard server with some very good hardware below that.
> Exchange works great and life is good. But I want to deploy the OWA and
> OMA
> features of the new Exchange server. Before opening up the firewall I
> want
> SSL in place. I have a CA on the network and I requested and installed a
> web
> cert for the website. I tested the cert and life was good for about a
> day.
> Then the https: stopped working. if I don't require ssl then I can use
> http:
> but if I try to come in https: it just acts like the site doesn't exist.
> I
> have looked at the cert and I don't see a problem.
> Any Suggestions will be welcomed.
> Ed
|