locked
Global address list is unavailable RRS feed

  • Question

  • Dear Forum Members,

    We use a Windows 2016 Exchange mail system with Office 365 with Outlook 2013 client and Windows 7 professional pc. The machines use in domain Windows 2012 server. The domain controller and the exhange run on a separate virtual machine.

    If I want to send a letter, I will receive this error message by clicking the recipient button (default mode is global address list). 

    "The connection to the Microsoft Exchange server is unavailable. To do this, Outlook must be online or connected."

    So I can not reach the address list on the server.

    In addition, automatic responses (outside) do not work.

    "The connection to the Exchange server is unavailable. To complete this action, Outlook must be online or connected."

    Please if someone has an idea to write you.

    Thanks.

    Totyó

    Wednesday, January 10, 2018 9:53 AM

Answers

  • Thanks for your response.

    We can see from the test results the Certificate name validation failed. Please make sure you domain and autodiscover record are all included in your certificate.

    Thanks.

    Regards,

    Jason Chao


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.

    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.

    • Proposed as answer by Jason.Chao Friday, January 19, 2018 1:47 AM
    • Marked as answer by Totyó Thursday, February 8, 2018 7:35 AM
    Wednesday, January 17, 2018 5:53 AM

All replies

  • Hi Totyó,

    Thanks for contacting our forum. Does this issue affect in both external and internal of your network? And affects all of the user or specific users?

    Firstly, we can re-download the OAB from the Outlook and check the results;

    We can also re-create the Outlook profile and have a test.

    If we cannot download the OAB please check if any error messages and please post out in detail.

    It’s also recommended to test the Autodiscover with the ExRca Tool: https://testconnectivity.microsoft.com/  and check if we can get the OAB virtual directory URL.

    On the server side we can recycle the MSExchangeOABAppPool and check the results.

    Hope it helps.

    Regards,

    Jason Chao


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.

    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.

    • Proposed as answer by Jason.Chao Thursday, January 11, 2018 9:44 AM
    • Marked as answer by Totyó Monday, January 15, 2018 11:14 AM
    • Unmarked as answer by Totyó Monday, January 15, 2018 11:14 AM
    Thursday, January 11, 2018 2:54 AM
  • Hi Jason,

    Thank you for your answer!

    Outside address is not used for Exchange mail, only the administrator has set up mail on your mobile device. He has enabled mobile exchange activ sync.

    I tried to re-create the account nothing has changed.
    I've done the test, I'm copying that.

                                                          

    Exchange ActiveSync Autodiscover

    Attempting the Autodiscover and Exchange ActiveSync test (if requested).
    Testing of Autodiscover for Exchange ActiveSync failed.

    Additional Details

    Elapsed Time: 664 ms.

    Test Steps

    Attempting each method of contacting the Autodiscover service.
    The Autodiscover service couldn't be contacted successfully by any method.

    Additional Details

    Elapsed Time: 664 ms.

    Test Steps

    Attempting to test potential Autodiscover URL https://xxx.hu:443/Autodiscover/Autodiscover.xml
    Testing of this potential Autodiscover URL failed.

    Additional Details

    Test Steps

    Attempting to resolve the host name xxx.hu in DNS.
    The host name resolved successfully.

    Additional Details
    Testing TCP port 443 on host xxx.hu to ensure it's listening and open.
    The port was opened successfully.

    Additional Details
    Testing the SSL certificate to make sure it's valid.
    The SSL certificate failed one or more certificate validation checks.

    Additional Details

    Test Steps

    The Microsoft Connectivity Analyzer is attempting to obtain the SSL certificate from remote server xxx.hu on port 443.
    The Microsoft Connectivity Analyzer successfully obtained the remote SSL certificate.

    Additional Details
    Validating the certificate name.
    Certificate name validation failed.
    Tell me more about this issue and how to resolve it

    Additional Details

    Host name xxx.hu doesn't match any name found on the server certificate CN=*.silihost.hu.
    Elapsed Time: 0 ms.
    Attempting to test potential Autodiscover URL https://autodiscover.xxx.hu:443/Autodiscover/Autodiscover.xml
    Testing of this potential Autodiscover URL failed.

    Additional Details

    Test Steps

    Attempting to resolve the host name autodiscover.xxx.hu in DNS.
    The host name couldn't be resolved.
    Tell me more about this issue and how to resolve it

    Additional Details

    Host autodiscover.xxx.hu couldn't be resolved in DNS InfoDomainNonexistent.
    Elapsed Time: 108 ms.
    Attempting to contact the Autodiscover service using the HTTP redirect method.
    The attempt to contact Autodiscover using the HTTP Redirect method failed.

    Additional Details

    Test Steps

    Attempting to resolve the host name autodiscover.xxx.hu in DNS.
    The host name couldn't be resolved.
    Tell me more about this issue and how to resolve it

    Additional Details
    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.

    Additional Details

    Test Steps

    Attempting to locate SRV record _autodiscover._tcp.xxx.hu in DNS.
    The Autodiscover SRV record wasn't found in DNS.
    Tell me more about this issue and how to resolve it

    Additional Details
    Checking if there is an autodiscover CNAME record in DNS for your domain 'xxx.hu' for Office 365.
    Failed to validate autodiscover CNAME record in DNS. If your mailbox isn't in Office 365, you can ignore this warning.
    Tell me more about this issue and how to resolve it

    Additional Details

    There is no Autodiscover CNAME record for your domain 'xxx.hu'.
    Elapsed Time: 50 ms.

    Start OverRun Test Again

    Instead of the domain name, there is xxx

    What's wrong with that?
    Thanks in advance for the answers.

    Totyó

    Friday, January 12, 2018 10:08 AM
  • Thanks for your response.

    We can see from the test results the Certificate name validation failed. Please make sure you domain and autodiscover record are all included in your certificate.

    Thanks.

    Regards,

    Jason Chao


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.

    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.

    • Proposed as answer by Jason.Chao Friday, January 19, 2018 1:47 AM
    • Marked as answer by Totyó Thursday, February 8, 2018 7:35 AM
    Wednesday, January 17, 2018 5:53 AM
  • Hi,
     
    I am currently standing by for further update from you and would like to know how things are going. If you have any questions, please don't hesitate to let me know. And if the replies has helped you, please help to mark as answer and it could be helpful for others.
     
    Thanks for your time and have a nice day!

    Best Regards,
    Jason Chao


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.


    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.

    • Proposed as answer by Jason.Chao Wednesday, February 7, 2018 8:19 AM
    Thursday, February 1, 2018 9:00 AM
  • Hi Jason!

    Thanks for your help. Problem solved.

    Thursday, February 8, 2018 7:36 AM