Schramek_C

sorry, es ist 2013. nicht 2010. Kann ich den Betreff ändern?

Ja Server ist aktuell. .net passt auch. folgende Info habe ich heute von dem internen Techniker bekommen: Das zertifikat wurde getauscht folgenden Fehler habe ich gefunden. Verbund- oder Authentifizierungszertifikat nicht gefunden: E4D7098B4AFFEC3DDB263C79849839A6C8068604. Das Zertifikat wurde am lokalen sowie an benachbarten Standorten nicht gefunden. Bestätigen Sie, dass das Zertifikat in Ihrer Topologie vorhanden ist, und setzen Sie das Zertifikat bei Bedarf bei der Verbundvertrauensstellung mithilfe von 'Set-FederationTrust' oder 'Set-AuthConfig' auf ein gültiges Zertifikat zurück. Die Übermittlung des Zertifikats an den lokalen oder die benachbarten Standorte benötigt möglicherweise etwas Zeit. Event ID: 2005

Hallo, ich habe ein Problem mit einen Exchange 2013. Folgendes Problem: Ich kann keine externen geräte mehr verbinden. hier der Log von dem Test: The Microsoft Connectivity Analyzer is testing Exchange ActiveSync. The Exchange ActiveSync test failed. Additional Details Elapsed Time: 19481 ms. Test Steps Attempting to resolve the host name mail.orthoxxxxx.net in DNS. The host name resolved successfully. Additional Details IP addresses returned: 80.123.xxx.xx Elapsed Time: 19 ms. Testing TCP port 443 on host mail.orthoxxxxx.net to ensure it's listening and open. The port was opened successfully. Additional Details Elapsed Time: 56 ms. Testing the SSL certificate to make sure it's valid. The certificate passed all validation requirements. Additional Details Elapsed Time: 144 ms. Test Steps The Microsoft Connectivity Analyzer is attempting to obtain the SSL certificate from remote server mail.orthoxxxxx.net on port 443. The Microsoft Connectivity Analyzer successfully obtained the remote SSL certificate. Additional Details Remote Certificate Subject: CN=orthoxxxxx.net, OU=Domain Control Validated, Issuer: CN=GlobalSign Domain Validation CA - SHA256 - G2, O=GlobalSign nv-sa, C=BE. Elapsed Time: 92 ms. Validating the certificate name. The certificate name was validated successfully. Additional Details Host name mail.orthoxxxxx.net was found in the Certificate Subject Alternative Name entry. Elapsed Time: 0 ms. Validating certificate trust for Windows Mobile devices. 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=orthoxxxxx.net, OU=Domain Control Validated. 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=GlobalSign Root CA, OU=Root CA, O=GlobalSign nv-sa, C=BE. Elapsed Time: 18 ms. Analyzing the certificate chains for compatibility problems with Windows Phone devices. No Windows Phone compatibility problems were identified. Additional Details The certificate is trusted for Windows Mobile 5.0 and later versions. Root = CN=GlobalSign Root CA, OU=Root CA, O=GlobalSign nv-sa, C=BE Elapsed Time: 1 ms. The Microsoft Connectivity Analyzer is analyzing intermediate certificates sent by the remote server. All intermediate certificates are present and valid. Additional Details All intermediate certificates were present and valid. 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 = 9/25/2017 1:43:37 PM, NotAfter = 9/26/2019 1:43:37 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: 45 ms. Testing HTTP Authentication Methods for URL https://mail.orthoxxxxx.net/Microsoft-Server-ActiveSync/. The HTTP authentication methods are correct. Additional Details The Microsoft Connectivity Analyzer found all expected authentication methods and no disallowed methods. Methods found: Basic HTTP Response Headers: request-id: 1ea84280-a99c-4f17-9e10-3836120c1ce4 X-FEServer: SRV01 Content-Length: 0 Date: Mon, 02 Oct 2017 05:58:34 GMT Server: Microsoft-IIS/8.0 WWW-Authenticate: Basic realm="mail.orthoxxxxxxx.net" X-Powered-By: ASP.NET Elapsed Time: 136 ms. An ActiveSync session is being attempted with the server. Errors were encountered while testing the Exchange ActiveSync session. Additional Details Elapsed Time: 19078 ms. Test Steps Attempting to send the OPTIONS command to the server. Testing of the OPTIONS command failed. For more information, see Additional Details. Additional Details An HTTP 403 forbidden response was received. The response appears to have come from IIS7. Body of the response: <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"> <head> <title>IIS 8.0 Detaillierter Fehler - 403.0 - Forbidden</title> <style type="text/css"> <!-- body{margin:0;font-size:.7em;font-family:Verdana,Arial,Helvetica,sans-serif;} code{margin:0;color:#006600;font-size:1.1em;font-weight:bold;} .config_source code{font-size:.8em;color:#000000;} pre{margin:0;font-size:1.4em;word-wrap:break-word;} ul,ol{margin:10px 0 10px 5px;} ul.first,ol.first{margin-top:5px;} fieldset{padding:0 15px 10px 15px;word-break:break-all;} .summary-container fieldset{padding-bottom:5px;margin-top:4px;} legend.no-expand-all{padding:2px 15px 4px 10px;margin:0 0 0 -12px;} legend{color:#333333;;margin:4px 0 8px -12px;_margin-top:0px; font-weight:bold;font-size:1em;} a:link,a:visited{color:#007EFF;font-weight:bold;} a:hover{text-decoration:none;} h1{font-size:2.4em;margin:0;color:#FFF;} h2{font-size:1.7em;margin:0;color:#CC0000;} h3{font-size:1.4em;margin:10px 0 0 0;color:#CC0000;} h4{font-size:1.2em;margin:10px 0 5px 0; }#header{width:96%;margin:0 0 0 0;padding:6px 2% 6px 2%;font-family:"trebuchet MS",Verdana,sans-serif; color:#FFF;background-color:#5C87B2; }#content{margin:0 0 0 2%;position:relative;} .summary-container,.content-container{background:#FFF;width:96%;margin-top:8px;padding:10px;position:relative;} .content-container p{margin:0 0 10px 0; }#details-left{width:35%;float:left;margin-right:2%; }#details-right{width:63%;float:left;overflow:hidden; }#server_version{width:96%;_height:1px;min-height:1px;margin:0 0 5px 0;padding:11px 2% 8px 2%;color:#FFFFFF; background-color:#5A7FA5;border-bottom:1px solid #C1CFDD;border-top:1px solid #4A6C8E;font-weight:normal; font-size:1em;color:#FFF;text-align:right; }#server_version p{margin:5px 0;} table{margin:4px 0 4px 0;width:100%;border:none;} td,th{vertical-align:top;padding:3px 0;text-align:left;font-weight:normal;border:none;} th{width:30%;text-align:right;padding-right:2%;font-weight:bold;} thead th{background-color:#ebebeb;width:25%; }#details-right th{width:20%;} table tr.alt td,table tr.alt th{} .highlight-code{color:#CC0000;font-weight:bold;font-style:italic;} .clear{clear:both;} .preferred{padding:0 5px 2px 5px;font-weight:normal;background:#006633;color:#FFF;font-size:.8em;} --> </style> </head> <body> <div id="content"> <div class="content-container"> <h3>HTTP-Fehler 403.0 - Forbidden</h3> <h4>Sie sind nicht berechtigt, dieses Verzeichnis oder diese Seite anzuzeigen.</h4> </div> <div class="content-container"> <fieldset><h4>Wahrscheinlichste Ursachen:</h4> <ul> <li>Dabei handelt es sich um den generischen Fehler 403. Der Benutzer ist dazu nicht autorisiert, die Seite anzuzeigen.</li> </ul> </fieldset> </div> <div class="content-container"> <fieldset><h4>Mögliche Vorgehensweise:</h4> <ul> <li>Erstellen Sie eine Ablaufverfolgungsregel für Anforderungsfehler für diesen HTTP-Statuscode. Weitere Informationen zum Erstellen von Überwachungsregeln für Anforderungsfehler finden Sie <a href="http://go.microsoft.com/fwlink/?LinkID=66439">hier</a>. </li> </ul> </fieldset> </div> <div class="content-container"> <fieldset><h4>Detaillierte Fehlerinformationen:</h4> <div id="details-left"> <table border="0" cellpadding="0" cellspacing="0"> <tr class="alt"><th>Modul</th><td> ManagedPipelineHandler</td></tr> <tr><th>Benachrichtigung</th><td> ExecuteRequestHandler</td></tr> <tr class="alt"><th>Handler</th><td> AirSyncHandler</td></tr> <tr><th>Fehlercode</th><td> 0x00000000</td></tr> </table> </div> <div id="details-right"> <table border="0" cellpadding="0" cellspacing="0"> <tr class="alt"><th>Angeforderte URL</th><td> https://srv01.orthoxxxxx.local:444/Microsoft-Server-ActiveSync/Proxy/default.eas</td></tr> <tr><th>Physischer Pfad</th><td> E:\Programme\Exchange Server V15\ClientAccess\sync\Proxy\default.eas</td></tr> <tr class="alt"><th>Anmeldemethode</th><td> Basic</td></tr> <tr><th>Benutzeranmeldung</th><td> orthoxxxxx\Administrator</td></tr> </table> <div class="clear"></div> </div> </fieldset> </div> <div class="content-container"> <fieldset><h4>Weitere Informationen:</h4> Der generische Fehler 403 weist darauf hin, dass der authentifizierte Benutzer nicht autorisiert ist, die angeforderte Ressource zu verwenden. Der Grund für den Fehler 403 sollte durch einen Unterstatuscode in den IIS-Protokolldateien angegeben werden. Sammeln Sie mithilfe der genannten Schritte weitere Informationen über die Fehlerquelle, falls kein Unterstatuscode vorhanden ist. <p><a href="http://go.microsoft.com/fwlink/?LinkID=62293&IIS70Error=403,0,0x00000000,9200">Weitere Informationen anzeigen »</a></p> </fieldset> </div> </div> </body> </html> HTTP Response Headers: request-id: 1f5e9151-15c3-4c3d-bade-54461a672e69 X-CalculatedBETarget: srv01.orthoxxxxx.local X-MS-BackOffDuration: L/-470 X-DiagInfo: SRV01 X-BEServer: SRV01 X-FEServer: SRV01 Content-Length: 5076 Cache-Control: private Content-Type: text/html; charset=utf-8 Date: Mon, 02 Oct 2017 05:58:53 GMT Set-Cookie: X-BackEndCookie=S-1-5-21-3522320100-2819747638-3160837974-500=u56Lnp2ejJqBncuZxsmdm8/SnM+eyNLLxsyb0sfHz87Sy53MzZyZy8/GycnPgYHOztDPztDNz87I38/KxcrHxcrM; expires=Wed, 01-Nov-2017 04:58:53 GMT; path=/Microsoft-Server-ActiveSync; secure; HttpOnly Server: Microsoft-IIS/8.0 X-AspNet-Version: 4.0.30319 X-Powered-By: ASP.NET Elapsed Time: 19078 ms. Hat jemand einen Rat für mich. bin gerade am Verzweifeln Danke