none
Failure to match name to address list RRS feed

  • Question

  • I have a multi-tennat Exchange environment. I am trying to migration from 2007 to 2013 and all but one customer is working fine.

    When I try to setup Outlook on this one customer's computers (in their office), Outlook says, "The action cannot be completed. The name cannot be matched to a name in the address list." When I click OK, Outlook shows me the user's mailbox server in the Micorsoft Exchange server field (the Exchange 2007 server).

    I verified that the customer has an Autodiscover SRV record in internal and external DNS, and that the test user can log into webmail internally. I also verified that I can telnet to the 2013 CAS's external IP address over 443. Finally, I verified that webmail.hostedDomain.com resolves to the correct IP (and responds to ping).

    When I try to setup the same account on a laptop outside of the customer's network (specifically, the same domain as the Exchange servers), Autodiscover works fine and I can log into the mailbox.

    From the test machine (on the customer's network), Remote Connectivity Analyzer shows: 
    Attempting to send an Autodiscover POST request to potential Autodiscover URLs.
    Autodiscover settings weren't obtained when the Autodiscover POST request was sent.

    Test Steps

    The Microsoft Connectivity Analyzer is attempting to retrieve an XML Autodiscover response from URL https://webmail.hostedDomain.com:443/Autodiscover/Autodiscover.xml for user dtest@customerDomain.com.
    The Microsoft Connectivity Analyzer failed to obtain an Autodiscover XML response.

    Additional Details

    An HTTP 401 Unauthorized response was received from the remote Unknown server. This is usually the result of an incorrect username or password. If you are attempting to log onto an Office 365 service, ensure you are using your full User Principal Name (UPN).
    HTTP Response Headers:
    request-id: 6a387132-e372-4bf9-9833-779286820a61
    Set-Cookie: ClientId=HMCLPHFOUYPIWAYOVXSW; expires=Fri, 05-Aug-2016 16:57:49 GMT; path=/; HttpOnly
    Server: Microsoft-IIS/8.5
    WWW-Authenticate: Negotiate,NTLM,Basic realm="webmail.hostedDomain.com"
    X-Powered-By: ASP.NET
    X-FEServer: E2013ServerName
    Date: Thu, 06 Aug 2015 16:57:49 GMT
    Content-Length: 0

    What gives? Thanks?
    Saturday, August 8, 2015 1:06 AM

Answers

  • I found that there is a trust between the hosted domain and the customer's domain. Because of this, Outlook was trying to authenticate with NTLM. Using the Outlook 2010 and 2013 ADM templates, I setup a GPO to force Basic auth. With Basic auth, Outlook prompts for credentials, allowing the user to enter their hosted domain credentials.
    • Marked as answer by mhashemi Tuesday, August 25, 2015 8:08 PM
    Tuesday, August 25, 2015 8:08 PM

All replies

  • Hi,

    According to your description, I understand that internal user mailbox cannot use Outlook Anywhere to connect to Exchange server with error "The action cannot be completed. The name cannot be matched to a name in the address list".
    If I misunderstand your concern, please do not hesitate to let me know.

    I want to confirm some points, please help to collect answers for further troubleshooting:
    1. Is user hosted in Exchange 2007 or hosted in Exchange 2013 experience this issue?
    2. Do you migrate this problematic account from Exchange 2007 to Exchange 2013?

    For internal, Outlook Anywhere account use ECP access to Exchange server. Run below command to check: Get-ClientAccessServer | FL Identity,*URI*
    Also, run Get-MailboxDatabase | Fl Identity,*RPC* to check the value for RpcClientAccessServer.

    For this error message, please ensure Exchange Recipient Update Service works fine and if all user migrate to Exchange 2013 face this issue, please refer to below link to troubleshooting: https://technet.microsoft.com/en-us/library/dd285508(v=exchg.80).aspx

    Thanks


    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    Allen Wang
    TechNet Community Support

    Monday, August 10, 2015 1:58 AM
    Moderator
  • Allen, let me answer your questions:

    1. All mailboxes are still on Exchange 2007

    2. I migrated a test user today and found that the problem persists. The difference is, that the "Microsoft Exchange server" field in Outlook, shows the mailbox GUID, instead of the Exchange mailbox server

    3. Get-ClientAccessServer shows the same URL (https://webmail.hostedDomain.com/Autodiscover.com/Autodiscover.xml) for both Exchange 2007 and 2013 servers

    4. Get-MailboxDatabase on the Exchange 2007 servers doesn't return any value for "*RPC*" and it returns one of my 2013 CAS servers, when run in Exchange 2013

    5. There is no RUS in 2007


    Monday, August 10, 2015 4:16 PM
  • Allen, I also checked the Technet article and found that the search query I'm using is actually more inclusive than what is posted. Since my other tennants are fine, there's no reason to make any changes to the purportedSearch attribute.
    Monday, August 10, 2015 4:33 PM
  • I found that there is a trust between the hosted domain and the customer's domain. Because of this, Outlook was trying to authenticate with NTLM. Using the Outlook 2010 and 2013 ADM templates, I setup a GPO to force Basic auth. With Basic auth, Outlook prompts for credentials, allowing the user to enter their hosted domain credentials.
    • Marked as answer by mhashemi Tuesday, August 25, 2015 8:08 PM
    Tuesday, August 25, 2015 8:08 PM
  • Hello, 

    i have the same problem. Can you please tell me which GPO setting you use ? 

    Best regards

    Tuesday, October 30, 2018 1:54 PM