none
Outlook 2016 something went wrong connecting to Exchange 2013 Mailbox RRS feed

  • Question

  • Hi all,
    it's days now I am trying to set up an Exchange 2013 mailbox (from 1and1) on my Outlook 2016. As soon as I enter the email address I got the message:
    "Something went wrong and Outlook couldn't set up your account".

    It used to work until a few weeks ago (we installed the same mailbox onto different computers). I already tested the connectivity using testconnectivity.microsoft.com and it worked (with warnings). 

    Is there anybody who could help me please?

    Thanks,

    D.

    Tuesday, November 14, 2017 11:59 AM

All replies

  • Hi,

    >>we installed the same mailbox onto different computers

    Are you using Outlook 2016 on the other computers?

    >>I already tested the connectivity using testconnectivity.microsoft.com and it worked (with warnings). 

    What warnings did you get? Could you provide the test result here?

    Meanwhile, we may try to disable MAPI over HTTP on your computer and then try testing again. To disable MAPI over HTTP, try adding the following registry:

    (Important Serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it.)

    HKEY_CURRENT_USER\Software\Microsoft\Exchange
    DWORD: MapiHttpDisabled
    Value: 1

    Hope this helps.

    Regards,

    Steve Fan


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

    • Proposed as answer by Dericslab Friday, March 9, 2018 11:38 AM
    Wednesday, November 15, 2017 7:56 AM
    Moderator
  • Hi Steve,
    thanks for your reply. All other computers are using outlook 2016. I tested with MapiHttpDisabled, didn't work.

    Here the result of the test connectivity

                                                                                                                                                                                                          

    Testing Outlook connectivity.
    The Outlook connectivity test completed successfully.

    Additional Details

    Elapsed Time: 58084 ms.

    Test Steps

    The Microsoft Connectivity Analyzer is attempting to test Autodiscover for support@mydomain.net.
    Autodiscover was tested successfully.

    Additional Details

    Elapsed Time: 29106 ms.

    Test Steps

    Attempting each method of contacting the Autodiscover service.
    The Autodiscover service was tested successfully.

    Additional Details

    Elapsed Time: 29106 ms.

    Test Steps

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

    Additional Details

    Elapsed Time: 1443 ms.

    Test Steps

    Attempting to resolve the host name mydomain.net in DNS.
    The host name resolved successfully.

    Additional Details

    IP addresses returned: 217.160.233.168, 2001:8d8:1000:a05d:f0f6:5145:badf:b838
    Elapsed Time: 584 ms.
    Testing TCP port 443 on host mydomain.net to ensure it's listening and open.
    The port was opened successfully.

    Additional Details

    Elapsed Time: 473 ms.
    Testing the SSL certificate to make sure it's valid.
    The SSL certificate failed one or more certificate validation checks.

    Additional Details

    Elapsed Time: 384 ms.

    Test Steps

    The Microsoft Connectivity Analyzer is attempting to obtain the SSL certificate from remote server mydomain.net on port 443.
    The Microsoft Connectivity Analyzer wasn't able to obtain the remote SSL certificate.

    Additional Details

    The certificate couldn't be validated because SSL negotiation wasn't successful. This could have occurred as a result of a network error or because of a problem with the certificate installation.
    Elapsed Time: 360 ms.
    Attempting to test potential Autodiscover URL https://autodiscover.mydomain.net:443/Autodiscover/Autodiscover.xml
    Testing of this potential Autodiscover URL failed.

    Additional Details

    Elapsed Time: 22482 ms.

    Test Steps

    Attempting to resolve the host name autodiscover.mydomain.net in DNS.
    The host name resolved successfully.

    Additional Details

    IP addresses returned: 217.160.154.167
    Elapsed Time: 1181 ms.
    Testing TCP port 443 on host autodiscover.mydomain.net to ensure it's listening and open.
    The specified port is either blocked, not listening, or not producing the expected response.
    Tell me more about this issue and how to resolve it

    Additional Details

    A network error occurred while communicating with the remote host.
    Elapsed Time: 21300 ms.
    Attempting to contact the Autodiscover service using the HTTP redirect method.
    The Autodiscover service was successfully contacted using the HTTP redirect method.

    Additional Details

    Elapsed Time: 5180 ms.

    Test Steps

    Attempting to resolve the host name autodiscover.mydomain.net in DNS.
    The host name resolved successfully.

    Additional Details

    IP addresses returned: 217.160.154.167
    Elapsed Time: 9 ms.
    Testing TCP port 80 on host autodiscover.mydomain.net to ensure it's listening and open.
    The port was opened successfully.

    Additional Details

    Elapsed Time: 258 ms.
    The Microsoft Connectivity Analyzer is checking the host autodiscover.mydomain.net for an HTTP redirect to the Autodiscover service.
    The redirect (HTTP 301/302) response was received successfully.

    Additional Details

    Redirect URL: https://1.exchange.1and1.eu/Autodiscover/Autodiscover.xml
    HTTP Response Headers:
    Content-Length: 180
    Content-Type: text/html; charset=UTF-8
    Date: Wed, 15 Nov 2017 11:30:28 GMT
    Location: https://1.exchange.1and1.eu/Autodiscover/Autodiscover.xml
    Server: Microsoft-IIS/8.5
    X-Powered-By: ASP.NET
    Elapsed Time: 359 ms.
    Attempting to test potential Autodiscover URL https://1.exchange.1and1.eu/Autodiscover/Autodiscover.xml
    Testing of the Autodiscover URL was successful.

    Additional Details

    Elapsed Time: 4553 ms.

    Test Steps

    Attempting to resolve the host name 1.exchange.1and1.eu in DNS.
    The host name resolved successfully.

    Additional Details

    IP addresses returned: 217.160.154.165, 217.160.154.197
    Elapsed Time: 476 ms.
    Testing TCP port 443 on host 1.exchange.1and1.eu to ensure it's listening and open.
    The port was opened successfully.

    Additional Details

    Elapsed Time: 495 ms.
    Testing the SSL certificate to make sure it's valid.
    The certificate passed all validation requirements.

    Additional Details

    Elapsed Time: 649 ms.

    Test Steps

    The Microsoft Connectivity Analyzer is attempting to obtain the SSL certificate from remote server 1.exchange.1and1.eu on port 443.
    The Microsoft Connectivity Analyzer successfully obtained the remote SSL certificate.

    Additional Details

    Remote Certificate Subject: CN=1.exchange.1and1.eu, L=Montabaur, S=Rhineland-Palatinate, OU=IT, O=1&1 Internet SE, C=DE, Issuer: CN=TeleSec ServerPass Class 2 CA, STREET=Untere Industriestr. 20, L=Netphen, PostalCode=57250, S=Nordrhein Westfalen, OU=T-Systems Trust Center, O=T-Systems International GmbH, C=DE.
    Elapsed Time: 589 ms.
    Validating the certificate name.
    The certificate name was validated successfully.

    Additional Details

    Host name 1.exchange.1and1.eu was found in the Certificate Subject Common name.
    Elapsed Time: 0 ms.
    Certificate trust is being validated.
    The certificate is trusted and all certificates are present in the chain.

    Test Steps

    The Microsoft Connectivity Analyzer is attempting to build certificate chains for certificate CN=1.exchange.1and1.eu, L=Montabaur, S=Rhineland-Palatinate, OU=IT, O=1&1 Internet SE, C=DE.
    One or more certificate chains were constructed successfully.

    Additional Details

    A total of 1 chains were built. The highest quality chain ends in root certificate CN=T-TeleSec GlobalRoot Class 2, OU=T-Systems Trust Center, O=T-Systems Enterprise Services GmbH, C=DE.
    Elapsed Time: 12 ms.
    Analyzing the certificate chains for compatibility problems with versions of Windows.
    Potential compatibility problems were identified with some versions of Windows.

    Additional Details

    The Microsoft Connectivity Analyzer can only validate the certificate chain using the Root Certificate Update functionality from Windows Update. Your certificate may not be trusted on Windows if the "Update Root Certificates" feature isn't enabled.
    Elapsed Time: 2 ms.
    Testing the certificate date to confirm the certificate is valid.
    Date validation passed. The certificate hasn't expired.

    Additional Details

    The certificate is valid. NotBefore = 4/20/2017 8:40:58 AM, NotAfter = 4/25/2019 11:59:59 PM
    Elapsed Time: 0 ms.
    Checking the IIS configuration for client certificate authentication.
    Client certificate authentication wasn't detected.

    Additional Details

    Accept/Require Client Certificates isn't configured.
    Elapsed Time: 1024 ms.
    Attempting to send an Autodiscover POST request to potential Autodiscover URLs.
    The Microsoft Connectivity Analyzer successfully retrieved Autodiscover settings by sending an Autodiscover POST.

    Additional Details

    Elapsed Time: 1907 ms.

    Test Steps

    The Microsoft Connectivity Analyzer is attempting to retrieve an XML Autodiscover response from URL https://1.exchange.1and1.eu/Autodiscover/Autodiscover.xml for user support@mydomain.net.
    The Autodiscover XML response was successfully retrieved.

    Additional Details

    Autodiscover Account Settings
    XML response:
    <?xml version="1.0"?>
    <Autodiscover xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.microsoft.com/exchange/autodiscover/responseschema/2006">
    <Response xmlns="http://schemas.microsoft.com/exchange/autodiscover/outlook/responseschema/2006a">
    <User>
    <DisplayName>HD Support</DisplayName>
    <LegacyDN>/o=First Organization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=36450f4551244feb9599628593b7dd92-ocs28</LegacyDN>
    <DeploymentId>c55fb657-8dd2-4685-9bc3-d76e4d8092c1</DeploymentId>
    </User>
    <Account>
    <AccountType>email</AccountType>
    <Action>settings</Action>
    <Protocol>
    <Type>EXCH</Type>
    <Server>567847ac-45e6-44e1-8bfc-2857bc211b30@mydomain.net</Server>
    <ServerDN>/o=First Organization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=567847ac-45e6-44e1-8bfc-2857bc211b30@mydomain.net</ServerDN>
    <ServerVersion>73C084EF</ServerVersion>
    <MdbDN>/o=First Organization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=567847ac-45e6-44e1-8bfc-2857bc211b30@mydomain.net/cn=Microsoft Private MDB</MdbDN>
    <ASUrl>https://winhexfeeu1.win.mail/EWS/Exchange.asmx</ASUrl>
    <OOFUrl>https://winhexfeeu1.win.mail/EWS/Exchange.asmx</OOFUrl>
    <OABUrl>https://1.exchange.1and1.eu/OAB/c8485a5f-8a49-4500-920b-23c16c5b435f/</OABUrl>
    <UMUrl>https://winhexfeeu1.win.mail/EWS/UM2007Legacy.asmx</UMUrl>
    <Port>0</Port>
    <DirectoryPort>0</DirectoryPort>
    <ReferralPort>0</ReferralPort>
    <AuthPackage>Anonymous</AuthPackage>
    <PublicFolderServer>1.exchange.1and1.eu</PublicFolderServer>
    <AD>winhexadeu1.win.mail</AD>
    <EwsUrl>https://winhexfeeu1.win.mail/EWS/Exchange.asmx</EwsUrl>
    <EmwsUrl>https://winhexfeeu1.win.mail/EWS/Exchange.asmx</EmwsUrl>
    <EcpUrl>https://winhexfeeu1.win.mail/ecp/</EcpUrl>
    <EcpUrl-um>?rfr=olk&amp;p=customize/voicemail.aspx&amp;exsvurl=1&amp;realm=mydomain.net</EcpUrl-um>
    <EcpUrl-aggr>?rfr=olk&amp;p=personalsettings/EmailSubscriptions.slab&amp;exsvurl=1&amp;realm=mydomain.net</EcpUrl-aggr>
    <EcpUrl-mt>PersonalSettings/DeliveryReport.aspx?rfr=olk&amp;exsvurl=1&amp;IsOWA=&lt;IsOWA&gt;&amp;MsgID=&lt;MsgID&gt;&amp;Mbx=&lt;Mbx&gt;&amp;realm=mydomain.net</EcpUrl-mt>
    <EcpUrl-ret>?rfr=olk&amp;p=organize/retentionpolicytags.slab&amp;exsvurl=1&amp;realm=mydomain.net</EcpUrl-ret>
    <EcpUrl-sms>?rfr=olk&amp;p=sms/textmessaging.slab&amp;exsvurl=1&amp;realm=mydomain.net</EcpUrl-sms>
    <EcpUrl-publish>customize/calendarpublishing.slab?rfr=olk&amp;exsvurl=1&amp;FldID=&lt;FldID&gt;&amp;realm=mydomain.net</EcpUrl-publish>
    <EcpUrl-photo>PersonalSettings/EditAccount.aspx?rfr=olk&amp;chgPhoto=1&amp;exsvurl=1&amp;realm=mydomain.net</EcpUrl-photo>
    <EcpUrl-tm>?rfr=olk&amp;ftr=TeamMailbox&amp;exsvurl=1&amp;realm=mydomain.net</EcpUrl-tm>
    <EcpUrl-tmCreating>?rfr=olk&amp;ftr=TeamMailboxCreating&amp;SPUrl=&lt;SPUrl&gt;&amp;Title=&lt;Title&gt;&amp;SPTMAppUrl=&lt;SPTMAppUrl&gt;&amp;exsvurl=1&amp;realm=mydomain.net</EcpUrl-tmCreating>
    <EcpUrl-tmEditing>?rfr=olk&amp;ftr=TeamMailboxEditing&amp;Id=&lt;Id&gt;&amp;exsvurl=1&amp;realm=mydomain.net</EcpUrl-tmEditing>
    <EcpUrl-extinstall>Extension/InstalledExtensions.slab?rfr=olk&amp;exsvurl=1&amp;realm=mydomain.net</EcpUrl-extinstall>
    <ServerExclusiveConnect>off</ServerExclusiveConnect>
    </Protocol>
    <Protocol>
    <Type>EXPR</Type>
    <Server>1.exchange.1and1.eu</Server>
    <ASUrl>https://1.exchange.1and1.eu/EWS/Exchange.asmx</ASUrl>
    <OOFUrl>https://1.exchange.1and1.eu/EWS/Exchange.asmx</OOFUrl>
    <OABUrl>https://1.exchange.1and1.eu/OAB/c8485a5f-8a49-4500-920b-23c16c5b435f/</OABUrl>
    <UMUrl>https://1.exchange.1and1.eu/EWS/UM2007Legacy.asmx</UMUrl>
    <Port>0</Port>
    <DirectoryPort>0</DirectoryPort>
    <ReferralPort>0</ReferralPort>
    <SSL>On</SSL>
    <AuthPackage>Negotiate</AuthPackage>
    <EwsUrl>https://1.exchange.1and1.eu/EWS/Exchange.asmx</EwsUrl>
    <EmwsUrl>https://1.exchange.1and1.eu/EWS/Exchange.asmx</EmwsUrl>
    <ServerExclusiveConnect>on</ServerExclusiveConnect>
    <EwsPartnerUrl>https://1.exchange.1and1.eu/EWS/Exchange.asmx</EwsPartnerUrl>
    <GroupingInformation>KA</GroupingInformation>
    </Protocol>
    <Protocol>
    <Type>WEB</Type>
    <Port>0</Port>
    <DirectoryPort>0</DirectoryPort>
    <ReferralPort>0</ReferralPort>
    <Internal>
    <OWAUrl AuthenticationMethod="Basic, Fba">https://winhexfeeu1.win.mail/owa/</OWAUrl>
    <OWAUrl AuthenticationMethod="Basic, Fba">https://winhexfeeu11.win.mail/owa/</OWAUrl>
    <OWAUrl AuthenticationMethod="Basic, Fba">https://winhexfeeu13.win.mail/owa/</OWAUrl>
    <OWAUrl AuthenticationMethod="Basic, Fba">https://winhexfeeu15.win.mail/owa/</OWAUrl>
    <OWAUrl AuthenticationMethod="Basic, Fba">https://winhexfeeu3.win.mail/owa/</OWAUrl>
    <OWAUrl AuthenticationMethod="Basic, Fba">https://winhexfeeu5.win.mail/owa/</OWAUrl>
    <OWAUrl AuthenticationMethod="Basic, Fba">https://winhexfeeu7.win.mail/owa/</OWAUrl>
    <OWAUrl AuthenticationMethod="Basic, Fba">https://winhexfeeu9.win.mail/owa/</OWAUrl>
    <OWAUrl AuthenticationMethod="Basic, Fba">https://winhexfemig1.win.mail/owa/</OWAUrl>
    <OWAUrl AuthenticationMethod="Basic, Fba">https://winhexfemig3.win.mail/owa/</OWAUrl>
    <Protocol>
    <Type>EXCH</Type>
    <ASUrl>https://winhexfeeu1.win.mail/EWS/Exchange.asmx</ASUrl>
    </Protocol>
    </Internal>
    </Protocol>
    <Protocol>
    <Type>EXHTTP</Type>
    <Server>1.exchange.1and1.eu</Server>
    <ASUrl>https://winhexfeeu1.win.mail/EWS/Exchange.asmx</ASUrl>
    <OOFUrl>https://winhexfeeu1.win.mail/EWS/Exchange.asmx</OOFUrl>
    <OABUrl>https://1.exchange.1and1.eu/OAB/c8485a5f-8a49-4500-920b-23c16c5b435f/</OABUrl>
    <UMUrl>https://winhexfeeu1.win.mail/EWS/UM2007Legacy.asmx</UMUrl>
    <Port>0</Port>
    <DirectoryPort>0</DirectoryPort>
    <ReferralPort>0</ReferralPort>
    <SSL>On</SSL>
    <AuthPackage>Ntlm</AuthPackage>
    <EwsUrl>https://winhexfeeu1.win.mail/EWS/Exchange.asmx</EwsUrl>
    <EmwsUrl>https://winhexfeeu1.win.mail/EWS/Exchange.asmx</EmwsUrl>
    <EcpUrl>https://winhexfeeu1.win.mail/ecp/</EcpUrl>
    <EcpUrl-um>?rfr=olk&amp;p=customize/voicemail.aspx&amp;exsvurl=1&amp;realm=mydomain.net</EcpUrl-um>
    <EcpUrl-aggr>?rfr=olk&amp;p=personalsettings/EmailSubscriptions.slab&amp;exsvurl=1&amp;realm=mydomain.net</EcpUrl-aggr>
    <EcpUrl-mt>PersonalSettings/DeliveryReport.aspx?rfr=olk&amp;exsvurl=1&amp;IsOWA=&lt;IsOWA&gt;&amp;MsgID=&lt;MsgID&gt;&amp;Mbx=&lt;Mbx&gt;&amp;realm=mydomain.net</EcpUrl-mt>
    <EcpUrl-ret>?rfr=olk&amp;p=organize/retentionpolicytags.slab&amp;exsvurl=1&amp;realm=mydomain.net</EcpUrl-ret>
    <EcpUrl-sms>?rfr=olk&amp;p=sms/textmessaging.slab&amp;exsvurl=1&amp;realm=mydomain.net</EcpUrl-sms>
    <EcpUrl-publish>customize/calendarpublishing.slab?rfr=olk&amp;exsvurl=1&amp;FldID=&lt;FldID&gt;&amp;realm=mydomain.net</EcpUrl-publish>
    <EcpUrl-photo>PersonalSettings/EditAccount.aspx?rfr=olk&amp;chgPhoto=1&amp;exsvurl=1&amp;realm=mydomain.net</EcpUrl-photo>
    <EcpUrl-tm>?rfr=olk&amp;ftr=TeamMailbox&amp;exsvurl=1&amp;realm=mydomain.net</EcpUrl-tm>
    <EcpUrl-tmCreating>?rfr=olk&amp;ftr=TeamMailboxCreating&amp;SPUrl=&lt;SPUrl&gt;&amp;Title=&lt;Title&gt;&amp;SPTMAppUrl=&lt;SPTMAppUrl&gt;&amp;exsvurl=1&amp;realm=mydomain.net</EcpUrl-tmCreating>
    <EcpUrl-tmEditing>?rfr=olk&amp;ftr=TeamMailboxEditing&amp;Id=&lt;Id&gt;&amp;exsvurl=1&amp;realm=mydomain.net</EcpUrl-tmEditing>
    <EcpUrl-extinstall>Extension/InstalledExtensions.slab?rfr=olk&amp;exsvurl=1&amp;realm=mydomain.net</EcpUrl-extinstall>
    <ServerExclusiveConnect>On</ServerExclusiveConnect>
    </Protocol>
    <Protocol>
    <Type>EXHTTP</Type>
    <Server>1.exchange.1and1.eu</Server>
    <ASUrl>https://1.exchange.1and1.eu/EWS/Exchange.asmx</ASUrl>
    <OOFUrl>https://1.exchange.1and1.eu/EWS/Exchange.asmx</OOFUrl>
    <OABUrl>https://1.exchange.1and1.eu/OAB/c8485a5f-8a49-4500-920b-23c16c5b435f/</OABUrl>
    <UMUrl>https://1.exchange.1and1.eu/EWS/UM2007Legacy.asmx</UMUrl>
    <Port>0</Port>
    <DirectoryPort>0</DirectoryPort>
    <ReferralPort>0</ReferralPort>
    <SSL>On</SSL>
    <AuthPackage>Negotiate</AuthPackage>
    <EwsUrl>https://1.exchange.1and1.eu/EWS/Exchange.asmx</EwsUrl>
    <EmwsUrl>https://1.exchange.1and1.eu/EWS/Exchange.asmx</EmwsUrl>
    <ServerExclusiveConnect>On</ServerExclusiveConnect>
    </Protocol>
    </Account>
    </Response>
    </Autodiscover>
    HTTP Response Headers:
    request-id: d3385416-58d9-4dce-b75a-b62d9a533841
    X-CalculatedBETarget: winhexbeeu27.win.mail
    X-DiagInfo: WINHEXBEEU27
    X-BEServer: WINHEXBEEU27
    Cache-Control: private
    Content-Type: text/xml; charset=utf-8
    Set-Cookie: ClientId=AWWFEKUKBESHYFRDGZBQ; expires=Thu, 15-Nov-2018 11:30:33 GMT; path=/; HttpOnly,X-BackEndCookie=S-1-5-21-3641299097-2916662688-2906139245-245991=u56Lnp2ejJqBzsbLmpuZnZ7Sx8rIntLLm5mb0p3GnMzSnczMz82dzZzOzpnGgYHNz87I0s7N0s7Kq87OxczPxczM; expires=Fri, 15-Dec-2017 11:30:33 GMT; path=/Autodiscover; secure; HttpOnly
    Server: Microsoft-IIS/8.0
    X-AspNet-Version: 4.0.30319
    Persistent-Auth: true
    X-Powered-By: ASP.NET
    Strict-Transport-Security: max-age=15768000
    X-FEServer: WINHEXFEEU2
    Date: Wed, 15 Nov 2017 11:30:33 GMT
    Content-Length: 8682
    Elapsed Time: 1907 ms.
    Autodiscover settings for Outlook connectivity are being validated.
    The Microsoft Connectivity Analyzer validated the Outlook Autodiscover settings.

    Additional Details

    Elapsed Time: 0 ms.
    Testing RPC over HTTP connectivity to server 1.exchange.1and1.eu
    RPC over HTTP connectivity was verified successfully.

    Additional Details

    HTTP Response Headers:
    request-id: 0482d5a6-809e-4854-8f65-17423cb62eb1
    Set-Cookie: ClientId=FQFCFXBEUJQDYWPIRG; expires=Thu, 15-Nov-2018 11:30:34 GMT; path=/; HttpOnly
    Server: Microsoft-IIS/8.0
    WWW-Authenticate: Negotiate,NTLM,Basic realm="1.exchange.1and1.eu"
    X-Powered-By: ASP.NET
    Strict-Transport-Security: max-age=15768000
    X-FEServer: WINHEXFEEU2
    Date: Wed, 15 Nov 2017 11:30:34 GMT
    Content-Length: 0
    Elapsed Time: 28977 ms.

    Test Steps

    Attempting to resolve the host name 1.exchange.1and1.eu in DNS.
    The host name resolved successfully.

    Additional Details

    IP addresses returned: 217.160.154.165, 217.160.154.197
    Elapsed Time: 7 ms.
    Testing TCP port 443 on host 1.exchange.1and1.eu to ensure it's listening and open.
    The port was opened successfully.

    Additional Details

    Elapsed Time: 194 ms.
    Testing the SSL certificate to make sure it's valid.
    The certificate passed all validation requirements.

    Additional Details

    Elapsed Time: 418 ms.

    Test Steps

    The Microsoft Connectivity Analyzer is attempting to obtain the SSL certificate from remote server 1.exchange.1and1.eu on port 443.
    The Microsoft Connectivity Analyzer successfully obtained the remote SSL certificate.

    Additional Details

    Remote Certificate Subject: CN=1.exchange.1and1.eu, L=Montabaur, S=Rhineland-Palatinate, OU=IT, O=1&1 Internet SE, C=DE, Issuer: CN=TeleSec ServerPass Class 2 CA, STREET=Untere Industriestr. 20, L=Netphen, PostalCode=57250, S=Nordrhein Westfalen, OU=T-Systems Trust Center, O=T-Systems International GmbH, C=DE.
    Elapsed Time: 366 ms.
    Validating the certificate name.
    The certificate name was validated successfully.

    Additional Details

    Host name 1.exchange.1and1.eu was found in the Certificate Subject Common name.
    Elapsed Time: 0 ms.
    Certificate trust is being validated.
    The certificate is trusted and all certificates are present in the chain.

    Test Steps

    The Microsoft Connectivity Analyzer is attempting to build certificate chains for certificate CN=1.exchange.1and1.eu, L=Montabaur, S=Rhineland-Palatinate, OU=IT, O=1&1 Internet SE, C=DE.
    One or more certificate chains were constructed successfully.

    Additional Details

    A total of 1 chains were built. The highest quality chain ends in root certificate CN=T-TeleSec GlobalRoot Class 2, OU=T-Systems Trust Center, O=T-Systems Enterprise Services GmbH, C=DE.
    Elapsed Time: 12 ms.
    Analyzing the certificate chains for compatibility problems with versions of Windows.
    Potential compatibility problems were identified with some versions of Windows.

    Additional Details

    The Microsoft Connectivity Analyzer can only validate the certificate chain using the Root Certificate Update functionality from Windows Update. Your certificate may not be trusted on Windows if the "Update Root Certificates" feature isn't enabled.
    Elapsed Time: 3 ms.
    Testing the certificate date to confirm the certificate is valid.
    Date validation passed. The certificate hasn't expired.

    Additional Details

    The certificate is valid. NotBefore = 4/20/2017 8:40:58 AM, NotAfter = 4/25/2019 11:59:59 PM
    Elapsed Time: 0 ms.
    Checking the IIS configuration for client certificate authentication.
    Client certificate authentication wasn't detected.

    Additional Details

    Accept/Require Client Certificates isn't configured.
    Elapsed Time: 271 ms.
    Testing HTTP Authentication Methods for URL https://1.exchange.1and1.eu/rpc/rpcproxy.dll?567847ac-45e6-44e1-8bfc-2857bc211b30@mydomain.net:6002.
    The HTTP authentication methods are correct.

    Additional Details

    The Microsoft Connectivity Analyzer found all expected authentication methods and no disallowed methods. Methods found: Basic, Negotiate, NTLM
    HTTP Response Headers:
    request-id: 0482d5a6-809e-4854-8f65-17423cb62eb1
    Set-Cookie: ClientId=FQFCFXBEUJQDYWPIRG; expires=Thu, 15-Nov-2018 11:30:34 GMT; path=/; HttpOnly
    Server: Microsoft-IIS/8.0
    WWW-Authenticate: Negotiate,NTLM,Basic realm="1.exchange.1and1.eu"
    X-Powered-By: ASP.NET
    Strict-Transport-Security: max-age=15768000
    X-FEServer: WINHEXFEEU2
    Date: Wed, 15 Nov 2017 11:30:34 GMT
    Content-Length: 0
    Elapsed Time: 204 ms.
    Attempting to ping RPC proxy 1.exchange.1and1.eu.
    RPC Proxy was pinged successfully.

    Additional Details

    Elapsed Time: 961 ms.
    Attempting to ping the MAPI Mail Store endpoint with identity: 567847ac-45e6-44e1-8bfc-2857bc211b30@mydomain.net:6001.
    The endpoint was pinged successfully.

    Additional Details

    The endpoint responded in 558 ms.
    Elapsed Time: 4559 ms.
    Testing the MAPI Address Book endpoint on the Exchange server.
    The address book endpoint was tested successfully.

    Additional Details

    Elapsed Time: 8879 ms.

    Test Steps

    Attempting to ping the MAPI Address Book endpoint with identity: 567847ac-45e6-44e1-8bfc-2857bc211b30@mydomain.net:6004.
    The endpoint was pinged successfully.

    Additional Details

    The endpoint responded in 426 ms.
    Elapsed Time: 5415 ms.
    Testing the address book "Check Name" operation for user support@mydomain.net against server 567847ac-45e6-44e1-8bfc-2857bc211b30@mydomain.net.
    Check Name succeeded.

    Additional Details

    DisplayName: HD Support, LegDN: /o=First Organization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=36450f4551244feb9599628593b7dd92-ocs28
    Elapsed Time: 3464 ms.
    Testing the MAPI Referral service on the Exchange Server.
    The Referral service was tested successfully.

    Additional Details

    Elapsed Time: 7191 ms.

    Test Steps

    Attempting to ping the MAPI Referral Service endpoint with identity: 567847ac-45e6-44e1-8bfc-2857bc211b30@mydomain.net:6002.
    The endpoint was pinged successfully.

    Additional Details

    The endpoint responded in 629 ms.
    Elapsed Time: 4624 ms.
    Attempting to perform referral for user /o=First Organization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=36450f4551244feb9599628593b7dd92-ocs28 on server 567847ac-45e6-44e1-8bfc-2857bc211b30@mydomain.net.
    We got the address book server successfully.

    Additional Details

    The server returned by the Referral service: 567847ac-45e6-44e1-8bfc-2857bc211b30@mydomain.net
    Elapsed Time: 2567 ms.
    Testing the MAPI Address Book endpoint on the Exchange server.
    The address book endpoint was tested successfully.

    Additional Details

    Elapsed Time: 1045 ms.

    Test Steps

    Attempting to ping the MAPI Address Book endpoint with identity: 567847ac-45e6-44e1-8bfc-2857bc211b30@mydomain.net:6004.
    The endpoint was pinged successfully.

    Additional Details

    The endpoint responded in 261 ms.
    Elapsed Time: 248 ms.
    Testing the address book "Check Name" operation for user support@mydomain.net against server 567847ac-45e6-44e1-8bfc-2857bc211b30@mydomain.net.
    Check Name succeeded.

    Additional Details

    DisplayName: HD Support, LegDN: /o=First Organization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=36450f4551244feb9599628593b7dd92-ocs28
    Elapsed Time: 797 ms.
    Testing the MAPI Mail Store endpoint on the Exchange server.
    We successfully tested the Mail Store endpoint.

    Additional Details

    Elapsed Time: 5243 ms.

    Test Steps

    Attempting to ping the MAPI Mail Store endpoint with identity: 567847ac-45e6-44e1-8bfc-2857bc211b30@mydomain.net:6001.
    The endpoint was pinged successfully.

    Additional Details

    The endpoint responded in 625 ms.
    Elapsed Time: 4619 ms.
    Attempting to log on to the Mailbox.
    We were able to log on to the Mailbox.

    Additional Details

    Elapsed Time: 623 ms.

    Thanks,

    D.

    Wednesday, November 15, 2017 12:03 PM
  • Thank you for the update. The connectivity test result looks fine. 

    Are there any other mailboxes affected by the same issue?

    >>It used to work until a few weeks ago (we installed the same mailbox onto different computers). 

    Can you still access the mailbox without issue on these other computers?

    Do you have any other version of Outlook in your environment? If so, we can also try to configure this mailbox in a different version of Outlook and see whether this issue continues.

    Regards,

    Steve Fan


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

    Wednesday, November 22, 2017 6:56 AM
    Moderator
  • The XML returned has several domain names that your outlook client might not be able to reach:

    <ASUrl>https://winhexfeeu1.win.mail/EWS/Exchange.asmx</ASUrl>
    <OOFUrl>https://winhexfeeu1.win.mail/EWS/Exchange.asmx</OOFUrl>
    <OABUrl>https://1.exchange.1and1.eu/OAB/c8485a5f-8a49-4500-920b-23c16c5b435f/</OABUrl>
    <UMUrl>https://winhexfeeu1.win.mail/EWS/UM2007Legacy.asmx</UMUrl>
    <Port>0</Port>
    <DirectoryPort>0</DirectoryPort>
    <ReferralPort>0</ReferralPort>
    <AuthPackage>Anonymous</AuthPackage>
    <PublicFolderServer>1.exchange.1and1.eu</PublicFolderServer>
    <AD>winhexadeu1.win.mail</AD>
    <EwsUrl>https://winhexfeeu1.win.mail/EWS/Exchange.asmx</EwsUrl>
    <EmwsUrl>https://winhexfeeu1.win.mail/EWS/Exchange.asmx</EmwsUrl>
    <EcpUrl>https://winhexfeeu1.win.mail/ecp/</EcpUrl>

    Note that Outlook does need EWS access for many functions.  If Outlook is unable to reach EWS, you will have issues.

    I would make sure that ALL the URLs in the XML are reachable.

    Regards,
    -Eriq

    You might also try our free AutoDiscover testing tool. 
    AutoDiscover Test Tool

    It lets you control more of the way AutoDiscover works.  For example, i notice that the XML returned is NOT one that supports mapiHTTP.  

    Exchange 2013 provides mapiHTTP since SP1, but it is not enabled by default.  It might be worth asking 1and1 if such is expected to be enabled.



    -Eriq VanBibber, CTO, Priasoft Inc.


    Friday, December 8, 2017 9:20 PM