2 Exchange 2003 Servers, OWA user authentication problems
In my domain, we have 2 exchange 2003 servers set up, each had been used to store (2) separate user groups. In the past I have had 2 separate OWA instances, one on each server for the specified groups. The problem that I am encountering now is I wish to only have one OWA page that will go directly to a mailbox on either Server1 or Server2. The problem that I am having is that if I open up OWA on Server1, type in username and password for a mailbox that is located on Server2, OWA then pops up another username and password logon for the second server before it will open up OWA. I know that my users will no doubt freak out, thinking that their passwords aren't working etc. Is there a way that I can get rid of that secondary logon box that pops up?
September 4th, 2008 8:26pm

I think you are going to need a front end server that will route the traffic to the server that each users is on when they login.
Free Windows Admin Tool Kit Click here and download it now
September 5th, 2008 5:48am

Dear customer: Thanks for swhittis reply. Yes, you can achieve your idea via install another Exchange server 2003 and set is as a front-end server. The most important feature of the FE is providing Single namespace. The primary advantage of the front-end and back-end server architecture is the ability to expose a single, consistent namespace. You can define a single namespace for users to access their mailboxes (for example, https://mail for Outlook Web Access). Without a front-end server, each user must know the name of the server that stores their mailbox. This complicates administration and compromises flexibility, because every time your organization grows or changes and you move some or all mailboxes to another server, you must inform the users. With a single namespace, users can use the same URL or POP and IMAP client configuration, even if you add or remove servers or move mailboxes from server to server. Additionally, creating a single namespace ensures that HTTPS, POP, or IMAP access remains scalable as your organization grows. Finally, a single namespace reduces the number of server certificates required for SSL encryption because clients are using SSL to the same servers and using the same namespace. For more information about Front-End and Back-End Server Topology Guide for Exchange Server 2003 and Exchange 2000 Server, please refer to the following articles: Front-End and Back-End Server Topology Guide for Exchange Server 2003 and Exchange 2000 Server http://technet.microsoft.com/en-us/library/aa996980(EXCHG.65).aspx Hope it helps. If anything is unclear, please feel free to let me know. Rock Wang - MSFT
September 5th, 2008 9:36am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics