Eu tenho o Exchange 2003 em execução em uma caixa do Windows Server 2003. Eu estou tentando usar o Microsoft Remote Connectivity Analyzer que está falhando com um erro ao tentar pingar RPC endpoint 6001 (Exchange Information Store)
Eu posso ver que muitas pessoas tiveram o mesmo problema, e eu tentei o seguinte conselho sem sucesso: (veja link )
Testing RPC/HTTP connectivity. The RPC/HTTP test failed. Additional Details Elapsed Time: 5670 ms.
Test Steps Attempting to resolve the host name owa.mycompany.com in DNS. The host name resolved successfully. Additional Details IP addresses returned: 199.203.XXX.XXX Elapsed Time: 15 ms.
Testing TCP port 443 on host owa.mycompany.com to ensure it's listening and open. The port was opened successfully. Additional Details Elapsed Time: 197 ms.
Testing the SSL certificate to make sure it's valid. The certificate passed all validation requirements. Additional Details Elapsed Time: 651 ms.
Test Steps The Microsoft Connectivity Analyzer is attempting to obtain the SSL certificate from remote server owa.mycompany.com on port 443. The Microsoft Connectivity Analyzer successfully obtained the remote SSL certificate. Additional Details Remote Certificate Subject: CN=owa.mycompany.com, OU=Domain Control Validated - RapidSSL(R), OU=See www.rapidssl.com/resources/cps (c)13, ..... Elapsed Time: 583 ms.
Validating the certificate name. The certificate name was validated successfully. Additional Details Host name owa.mycompany.com 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=owa.mycompany.com, OU=Domain Control Validated - RapidSSL(R), OU=See www.rapidssl.com/resources/cps (c)13, .... 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=GeoTrust Global CA, O=GeoTrust Inc., C=US. Elapsed Time: 33 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 = 7/23/2013 3:25:57 AM, NotAfter = 9/24/2014 1:35:21 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: 779 ms.
Testing HTTP Authentication Methods for URL https://owa.mycompany.com/rpc/rpcproxy.dll?mail.mycompany.com: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 Elapsed Time: 565 ms.
Testing SSL mutual authentication with the RPC proxy server. Mutual authentication was verified successfully. Additional Details Certificate common name owa.mycompany.com matches msstd:owa.mycompany.com. Elapsed Time: 0 ms.
Attempting to ping RPC proxy owa.mycompany.com. RPC Proxy was pinged successfully. Additional Details Completed with HTTP status 200 - OK Elapsed Time: 182 ms.
Attempting to ping RPC endpoint 6001 (Exchange Information Store) on server mail.mycompany.com. The attempt to ping the endpoint failed.
Tell me more about this issue and how to resolve it Additional Details The RPC_S_SERVER_UNAVAILABLE error (0x6ba) was thrown by the RPC Runtime process. Elapsed Time: 3279 ms.
Eu percebi qual era o problema. (Eu vi um problema semelhante em ligação )
Quando especifiquei manualmente as configurações do servidor, não coloquei o nome do host interno para o Exchange Server
(Eu também não apliquei todas as atualizações do Windows. Não tenho certeza se isso fez diferença)