I have an issue with OWA and public folders. Head office has Private Store and Public Store on different servers. (To be precise one or two Public Folders are located on the Private Store Server). When accessing via OWA, the Public Folders are not available. ("Internet Explorer cannot display the webpage").Satellite offices have single Exchange Servers and OWA can access both mailbox and public folders. But interestingly when logged into a satellite office OWA the Public Folders AT HEADOFFICE are also available (although they popup a separate login screen).I don't know if it's relevant but headoffice uses https, whereas satellites are http.Is there some kind of setting that allows access to Public Folders located on a different server than your mailbox?Thanks

Sorry forgot to mention : this is Exchange 2003

Internet Explorer cannot display the webpage Check info: 1. Please describe the exchange topology (FE/BE?), the relationship between two offices. Public folder stores stay in the FE or BE? 2. You said public folders are not available via OWA, does it mean that error occur when users click the Public Folders button? 3. Does users who were unable to access the public folder all belongs to one mailbox store? 4. Is there any error info in the application log of public folder servers? Troubleshooting: 1. Please try to access the public folders directly via URL https://ServerName/public directly from each public folder server 2. Please go to ADSIEditor, check msExchOwningPFTreeBL attribute, make sure it contains the (distinguishedName) DNs of all public folder stores that make up the public folder hierarchy a. Start->Run->ADSIEdit.msc b. Expand Configuration->CN= Configuration,DC=DomainName,DC=Com->CN=Services->CN=Microsoft Exchange->CN=OrgName->CN=Exchange Administrative Group (xxx)->CN=Folder Hierarchies c. In the right pane, double-click CN=Public Folders entry, check msExchOwningPFTreeBL attribute in the Attribute Editor tab. It should contain the DNs of all public folder stores

Thanks. First thing I've tried is doing (1) using the URL directly. With https I get same error, but with http this works (internally)! I suspect not available externally due to firewall etc, but at least now have a path of investigation to follow.