OWA Authentication with multiple domains, Help!!

[fenstrat]

We have 3 domains, one exchange organization and 2 physical AD sites. Site A has 2 domains and OWA is configured to authenticate to either domain. The owa server is using the default Exchange virtual directory. This setup works fine.

Site B has 2 domains. We had to create a new virtual directory for this site to allow authentication to the domains in this site. OWA server redirects to the new virtual directory. Virtual directory is set to basic authentication. Exchweb directory is set to anonymous authentication. When I log into the OWA server and type the username and password it authenticates but brings up a second authentication box asking me to log into the exchange backend server. After I give the second authentication OWA opens fine.
Anyone know why this is happening. Also, is there a way to modify the domain configuration in the default exchange virtual directory

 

[Marcs41]

If you configure your Exchange 2000 server to receive mail for an additional SMTP domain, you may notice that users with this additional domain as their SMTP address may not be able to access Outlook Web Access. You need to make some configuration changes for this to work.

Let's assume you install your Exchange 2000 server such that all users have an SMTP address in the format of user@abc.com, but later require some users to have the user@def.com address.

By default, the /exchange virtual directory will point to the abc.com domain. Users with the def.com domain will not be able to access OWA using the /exchange virtual directory.

To resolve this issue, you need to create a new HTTP virtual directory, and point this to the def.com recipient policy that you will have created in Exchange System Manager. Here's how to do this:

1. Run Exchange System Manager, and navigate to your Server / Protocols / HTTP / Exchange Virtual Server.

2. Right-click Exchange Virtual Server, and choose New / Virtual Directory.

3. Give this new virtual directory a meaningful name, and ensure that the 'Mailboxes for' radio button is selected.

4. Click the Modify button, and choose the def.com domain.

5. Click the Access tab, and set the authentication options as required.

6. Close the property windows by clicking OK, and you will now see the new virtual directory in Exchange System Manager. It is now important to wait a short while, to allow the DS2MB process to create the virtual directory in the IIS metabase.

You can then use a URL of

http://servername/def

to access OWA for users with a user@def.com SMTP address, whereas a URL of

http://servername/exchange

is used for users with a user@abc.com SMTP address.



Marc
_{If 'something' 'somewhere' gives 'some' error, expect random guesses or no replies at all. Please specify details.
Free Tip: The F1 Key does NOT destroy your PC!}

 

[fenstrat]

Thanks, I also read this microsoft article yesterday. I did fix the problem. If the front end server is redirecting to a virtual directory, the user who accesses the owa must also have an email address configured for that domain. I just gave users the additional email address and it's working fine.