Windows Forum

Ask something
Discussion Locked

Exchange 2000 OWA Problem

0 helpful
7 replies

by joshg 1 view

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I have a client that would like to use Outlook Web Access for remote mail. That part of OWA works great. They enter the URL to get to the login for Exchange 2000 then their mailbox, calendars etc. are dispalyed. The problem is that they use several dozen public folders. Which aren't currently showing up. When the user logs on to OWA in the building they get the public forlders displayed. When they go to another site (their home for example) the following error pops up while trying to access the folders: The server name or address could not be resolved 12007. OWA continues to work except they can't access the public folders.

Is this Firewall related? The only ports opened are 80 and 25.

7 replies

by techkid

Not too sure on this one but I know the latest Service Pack for Exchange 2000 was supposed to add several enhancements to OWA. Maybe try that

by joshg

Works fine on machines without the latest SP so I haven't loaded the latest to this machine yet.

by maxwell edison

This issue can occur if you enter the fully qualified domain name (FQDN) of your Exchange 2000 Server computer in your browser Address box.

To resolve this issue, use the following syntax when you enter the URL in your browser Address box:

http:// server_name /public/?cmd=contents

To work around this issue, use one of the following methods:

1. Go through a front-end server when using an FQDN to gain access to your mailbox with Outlook Web Access. For information about deploying Exchange 2000 using front-end and back-end servers, please see the "Exchange 2000 Front-end and Back-end Topology" white paper from the following Microsoft Web site:

http://www.microsoft.com/exchange/techinfo/deployment/2000/E2KFrontBack.asp

2.Use a separate instance of your browser to connect to public folders.

----------

The preceding is from Microsoft article Q260803 titled, " Public Folder Access Does Not Work When Using FQDN"

http://support.microsoft.com/directory/article.asp?ID=KB;EN-US;Q260803

(REMOVE SPACES from the pasted URL.)

Maxwell

by joshg

Using the FQDN, still creates problems. I have the users logging directly to the public folders instead of their box when they need to browse pub folders.

by joshg

Using the FQDN, still creates problems. I have the users logging directly to the public folders instead of their box when they need to browse pub folders.

This discussion is closed to new replies.