Externer Zugriff via Autodiscover - Problem

  • Hallo Norbert,

    Meinte anwählen, anhaken, markieren... :) Wenn ich dies nicht mache, kommen folgende Meldungen:

    Quellcode

    1. Attempting the Autodiscover and Exchange ActiveSync test (if requested).
    2. Testing of Autodiscover for Exchange ActiveSync failed.
    3. Additional Details
    4. Elapsed Time: 6502 ms.
    5. Test Steps
    6. Attempting each method of contacting the Autodiscover service.
    7. The Autodiscover service couldn't be contacted successfully by any method.
    8. Additional Details
    9. Elapsed Time: 6502 ms.
    10. Test Steps
    11. Attempting to test potential Autodiscover URL https://XXX.at:443/Autodiscover/Autodiscover.xml
    12. Testing of this potential Autodiscover URL failed.
    13. Additional Details
    14. Elapsed Time: 2937 ms.
    15. Test Steps
    16. Attempting to resolve the host name XXX.at in DNS.
    17. The host name resolved successfully.
    18. Additional Details
    19. IP addresses returned: XX.XXX.XXX.99
    20. Elapsed Time: 1261 ms.
    21. Testing TCP port 443 on host XXX.at to ensure it's listening and open.
    22. The port was opened successfully.
    23. Additional Details
    24. Elapsed Time: 915 ms.
    25. Testing the SSL certificate to make sure it's valid.
    26. The SSL certificate failed one or more certificate validation checks.
    27. Additional Details
    28. Elapsed Time: 760 ms.
    29. Test Steps
    30. The Microsoft Connectivity Analyzer is attempting to obtain the SSL certificate from remote server XXX.at on port 443.
    31. The Microsoft Connectivity Analyzer successfully obtained the remote SSL certificate.
    32. Additional Details
    33. Remote Certificate Subject: CN=www.XXX.eu, OU=IT, O=XXX GmbH, C=AT, OID.2.5.4.15=Private Organization, OID.1.3.6.1.4.1.311.60.2.1.3=AT, SERIALNUMBER=381011k, Issuer: CN=COMODO RSA Extended Validation Secure Server CA, O=COMODO CA Limited, L=Salford, S=Greater Manchester, C=GB.
    34. Elapsed Time: 732 ms.
    35. Validating the certificate name.
    36. Certificate name validation failed.
    37. Tell me more about this issue and how to resolve it
    38. Additional Details
    39. Host name XXX.at doesn't match any name found on the server certificate CN=www.XXX.eu, OU=IT, O=XXX GmbH,C=AT, OID.2.5.4.15=Private Organization, OID.1.3.6.1.4.1.311.60.2.1.3=AT, SERIALNUMBER=381011k.
    40. Elapsed Time: 0 ms.
    41. Attempting to test potential Autodiscover URL https://autodiscover.XXX.at:443/Autodiscover/Autodiscover.xml
    42. Testing of this potential Autodiscover URL failed.
    43. Additional Details
    44. Elapsed Time: 2047 ms.
    45. Test Steps
    46. Attempting to resolve the host name autodiscover.XXX.at in DNS.
    47. The host name resolved successfully.
    48. Additional Details
    49. IP addresses returned: XX.XX.XX.241
    50. Elapsed Time: 774 ms.
    51. Testing TCP port 443 on host autodiscover.XXX.at to ensure it's listening and open.
    52. The port was opened successfully.
    53. Additional Details
    54. Elapsed Time: 611 ms.
    55. Testing the SSL certificate to make sure it's valid.
    56. The SSL certificate failed one or more certificate validation checks.
    57. Additional Details
    58. Elapsed Time: 662 ms.
    59. Test Steps
    60. The Microsoft Connectivity Analyzer is attempting to obtain the SSL certificate from remote server autodiscover.XXX.at on port 443.
    61. The Microsoft Connectivity Analyzer successfully obtained the remote SSL certificate.
    62. Additional Details
    63. Remote Certificate Subject: CN=autodiscover.XXX.at, OU=HRA, O=XXX GmbH, C=AT, Issuer: CN=hr-net-HR-S001-CA, DC=hr-net, DC=local.
    64. Elapsed Time: 620 ms.
    65. Validating the certificate name.
    66. The certificate name was validated successfully.
    67. Additional Details
    68. Host name autodiscover.XXX.at was found in the Certificate Subject Common name.
    69. Elapsed Time: 0 ms.
    70. Certificate trust is being validated.
    71. Certificate trust validation failed.
    72. Test Steps
    73. The Microsoft Connectivity Analyzer is attempting to build certificate chains for certificate CN=autodiscover.XXX.at, OU=HRA, O=XXX GmbH,C=AT.
    74. A certificate chain couldn't be constructed for the certificate.
    75. Tell me more about this issue and how to resolve it
    76. Additional Details
    77. The certificate chain didn't end in a trusted root. Root = CN=hr-net-HR-S001-CA, DC=hr-net, DC=local
    78. Elapsed Time: 15 ms.
    79. Attempting to contact the Autodiscover service using the HTTP redirect method.
    80. The attempt to contact Autodiscover using the HTTP Redirect method failed.
    81. Additional Details
    82. Elapsed Time: 782 ms.
    83. Test Steps
    84. Attempting to resolve the host name autodiscover.XXX.at in DNS.
    85. The host name resolved successfully.
    86. Additional Details
    87. IP addresses returned: XX.XX.XX.241
    88. Elapsed Time: 8 ms.
    89. Testing TCP port 80 on host autodiscover.XXX.at to ensure it's listening and open.
    90. The port was opened successfully.
    91. Additional Details
    92. Elapsed Time: 193 ms.
    93. The Microsoft Connectivity Analyzer is checking the host autodiscover.XXX.at for an HTTP redirect to the Autodiscover service.
    94. The Microsoft Connectivity Analyzer failed to get an HTTP redirect response for Autodiscover.
    95. Additional Details
    96. 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).
    97. HTTP Response Headers:
    98. X-SOAP-Enabled: True
    99. X-WSSecurity-Enabled: False
    100. X-WSSecurity-For: None
    101. Cache-Control: private
    102. Content-Type: text/html;charset=ISO-8859-1
    103. Date: Wed, 17 Aug 2016 10:55:55 GMT
    104. Server: Apache
    105. WWW-Authenticate: NTLM,Negotiate,Basic realm="autodiscover.XXX.at"
    106. X-AspNet-Version: 2.0.50727
    107. X-Powered-By: ASP.NET
    108. Vary: Accept-Encoding
    109. Content-Length: 107
    110. Keep-Alive: timeout=15, max=100
    111. Connection: Keep-Alive
    112. Elapsed Time: 580 ms.
    113. Attempting to contact the Autodiscover service using the DNS SRV redirect method.
    114. The Microsoft Connectivity Analyzer failed to contact the Autodiscover service using the DNS SRV redirect method.
    115. Additional Details
    116. Elapsed Time: 486 ms.
    117. Test Steps
    118. Attempting to locate SRV record _autodiscover._tcp.XXX.at in DNS.
    119. The Autodiscover SRV record wasn't found in DNS.
    120. Tell me more about this issue and how to resolve it
    121. Additional Details
    122. Elapsed Time: 486 ms.
    123. Checking if there is an autodiscover CNAME record in DNS for your domain 'XXX.at' for Office 365.
    124. Failed to validate autodiscover CNAME record in DNS. If your mailbox isn't in Office 365, you can ignore this warning.
    125. Tell me more about this issue and how to resolve it
    126. Additional Details
    127. There is no Autodiscover CNAME record for your domain 'XXX.at'.
    128. Elapsed Time: 247 ms.
    Alles anzeigen

    Nein ich teste es über einen iPhone Hotspot / WLAN Hotspot an einem Laptop (Domänenmitglied) mit dem Netzbetreiber Drei Hutchison AT.

    LG

    Dieser Beitrag wurde bereits 1 mal editiert, zuletzt von floret88 ()

  • Guten Abend,

    Es ist zum Haare raufen... :P

    Mittlerweile bin ich so weit gekommen und habe herausgefunden, dass wenn ich mich mittels DOMÄNE\Benutzername anmelde der Verbindungsaufbau zur autodiscover.xml funktioniert.
    So bald ich aber extern mich über die E-Mail Adresse anmelden möchte - was auch Outlook 2016 bei mir standardmäßig macht - ist die Verbindung fehlgeschlagen.

    Habe nun die Benutzer einmal auf UPN eingestellt. Teste morgen, ob es dann funktioniert und gebe Euch Bescheid!

    LG

    Dieser Beitrag wurde bereits 3 mal editiert, zuletzt von floret88 ()