We help IT Professionals succeed at work.

Publish Exchange 2003 OWA with SSL through ISA 2004

Hooznext
Hooznext asked
on
550 Views
Last Modified: 2009-07-29
Hello experts.
I have a single Exchange 2003 box I am attempting to publish OWA with SSL through ISA, I have followed the instructions M$ has to the letter and it fails from outside my network. If I go to https://<ServerName>/Exchange I am able to connect fine, I get an error saying the name does not match the SSL which I expected due to the URL in the browser not matching the SSL name.

I think I found the problem...according to this article - http://www.microsoft.com/technet/prodtechnol/isa/2004/plan/digitalcertificates.mspx

It states in the properties of the publishing rule on the 'To' tab, the server name must match the name of the SSL. My problem is the SSL cert is named after my URL published for resolution to my OWA webserver and my internal nameing convention does not reflect the same. So, our users are trying to connect to https://www.<maildomain>.com and ISA is publishing this from the server <MailServer01>.<Location>.<InternalDomain>.com. This will cause a similar warning regarding the name of the SSL and ISA error's out and tells the user the page cannot be found.

Is anyone aware of a go around for this? I do not want to change the domain name we have been using for 5+ years and also changing the naming convention internally isn't a good option either. I also am not willing to publish the website without SSL.

Thanks for the assistance.
Comment
Watch Question

CERTIFIED EXPERT
Commented:
This one is on us!
(Get your first solution completely free - no credit card required)
UNLOCK SOLUTION

Author

Commented:
Matt,

Thanks for the article, I have used that site extensively but not having much luck with their search engine to locate what I need. The article gave me the information I needed to fix the issue. It boiled down to using the wrong method of exporting the SSL certificate (was using the export wizard instead of Copy to file...) and setting up the split DNS between the publich and private networks.

Thanks for the quick response and exactly the answer I needed. Sorry it took so long to get back to you as we are setting up an entirely new office and had many little issues demanding attention.
Unlock the solution to this question.
Join our community and discover your potential

Experts Exchange is the only place where you can interact directly with leading experts in the technology field. Become a member today and access the collective knowledge of thousands of technology experts.

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

OR

Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.