none
Outlook cannot resolve new account on Exchange 2013 server

    Question

  • Hi folks,

    I am currently installing Exchange 2013 into my company.  We already have Exchange 2010 running on another system.

    The issue I have is that while users can login to their mailboxes via OWA on server2013 they cannot resolve in outlook either by autodiscover or manual discover.  The error I get is:

    "The connection to Microsoft Exchange is unavailable.  Outlook must be online or connected to complete this action".

    On the next screen it resolves the GUID of Server2013 and the mailbox but again will not connect.

    My domain is domain.local, my email addresses are domain.com.

    I have ensured that Server2013 has a SAN certificate with all variations of server2013.domain.whatever.

    I appreciate this may be an autodiscoery problem but am loathed to start "experimenting" on what is alive system without knowing what the consequences of my actions may be to the running Exchange 2010 server.

    Any help greatly appreciated.

    Cheers,

    Steve

    Thursday, September 05, 2013 8:11 AM

All replies

  • What is the *Exact* version of outlook please?

    Outlook 2010 with what build number please?


    Cheers,

    Rhoderick

    Microsoft Senior Exchange PFE

    Blog: http://blogs.technet.com/rmilne  Twitter:   LinkedIn:   Facebook:   XING:

    Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

    Thursday, September 05, 2013 12:46 PM
  • Hi Rhoderick,

    I have tried it with both Outlook 2010 (14.0.6112.5000 32Bit) and Outlook 2013 (15.0.4505.1002 32Bit).

    Cheers,

    Steve

    Thursday, September 05, 2013 3:33 PM
  • For the Outlook 2010 client, that looks like it is the October 2011 update.

    That client is *NOT* supported with Exchange 2010 and needs to be updated please. Details in this post:

    http://blogs.technet.com/b/rmilne/archive/2013/07/18/patching-exchange-don-t-overlook-outlook.aspx


    Cheers,

    Rhoderick

    Microsoft Senior Exchange PFE

    Blog: http://blogs.technet.com/rmilne  Twitter:   LinkedIn:   Facebook:   XING:

    Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

    Thursday, September 05, 2013 3:40 PM
  • For Outlook 2013 that should be OK as it's higher than the minimum requirement of (15.0.4420.1017).

    Do you have CU2 installed onto the Exchange 2013 server, and have any modificaitons been made to it all ?


    Cheers,

    Rhoderick

    Microsoft Senior Exchange PFE

    Blog: http://blogs.technet.com/rmilne  Twitter:   LinkedIn:   Facebook:   XING:

    Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

    Thursday, September 05, 2013 3:42 PM
  • Have you run the autodiscovery test from the Exchange connectivity tool? Does it pass? Also are the users on the domain or external users? I just went through a migration and moved from a 2010 to a 2013 environment

    Also, do a "test-email configuration" from Outlook by right-clicking while holding down the CTRL key on the Outlook icon in the taskbar. You should test out the URLs and make sure you can access from where outlook is installed to verify you have setup the paths correctly.

    • Edited by BMIG Thursday, September 05, 2013 5:28 PM
    Thursday, September 05, 2013 5:25 PM
  • Thanks for the replies guys,

    I have applied CU2 to the exchange server it no reports version 15.0 (build 712.24).  It unfortunatley hasn't solved the issue.

    As far as the connectivity tool, it fails to autodiscovery for users on the new 2013 server but aslo for the users on 2010, which functions fine.  It complains that it cant find the autodiscover.company.com and _autodiscover SRV record, both of which exist.

    Cheers,

    Steve

    Friday, September 06, 2013 10:15 AM
  • Hi,

     

    Let’s begin with the following article:

    http://support.microsoft.com/kb/2754898/en-us

     

    So we can firstly check if the internal host name is different from the external host name in your environment. And we can run : Get-OutlookAnywhere

     

    Here is a relevant thread: http://social.technet.microsoft.com/Forums/en-US/3277343c-c782-4a4b-a5aa-83c7c89088df/correct-configure-outlook-anywhere-in-exchange-2013-to-work-with-internalexternal-autodiscover

     

    Moreover, we can try the following resolutions:

    1.Confirm if “autodiscover.domain.com” are included in the certificate.
    2.Run the Test e-mail Auto Configuration or use ExRCA to test Autodiscover and Outlook Anywhere connectivity.
    ExRCA: https://www.testexchangeconnectivity.com/
    3.Fix with hotfix package. Please refer to the article: http://support.microsoft.com/kb/2839517/en-us

    If you have any question, please feel free to let me know.

    Thanks,
    Angela Shi

     

    Saturday, September 07, 2013 6:31 AM
  • Hi,

    Apologies for the late reply.  unfortunately I have eben off work for a while.

    Both the https://www.testexchangeconnectivity.com/ tests fail with the same result, listed below.  The IP address it resolves as w.x.y.z (apologies again for vagueness, I cannot let company information out into the public domain) is actually our web server on the Internet, it is referenced with an A record in the internal company.com domain, I am unsure why it is being referenced as the entity for the whole "company.com" domain.

    I have applied the hotfixes to my Outlook clients and still get the same error.

    Cheers,

    Steve 

    -> Oh and Simon_Wu, how do you know this is the answer????

    ---> connectivity test result as follows:

    The Microsoft Connectivity Analyzer is attempting to test Autodiscover for john.doe@company.com.

     Testing Autodiscover failed.

     

    Test Steps

     

    Attempting each method of contacting the Autodiscover service.

     The Autodiscover service couldn't be contacted successfully by any method.

     

    Test Steps

     

    Attempting to test potential Autodiscover URL https://company.com/AutoDiscover/AutoDiscover.xml

     Testing of this potential Autodiscover URL failed.

     

    Test Steps

     

    Attempting to resolve the host name company.com in DNS.

     The host name resolved successfully.

     

    Additional Details

     IP addresses returned: w.x.y.z

    Testing TCP port 443 on host company.com to ensure it's listening and open.

     The port was opened successfully.

    Testing the SSL certificate to make sure it's valid.

     The SSL certificate failed one or more certificate validation checks.

     

    Test Steps

     

    The Microsoft Connectivity Analyzer is attempting to obtain the SSL certificate from remote server company.com on port 443.

     The Microsoft Connectivity Analyzer successfully obtained the remote SSL certificate.

     

    Additional Details

     Remote Certificate Subject: CN=*.secure-secure.co.uk, OU=Domain Control Validated, Issuer: CN=GlobalSign Domain Validation CA - G2, O=GlobalSign nv-sa, C=BE.

    Validating the certificate name.

     Certificate name validation failed.

      Tell me more about this issue and how to resolve it

     

    Additional Details

     Host name company.com doesn't match any name found on the server certificate CN=*.secure-secure.co.uk, OU=Domain Control Validated.

    Attempting to test potential Autodiscover URL https://autodiscover.company.com/AutoDiscover/AutoDiscover.xml

     Testing of this potential Autodiscover URL failed.

     

    Test Steps

     

    Attempting to resolve the host name autodiscover.company.com in DNS.

     The host name couldn't be resolved.

      Tell me more about this issue and how to resolve it

     

    Additional Details

     Host autodiscover.company.com couldn't be resolved in DNS InfoDomainNonexistent.

    Attempting to contact the Autodiscover service using the HTTP redirect method.

     The attempt to contact Autodiscover using the HTTP Redirect method failed.

     

    Test Steps

     

    Attempting to resolve the host name autodiscover.company.com in DNS.

     The host name couldn't be resolved.

      Tell me more about this issue and how to resolve it

     

    Additional Details

     Host autodiscover.company.com couldn't be resolved in DNS InfoDomainNonexistent.

    Attempting to contact the Autodiscover service using the DNS SRV redirect method.

     The Microsoft Connectivity Analyzer failed to contact the Autodiscover service using the DNS SRV redirect method.

     

    Test Steps

     

    Attempting to locate SRV record _autodiscover._tcp.company.com in DNS.

     The Autodiscover SRV record wasn't found in DNS.

      Tell me more about this issue and how to resolve it


    Wednesday, September 25, 2013 12:57 PM
  • Hi,

    In order to narrow down the cause, I’d like to ask the following questions:

    1. Is  “autodiscover.domain.com” in your certificate?
    2. Is there A record make the host name“autodiscover.domain.com” point to the IP address of your CAS server?

    Thanks,

    Angela Shi

    Friday, September 27, 2013 10:13 AM
  • Hi Angela,

    Thanks for the reply.

    Yes to both of those :)

    Steve

    Friday, September 27, 2013 10:16 AM