Exchange 2013 Client access issues

Сергей Карташев 1 Reputation point
2020-07-29T11:36:50.59+00:00

Hi,
We have 2 Exchange 2013 servers CU 12. DAG and one DB. When the database is active on the first server, Outlook continually prompts for authentication credentials for personal and public mailboxes. When switching the database to the second server, everything works correctly. DAG, DB, CAS, server components pass all availability checks.
The authentication settings on IIS on the servers are the same. All boxes are accessible through owa.

The only thing that was found was that health boxes were not created on the first (problematic) server when the Microsoft Exchange Health Manager was restarted.

any ideas?

Exchange Server Management
Exchange Server Management
Exchange Server: A family of Microsoft client/server messaging and collaboration software.Management: The act or process of organizing, handling, directing or controlling something.
7,331 questions
0 comments No comments
{count} votes

3 answers

Sort by: Most helpful
  1. Lydia Zhou - MSFT 2,371 Reputation points Microsoft Employee
    2020-07-30T04:42:31.623+00:00

    Hi,

    For "The authentication settings on IIS on the servers are the same", what do you check from IIS Manager?
    Do you use Outlook Anywhere or MAPI/HTTP in your organization? You can check with the following command:

    Get-OrganizationConfig|fl MapiHttpEnabled  
    

    Please use these command check the authentication method for Outlook Anywhere or MAPI/HTTP. You can post the screenshot here, and don't forget to cover your personal information:

    Get-OutlookAnywhere | fl servername,*method*  
    Get-MapiVirtualDirectory|fl Identity,*method*  
    

    Here are the default settings for Outlook Anywhere or MAPI/HTTP. Please make sure Negotiate is added into IISAuthenticationMethods:
    14452-514.png

    14446-515.png


  2. Lydia Zhou - MSFT 2,371 Reputation points Microsoft Employee
    2020-07-31T08:49:38.993+00:00

    Do you mean this issue occurs on EXMB02?
    What's the detailed version of Outlook do you use? Please make sure you install and use the latest Outlook version.

    For some old Outlook version, it uses the external namespace to connect mailbox. This can cause the credential issue if set external authentication to Basic. You can check this for more details: Outlook is unable to connect to Exchange 2013 public folder or auto-mapped mailbox.

    Please set ExternalClientAuthenticationMethod to NTLM or update to the latest version of Outlook, check if it works. Here is a similar thread for your reference: Users Prompted Once for Password When Opening Public Folders.

    Additionally, the Outlook credential is more related to authentication in general. For your issues about health mailboxes, since you are using an old version of Exchange 2013, it's suggested to upgrade to the latest version Exchange Server 2013 CU23. Something may be fixed automatically during the upgrade. If you need further assistance for the health mailbox, you can post a new question to discuss it specifically.


  3. Сергей Карташев 1 Reputation point
    2021-02-12T08:30:04.49+00:00

    Hi. sorry for the long answer. Updated all servers to CU23. The problem with access remains.I tried it on a new base with test accounts - no changes.
    After the last scheduled maintenance, I now have a picture: on one PC, where the data file was created a long time ago (includes both the main user box and shared boxes), everything works normally. Only the main mailbox works on the test VM under the same user without authorization. When adding shared mailboxes, authorization requests appear immediately. At the same time, the database is active on the EXMB02. It seems that there is no longer any dependence on the server where the active database is located67289-provider.png

    67237-outany.png

    0 comments No comments