Configuring OWA where more than one Exchange 2003 Server exists

20 pts.
Tags:
Exchange 2003
Firewalls
Multiple Exchange Servers
Outlook
Outlook Web Access
OWA
RCP over HTTP
SSL certificate
SSL Exchange
Windows Server 2003
We are adding a second Exchange server onto the domain with the hopes of retiring the first box when the configuration is complete, tested, and working. It was a fairly painless install with SERVER1 being the Master and SERVER2 being the Master. SERVER1 was set up with OWA and RCP over HTTP working without error. SERVER1 is running MSServer 2003 with Exchanger server 2003 Enterprise SP2. SERVER2 is running on MS Server 2003 R2 with Exchange Server Enterprise SP2. https://SERVER2/exchange works internally using a self certified certificate (It was exported form SERVER1) All my research says that I can use the single instance of OWA over SERVER1 but when I access OWA externally, https://external.domain.com/exchange, I can only log on and access users on SERVER1. (OWA is using Forms-based authentication) Trying to access users located on SERVER2 gives me "Internet Explorer cannot access web page" If I change my firewall access rules on my Sonicwall Firewall to point to SERVER2 (not using forms-based authentication) and still using the same URL https://external.domain.com/exchange, I can then log in and see users on SERVER2 but not those users on SERVER1 however Outlook using RCP over HTTP doesn't work . Now to get to my question, How can I configure OWA using https://external.domain.com/exchange to authenticate and access Mailboxes and get Outlook using RCP over HTTP to work with both servers?
ASKED: May 15, 2009  1:41 PM
UPDATED: May 18, 2009  3:59 PM

Answer Wiki

Thanks. We'll let you know when a new response is added.

Have you considered installing a <a href=”http://www.msexchange.org/tutorials/OWA_Exchange_Server_2003.html”>front end server</a>? The front end server would allow access to both back end mail servers regardless of which one the users are on. It would also handle the RPC over HTTP(S). I highly recommend making it HTTPS not HTTP.

Discuss This Question: 2  Replies

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
  • ChrisMPG
    Thanks. I will give it a try. Can the front-end server be Exchange Server 2003 Standard since I will no be hosting any of the message stores? I will look more into RCP over HTTP(S) and pray I'm not getting out of my depth here!!
    20 pointsBadges:
    report
  • Technochic
    Yes you can use Exchange 2003 Standard for your front end server. Here is another article for your information.
    57,010 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Thanks! We'll email you when relevant content is added and updated.

Following