none
Outlook connected to AD cant connect to the right autodiscover address

    Question

  • Hi

    1 x MS Server 2012 AD + DNS + DHCP (Internal DNS: dc01.domainas.local)
    1 x MS Server 2012 with All Exchange installed on it (Internal DNS: ex01.domainas.local)

    Internal domainname: domainas.local
    External domainname: domain.com

    Exchange server is configured with a wildcard certificate (*.domain.com). All internal and external vertical directories on exchange er pointing to https://outlook.domain.com/*

    Have also created a SRV record to autodiscovery.domain.com on the Active Directory server

    The Exchange server is working, and i can send email external and internal to people.

    Have tried to setup Outlook on external clients and mobile devices with autodiscovery. Have also tried to configure Outlook on a client that is not a member of the domain. The client configure Outlook with no issue with.

    But when i try to setup Outlook with a client that is a member of the domain controller, the client finds the Exchange server. But when i starting Outlook up,  I get an error message saying that the name on the certificate is not valid.

    This is because the client tries to connect to ex01.domainas.local and not outlook.domain.com as the other clients that is not a member of Exchange connects to.

    Anybody have a clue how to let clients member to exchange connect to the right hostname?

    Tuesday, September 24, 2013 12:31 PM

Answers

  • Your internal clients will, by default, locate Exchange server by its internal name, so this is expected behavior. Your domain joined client locates the Exchange through AD and DNS, and it gets local Exchange name. 

    Look at this article: http://support.microsoft.com/kb/940726/en-us


    Please mark as helpful if you find my contribution useful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you. Thank you! Damir

    • Proposed as answer by damirdMVP Wednesday, September 25, 2013 8:11 AM
    • Marked as answer by nPulz Wednesday, September 25, 2013 10:14 AM
    Wednesday, September 25, 2013 8:11 AM

All replies

  • Your internal clients will, by default, locate Exchange server by its internal name, so this is expected behavior. Your domain joined client locates the Exchange through AD and DNS, and it gets local Exchange name. 

    Look at this article: http://support.microsoft.com/kb/940726/en-us


    Please mark as helpful if you find my contribution useful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you. Thank you! Damir

    • Proposed as answer by damirdMVP Wednesday, September 25, 2013 8:11 AM
    • Marked as answer by nPulz Wednesday, September 25, 2013 10:14 AM
    Wednesday, September 25, 2013 8:11 AM
  • Thx damird,

    Had forgotten to change the ClientAccessServer AutoDiscoverServiceInternalUri in PowerShell.

    After doing this command, all worked as we wanted.

    Get-ClientAccessServer | set-ClientAccessServer -AutoDiscoverServiceInternalUri https://outlook.domain.com/Autodiscover/Autodiscover.xml

    Wednesday, September 25, 2013 10:13 AM
  • Hi,

    Glad that you have resoluved the issue.

    And I would like to explain, by default, the AutoDiscover Service Internal URL would be automatically configured with the server‘s FQDN. If the internal namespace differs from the external namespace, we should handle the URL properly.

    Best regards,

    Angela Shi

    Thursday, September 26, 2013 1:47 AM