I have a multi-tennat Exchange environment. I am trying to migration from 2007 to 2013 and all but one customer are working fine.
When I try to setup Outlook on this one customer's computers (in their office, on their own AD domain), 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 thought the problem might go away if I migrated the mailboxes, so I moved a test mailbox to 2013 and have the same problem (Outlook shows me the mailbox GUID instead of the mailbox 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.
Here are some things I checked:
1. Verified that the user's account is not hidden from the GAL
2. Logged into webmail.hostedDomain.com works
3. Verified that the issue occurrs with both Exchange 2007 and 2013 mailboxes
4. Verified success with Test-Mailflow
5. Verified success with MAPIConnectivity
6. Verified that the the LegacyExchangeDN attribute looks correct
7. Verified that _autodiscover._tcp.customerDomain.com record resolves to the correct IP
8. Verified that webmail.hostedDomain.com resolves to the correct IP
9. Outlook Test E-mail AutoConfiguration tool shows correct resolution
10. The command, "Get-ClientAccessServer | select Identity,*URI*" shows the same URL (https://webmail.hostedDomain.com/Autodiscover.com/Autodiscover.xml) for both Exchange 2007 and 2013 servers
11. Exchange 2007 CAS have "ExternalClientAuthenticationMethod" == Negotiate & 2013 == NTLM (for Get-OutlookAnywhere)
12. InternalClientAuthenticationMethod == Ntlm for all servers (for Get-OutlookAnywhere)
13. Created the ExcludeScpLookup registry key on the internal (on the customer's domain) test machine
I don't think this is an Autodiscover issue, since Outlook shows me the correct mailbox server (for 2007 mailboxes) or mailbox GUID (for 2013 mailboxes). That indicates that I'm talking to Exchange, which leads me to believe this is a permissions issue, but I'm not sure where. Since I can log into OWA, I don't think it is a problem with mailbox permissions. I suspect that there is a problem with one of the users' address lists, but I can't tell which one (and I don't see anything out of order when I compare the perms to the ALs (and GALs) of other customers). I also noted that when run from a customerDomain.local computer, Outlook never prompts me for mailbox credentials. When I run Outlook from hostedDomain.local, I am prompted for mail credentials.
What gives? Thanks.
Other recent topics
