|
marcelo73 -> RE: Setting up a CA for a Secure OWA (9.Jun.2005 9:33:00 AM)
|
Madcow, Soth, Henrik and company...
I think my problem (don't know others) is in Henrik Walther's article (http://www.msexchange.org/tutorials/SSL_Enabling_OWA_2003.html) where it says:
---------------------------------------- In the next screen we need to pay extra attention, as the common name reflects the external FQDN (Fully Qualified Domain Name), to spell it out, this is the address external users have to type in their browsers in order to access OWA from the Internet.
Note: As many (especially small to midsized) companies donÆt publish their Exchange servers directly to the Internet, but instead runs the Exchange server on a private IP address, they let their ISPÆs handle their external DNS settings. In most cases the ISP creates a so called A record named mail.domain.com pointing to the companyÆs public IP address, which then forwards the appropriate port (443) to the Exchange servers internal IP address. ----------------------------------------
Ok, this is my case; an ISP creates an A record named mail.mydomain.com pointing to my IP address.
In this place I type mail.mydomain.com (mydomain is my domain, you understand) Am I doing this ok? or am I making a mistake here?
then... after having completed all the tutorial I type http://mail.mydomain.com/exchange and it works as if I haven't done anything and if I type the same with HTTPS it will say PAGE cannot be displayed.
For heavens sake! Is this SUCH difficult to configure a secure OWA?
I still hope you can help me figure this out. Marcelo.
|
|
|
|