I have two servers. One runs Exchange 2003, and the other host the IIS website. When I type www.domain.org, It goes to the website. When I type www.domain.org/exchange, it goes to OWA. I went through the steps to enable OWA 2003 using our own Certificate Authority. I configured the certificate authority on the Exchange server. But when I try to access the website or the OWA site, using https://www.domain.org or https://www.domain.org/exchange, it will not let me through. Do I have to setup SSL on the server that is the default IIS server as well? One more thing, typing http://mail.domain.org takes me to the default website. Darrell
Hi, Follow this: http://www.msexchange.org/tutorials/SSL_Enabling_OWA_2003.html Oliver
This is what I followed when I created the certificate. The certificate was created using the server that runs Exchange 2003. After I activated the certificate, then I get the navigation blocked error page. Since the organization webserver and the Exchange server are onseperate machines, do I need to have the certificate on both servers? I am unclear about what to do next. Thanks for your help. "Oliver Moazzezi [MVP]" wrote in message news:%232MhhTudIHA.4880@TK2MSFTNGP02.phx.gbl... > Hi, > > Follow this: > > http://www.msexchange.org/tutorials/SSL_Enabling_OWA_2003.html > > Oliver > >
If it a self generated cert you will have to install the cert on the client machines that will be used, otherwise certificate errors (using IE7 will block you for example) will occur. Oliver
You can get a trusted root cert from GoDaddy or elsewhere for $39 and upwards. This will negate the need to install your self signed one to all client machines. Oliver
