none
Outlook 2016 does not connect to Exchange 2016 RRS feed

  • Frage

  • Hello,

    I am using Exchange Server 2016 with Outlook 2016 clients. In Outlook I create an account and use the first offered option "Email Account" which should be used to connect an Outlook 2016 to an Exchange Server. Then I enter my name, e-mail address and password. After a click on Continue a Windows security window appears after a few seconds, which asks me to enter my password to the e-mail address. No matter what I enter here, it will not lead to a successful connection. I have already tried it with the domain user name and the domain in the following variants instead of the e-mail address:
    user
    domain\user
    user@domain.tld

    None of the variants is accepted. I also noticed that the autodiscover page of the Exchanges (https://autodiscover.domain.tld/autodisover/autodiscover.xml) behaves the same way. It is not possible to display the autodiscover.xml file, because no combination of username, domain and password is accepted.

    Setting up mobile phones like the iPhone worked fine. Also the connection via IMAP and SMTP works smoothly. All other functions of the Exchange Server seem to work fine.

    Can anyone guide me to solve this problem?

    Thanks and regards

    Dirk

    Freitag, 20. September 2019 06:42

Alle Antworten

  • Moin,

    da du im Deutschen Forum postest, antworte ich auf Deutsch

    Hört sich eigentlich nach Autodiscover-Problem an.

    Was sagt der Test von extern?
    https://testconnectivity.microsoft.com/

    ;)


    Gruß Norbert

    Freitag, 20. September 2019 08:28
    Moderator
  • Hallo Norbert,

    danke für die schnelle Antwort.

    Testconnectivity sagt:

    TL;DR;

    An HTTP 401 Unauthorized response was received from the remote Unknown server. This is usually the result of an incorrect username or password. If you are attempting to log onto an Office 365 service, ensure you are using your full User Principal Name (UPN).
    HTTP Response Headers:
    Connection: keep-alive
    request-id: 6db29eb0-62dc-42c0-b5a7-23e78c0f7d54
    X-CalculatedBETarget: mail1.ebel.local
    X-FEServer: MAIL1
    Content-Length: 0
    Cache-Control: private
    Date: Fri, 20 Sep 2019 09:26:27 GMT
    Server: Microsoft-IIS/10.0
    WWW-Authenticate: Basic realm="mail.domain.tld"
    X-AspNet-Version: 4.0.30319
    X-Powered-By: ASP.NET
    Elapsed Time: 425 ms.

    Und ja: ich benutze den richtigen Benutzernamen und das korrekte Passwort. Und es ist auch egal welchen Benutzernamen ich nehmen, ich bekomme keinen Zugang zur Autodiscover XML

    Hier der ganze Text:

    	Attempting to resolve the host name autodiscover.domain.tld in DNS.
     	The host name resolved successfully.
     	
    	Additional Details
     	
    IP addresses returned: 217.92.122.131
    Elapsed Time: 87 ms.
    	Testing TCP port 443 on host autodiscover.domain.tld to ensure it's listening and open.
     	The port was opened successfully.
     	
    	Additional Details
     	
    Elapsed Time: 73 ms.
    	Testing the SSL certificate to make sure it's valid.
     	The certificate passed all validation requirements.
     	
    	Additional Details
     	
    Elapsed Time: 117 ms.
     	
    	Test Steps
     	
    	The Microsoft Connectivity Analyzer is attempting to obtain the SSL certificate from remote server autodiscover.domain.tld on port 443.
     	The Microsoft Connectivity Analyzer successfully obtained the remote SSL certificate.
     	
    	Additional Details
     	
    Remote Certificate Subject: CN=*.domain.tld, Issuer: CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US.
    Elapsed Time: 92 ms.
    	Validating the certificate name.
     	The certificate name was validated successfully.
     	
    	Additional Details
     	
    The host name that was found, autodiscover.domain.tld, is a wildcard certificate match for common name *.domain.tld.
    Elapsed Time: 0 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 = 7/17/2019 4:37:49 AM, NotAfter = 10/15/2019 4:37:49 AM
    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: 206 ms.
    	Attempting to send an Autodiscover POST request to potential Autodiscover URLs.
     	Autodiscover settings weren't obtained when the Autodiscover POST request was sent.
     	
    	Additional Details
     	
    Elapsed Time: 425 ms.
     	
    	Test Steps
     	
    	The Microsoft Connectivity Analyzer is attempting to retrieve an XML Autodiscover response from URL https://autodiscover.domain.tld:443/Autodiscover/Autodiscover.xml for user d.hildebrand@domain.tld.
     	The Microsoft Connectivity Analyzer failed to obtain an Autodiscover XML response.
     	
    	Additional Details
     	
    An HTTP 401 Unauthorized response was received from the remote Unknown server. This is usually the result of an incorrect username or password. If you are attempting to log onto an Office 365 service, ensure you are using your full User Principal Name (UPN).
    HTTP Response Headers:
    Connection: keep-alive
    request-id: 6db29eb0-62dc-42c0-b5a7-23e78c0f7d54
    X-CalculatedBETarget: mail1.ebel.local
    X-FEServer: MAIL1
    Content-Length: 0
    Cache-Control: private
    Date: Fri, 20 Sep 2019 09:26:27 GMT
    Server: Microsoft-IIS/10.0
    WWW-Authenticate: Basic realm="mail.domain.tld"
    X-AspNet-Version: 4.0.30319
    X-Powered-By: ASP.NET
    Elapsed Time: 425 ms.



    • Bearbeitet VBK IT Freitag, 20. September 2019 09:34 Schreibfehler korrigiert
    Freitag, 20. September 2019 09:31
  • Ich sehe da immer den Server mail1.ebel.local - das passt nicht.

    ;)


    Gruß Norbert

    Freitag, 20. September 2019 10:11
    Moderator
  • Ich sehe da immer den Server mail1.ebel.local - das passt nicht.

    ;)


    Gruß Norbert

    Habe die Einstellungen geprüft:

    [PS] C:\Windows\system32>Get-ClientAccessService MAIL1 | fl
    
    
    RunspaceId                           : ab4053e9-03dd-4e57-9e88-8503bc4782cc
    Name                                 : MAIL1
    Fqdn                                 : Mail1.ebel.local
    ClientAccessArray                    :
    OutlookAnywhereEnabled               : True
    AutoDiscoverServiceCN                : Mail1
    AutoDiscoverServiceClassName         : ms-Exchange-AutoDiscover-Service
    AutoDiscoverServiceInternalUri       : https://autodiscover.domain.tld/Autodiscover/Autodiscover.xml
    AutoDiscoverServiceGuid              : 77378f46-2c66-4aa9-a6a6-3e7a48b19596
    AutoDiscoverSiteScope                : {Default-First-Site-Name}
    AlternateServiceAccountConfiguration :
    IsOutOfService                       : False
    Identity                             : MAIL1
    IsValid                              : True
    ExchangeVersion                      : 0.1 (8.0.535.0)
    DistinguishedName                    : CN=MAIL1,CN=Servers,CN=Exchange Administrative Group
                                           (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=First Organization,CN=Microsoft
                                           Exchange,CN=Services,CN=Configuration,DC=ebel,DC=local
    Guid                                 : 11d91026-1530-4be1-b296-753d2bd2df06
    ObjectCategory                       : ebel.local/Configuration/Schema/ms-Exch-Exchange-Server
    ObjectClass                          : {top, server, msExchExchangeServer}
    WhenChanged                          : 19.09.2019 14:34:59
    WhenCreated                          : 15.04.2019 12:26:42
    WhenChangedUTC                       : 19.09.2019 12:34:59
    WhenCreatedUTC                       : 15.04.2019 10:26:42
    OrganizationId                       :
    Id                                   : MAIL1
    OriginatingServer                    : DC1.ebel.local
    ObjectState                          : Unchanged

    Soweit ich das verstehe passt das.

    Freitag, 20. September 2019 11:53