You have a computer that is running Microsoft Exchange Server 2007 in a disjoint namespace.
Microsoft Office Outlook Web Access (OWA) is configured to use one or more standard authentication methods other than forms-based authentication (FBA).
You run the Test-OwaConnectivity command in Exchange Management Shell to verify that OWA is running correctly.
In this scenario, the command returns the following error message:
The test was unable to log on to Outlook Web Access because of an authentication failure.
You receive this error message even though OWA works. Additionally, when you use Microsoft Operations Manager (MOM) to monitor OWA, MOM also report that OWA has failed.
This error message occurs because the Exchange Server 2007 server uses adomain\username format during connectivity tests for standard authentication methods. However, in a disjoint namespace scenario, the domain name of the Exchange Server 2007 server differs from the domain name of the Active Directory.
To resolve this problem, install the following update rollup:
972076 Description of Update Rollup 2 for Exchange Server 2007 Service Pack 2
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
There are three articles of similar symptoms that were released. The following Microsoft Knowledge KB articles describe different authentication methods scenarios and different disjoint namespace scenarios problems:
954213 All Test commands that are related to the Client Access Server fail when you run the commands on an Exchange 2007 server in a disjoint namespace
957485 The Test-OwaConnectivity command returns a warning message in Exchange Server 2007 when there is a disjoint namespace
968224 You still receive unexpected error messages when you run the Test-OwaConnectivity command or the Test-ActiveSyncConnectivity command after you apply hotfix KB954213 on an Exchange 2007 Service Pack 1-based server
Note Update Rollup 2 for Exchange Server 2007 Service Pack 2 resolves the issues in these three articles in addition to the issue that is described in this article.
For more information about disjoint namespace scenario, visit the following Microsoft Web site: