Microsoft KB Archive/329031

= A user cannot see public folders in the Outlook Web Access client when the user tries to input a non-FQDN host name in the Outlook Web Access client to open the public folders =

Article ID: 329031

Article Last Modified on 2/13/2007

-

APPLIES TO


 * Microsoft Exchange Server 2000 Service Pack 1
 * Microsoft Exchange 2000 Server Service Pack 2

-



This article was previously published under Q329031



SYMPTOMS
Consider the following scenario. A user creates a public folder in Microsoft Exchange 2000 Server. When the user tries to open the public folders by running the Microsoft Office Outlook Web Access (OWA) client that is using a non-FQDN host name, the user cannot see the public folders that the user previously created in Microsoft Exchange 2000 Server.

NOTE: If the users log on with an Outlook client, they can see the public folders that they previously created.



CAUSE
This issue occurs because the user is not using the fully qualified domain name (FQDN), the NetBIOS host name, or an IP address to log on to OWA. The user is logged on to the public folders through the anonymous account, and the user can see only those public folders for which the anonymous account has permissions.



RESOLUTION
This behavior is by design.OWA requires the FQDN, the NetBIOS host name, or the IP address. OWA does not support host names that are typed in, except for the NetBIOS host name.

For example, assume that you try to access the server by using http://mailserver/exchange. The computer's NetBIOS name is &quot;mycomputer&quot;, and the host records for mycomputer include mail.domain.com and mailserver. When you use http://mailserver/exchange to access OWA, you log on to the public folders by using the anonymous account, because you are not using the NetBIOS host name or the FQDN. You can access the public folders that you created by using any of the following addresses:
 * http://mailserver.domain.com/exchange
 * http://mail.domain.com/exchange
 * http:// /exchange
 * http://mycomputer/exchange



WORKAROUND
To work around this issue, use one of the following options to access OWA:
 * Use the FQDN.
 * Use the NetBIOS name on the local area network (LAN).
 * Use the server's IP address.
 * Create a separate public folder virtual directory for anonymous access, and then remove the anonymous access permissions from the default public virtual directory.
 * Create a forward lookup zone on your internal DNS server. Use a short domain name that users can remember so that they can use the FQDN.



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

Additional query words: xccc

Keywords: kbprb KB329031

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.