• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 890
  • Last Modified:

RPC over HTTPS disconnected

Hello guys

I have an issue with my outlook 2010 clients getting disconnected when they are on Outlook Anywhere. The Exchange server is an SBS2008 server. I have done a exchange Connectivity Test and here is the result. Can anyone shed some light as to what can be wrong? I have also disabled firewall settings on the SBS server and it has also no effect.


      Connectivity Test Failed
Test Details

      Testing RPC/HTTP connectivity.
       The RPC/HTTP test failed.
      Test Steps
      Attempting to resolve the host name mx.homegreen.com.au in DNS.
       The host name resolved successfully.
      Additional Details
       IP addresses returned:
      Testing TCP port 443 on host mx.homegreen.com.au to ensure it's listening and open.
       The port was opened successfully.
      Testing the SSL certificate to make sure it's valid.
       The certificate passed all validation requirements.
      Test Steps
      The Microsoft Connectivity Analyzer is attempting to obtain the SSL certificate from remote server mx.homegreen.com.au on port 443.
       The Microsoft Connectivity Analyzer successfully obtained the remote SSL certificate.
      Additional Details
       Remote Certificate Subject: CN=homegreen.com.au, OU=Domain Control Validated, Issuer: SERIALNUMBER=07969287, CN=Go Daddy Secure Certification Authority, OU=http://certificates.godaddy.com/repository, O="GoDaddy.com, Inc.", L=Scottsdale, S=Arizona, C=US.
      Validating the certificate name.
       The certificate name was validated successfully.
      Additional Details
       Host name mx.homegreen.com.au was found in the Certificate Subject Alternative Name entry.
      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=homegreen.com.au, 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 OU=Go Daddy Class 2 Certification Authority, O="The Go Daddy Group, Inc.", C=US.
      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.
      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/27/2013 4:07:35 AM, NotAfter = 9/27/2016 4:07:35 AM
      Checking the IIS configuration for client certificate authentication.
       Client certificate authentication wasn't detected.
      Additional Details
       Accept/Require Client Certificates isn't configured.
      Testing HTTP Authentication Methods for URL https://mx.homegreen.com.au/rpc/rpcproxy.dll?w2k8sbs.hgreen.local: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
      Testing SSL mutual authentication with the RPC proxy server.
       The test passed with some warnings encountered. Please expand the additional details.
        Tell me more about this issue and how to resolve it
      Additional Details
       The certificate common name homegreen.com.au doesn't match the mutual authentication string provided mx.homegreen.com.au; however, a match was found in the subject alternative name extension.
      Attempting to ping RPC proxy mx.homegreen.com.au.
       RPC Proxy can't be pinged.
      Additional Details
       A Web exception occurred because an HTTP 404 - NotFound response was received from IIS7.
Headers received:
Content-Length: 1245
Content-Type: text/html
Date: Mon, 30 Sep 2013 05:22:25 GMT
Server: Microsoft-IIS/7.0
X-Powered-By: ASP.NET

© 2013 Microsoft | Version 2.6 | Feedback | Privacy | Terms of Use
  • 2
1 Solution
Shreedhar EtteCommented:
Please refer this article and verfiy your settings:
OZSGAuthor Commented:
Hi Shreedar unfortunately the settings changes made it worse as suddenly my OWA and Active Sync was not working. I ended up calling MS in as it was getting serious fast and I got to know that there were more things wrong with it like the RPC and RPC cert directory in IIS were in the wrong website and application group.

Whoever build this server made sure made a mess of it to begin with.
OZSGAuthor Commented:
Not the answer that solved the question but did point me to the right direction to start looking. Unfortunately it caused more issues after I made the recommended changes unknowingly there were more serious issues underneath the server setup as a whole.

Called MS to resolve.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: SSL Checker

Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now