Article ID: 267936 - View products that this article applies to.
This article was previously published under Q267936
This article has been archived. It is offered "as is" and will no longer be updated.
Users who attempt to log on to Microsoft Outlook Web Access (OWA) without specifying the domain may not be authenticated, even though the default domain is configured in Exchange System Manager under Authentication Methods for a Hypertext Transfer Protocol (HTTP) virtual directory.
This problem can occur if the Directory Service to Metabase replication service does not correctly write the default logon domain to the metabase.
To resolve this problem, obtain the latest service pack for Microsoft Exchange 2000 Server. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
301378Under all other circumstances, make OWA virtual directory configuration changes from Exchange System Manager. For additional information, click the article number below to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/301378/EN-US/ )XGEN: How to Obtain the Latest Exchange 2000 Server Service Pack
264941You can also resolve this problem by configuring the default domain from the Internet Services Manager:
(http://support.microsoft.com/kb/264941/EN-US/ )XCCC: Changes to Virtual Directory Settings Are Not Maintained
You can use a backslash (\) as the default domain to check users' credentials against all trusted domains, instead of just a single domain that is specified.
The resolution that is described in the "Resolution" section of this article does not work for front-end servers because the local path for the Exchange virtual root is no longer valid from Internet Services Manager on the front-end server. When you attempt to gain access to the Directory Security tab, you receive the following error message:
To work around this problem, use one of the following methods:
The path does not exist or is not a directory.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Microsoft Exchange 2000 Server Service Pack 1.
For additional information, click the article number below to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/240105/EN-US/ )XGEN: General Information on Directory Service/Metabase Synchronization in Exchange 2000 Server