Outlook is unable to connect to Exchange 2013 public folder or auto-mapped mailbox
Cannot expand the folder. Microsoft Exchange is not available. Either there are network problems or the Exchange server is down for maintenance.
Additionally, you may see a credentials prompt if the Exchange Server administrator set ExternalAuthentication to Basic.
Description of the Outlook 2010 hotfix package (Outlook-x-none.msp): June 11, 2013
For Outlook 2007 and Outlook 2013, Microsoft is currently working on a fix for this issue and this article will be updated once more information is available.
The internal part of the Autodiscover response typically looks as follows:
EXHTTP exch1.contoso.com Off NTLM https://exch1.contoso.com/EWS/Exchange.asmx https://exch1.contoso.com/EWS/Exchange.asmx https://exch1.contoso.com/EWS/Exchange.asmx https://exch1.contoso.com/OAB/9f2dd03f-064b-4356-b0d0-6789c44ebf29/
The external part of the Autodiscover response typically looks as follows:
EXHTTP mail.contoso.com On Ntlm https://mail.contoso.com/EWS/Exchange.asmx https://mail.contoso.com/EWS/Exchange.asmx https://mail.contoso.com/EWS/Exchange.asmx
In this example, the first entry represents InternalHostname and is set to exch1.contoso.com. The second entry represents ExternalHostname and is set to mail.contoso.com.
Outlook generally tries to connect with the first EXHTTP block. If that connection fails, Outlook then tries to connect by using the second EXHTTP block. By default, Outlook uses this logic for the primary mailbox. However, it incorrectly skips to the second EXHTTP block for alternate mailbox connections.
for other considerations.
Article ID: 2839517 – Last Review: July 18, 2013 – Revision: 3.0
- Microsoft Office Outlook 2007
- Microsoft Outlook 2010
- Microsoft Outlook 2013
- Microsoft Exchange Online
|o365 o365a o365e o365m o365p after upgrade o365022013 KB2839517|