XCCC: OWA Users Cannot View Public Folders After You Set Up Anonymous Access (329031)
The information in this article applies to:
- Microsoft Exchange 2000 Server SP1
- Microsoft Exchange 2000 Server SP2
This article was previously published under Q329031 SYMPTOMS After you set up a public folder for anonymous access, and
then Microsoft Outlook Web Access (OWA) users try to open the public folders,
these users cannot see the public folders that they created if they are using
an Outlook client.
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 "mycomputer", 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://IP_address/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.
| Modification Type: | Minor | Last Reviewed: | 4/25/2005 |
|---|
| Keywords: | kbprb KB329031 |
|---|
|