We are in the process of setting up our migration by doing a cut over exchange migration.

 

While setting it up and testing using the outlook anywhere setup, we ran into a problem and got the The RPC_S_SERVER_UNAVAILABLE   error while using the exchange connectivity tester. 

 

Description: https://www.testexchangeconnectivity.com/Images/Error.png

Testing RPC/HTTP connectivity.

 

The RPC/HTTP test failed.

 

Description: https://www.testexchangeconnectivity.com/Images/Minus.gif

Test Steps

 

Description: https://www.testexchangeconnectivity.com/Images/Success.png

Attempting to resolve the host name mail.cdpl.org in DNS.

 

The host name resolved successfully.

 

Description: https://www.testexchangeconnectivity.com/Images/Minus.gif

Additional Details

 

IP addresses returned: 24.106.185.202

 

Description: https://www.testexchangeconnectivity.com/Images/Success.png

Testing TCP port 443 on host mail.cdpl.org to ensure it's listening and open.

 

The port was opened successfully.

 

Description: https://www.testexchangeconnectivity.com/Images/Success.png

Testing the SSL certificate to make sure it's valid.

 

The certificate passed all validation requirements.

 

Description: https://www.testexchangeconnectivity.com/Images/Minus.gif

Test Steps

 

Description: https://www.testexchangeconnectivity.com/Images/Success.png

ExRCA is attempting to obtain the SSL certificate from remote server mail.cdpl.org on port 443.

 

ExRCA successfully obtained the remote SSL certificate.

 

Description: https://www.testexchangeconnectivity.com/Images/Minus.gif

Additional Details

 

Remote Certificate Subject: CN=mail.cdpl.org, OU=Domain Control Validated, O=mail.cdpl.org, Issuer: SERIALNUMBER=10688435, CN=Starfield Secure Certification Authority, OU=http://certificates.starfieldtech.com/repository, O="Starfield Technologies, Inc.", L=Scottsdale, S=Arizona, C=US.

 

Description: https://www.testexchangeconnectivity.com/Images/Success.png

Validating the certificate name.

 

The certificate name was validated successfully.

 

Description: https://www.testexchangeconnectivity.com/Images/Minus.gif

Additional Details

 

Host name mail.cdpl.org was found in the Certificate Subject Common name.

 

Description: https://www.testexchangeconnectivity.com/Images/Success.png

Certificate trust is being validated.

 

The certificate is trusted and all certificates are present in the chain.

 

Description: https://www.testexchangeconnectivity.com/Images/Minus.gif

Test Steps

 

Description: https://www.testexchangeconnectivity.com/Images/Success.png

ExRCA is attempting to build certificate chains for certificate CN=mail.cdpl.org, OU=Domain Control Validated, O=mail.cdpl.org.

 

One or more certificate chains were constructed successfully.

 

Description: https://www.testexchangeconnectivity.com/Images/Minus.gif

Additional Details

 

A total of 2 chains were built. The highest quality chain ends in root certificate OU=Starfield Class 2 Certification Authority, O="Starfield Technologies, Inc.", C=US.

 

Description: https://www.testexchangeconnectivity.com/Images/Success.png

Analyzing the certificate chains for compatibility problems with versions of Windows.

 

No Windows compatibility problems were identified.

 

Description: https://www.testexchangeconnectivity.com/Images/Minus.gif

Additional Details

 

The certificate chain has been validated up to a trusted root. Root = E=info@valicert.com, CN=http://www.valicert.com/, OU=ValiCert Class 2 Policy Validation Authority, O="ValiCert, Inc.", L=ValiCert Validation Network.

 

Description: https://www.testexchangeconnectivity.com/Images/Success.png

Testing the certificate date to confirm the certificate is valid.

 

Date validation passed. The certificate hasn't expired.

 

Description: https://www.testexchangeconnectivity.com/Images/Minus.gif

Additional Details

 

The certificate is valid. NotBefore = 4/11/2012 5:38:32 PM, NotAfter = 4/11/2013 5:38:32 PM

 

Description: https://www.testexchangeconnectivity.com/Images/Success.png

Checking the IIS configuration for client certificate authentication.

 

Client certificate authentication wasn't detected.

 

Description: https://www.testexchangeconnectivity.com/Images/Minus.gif

Additional Details

 

Accept/Require Client Certificates isn't configured.

 

Description: https://www.testexchangeconnectivity.com/Images/Success.png

Testing HTTP Authentication Methods for URL https://mail.cdpl.org/rpc/rpcproxy.dll.

 

The HTTP authentication methods are correct.

 

Description: https://www.testexchangeconnectivity.com/Images/Minus.gif

Additional Details

 

ExRCA found all expected authentication methods and no disallowed methods. Methods found: Basic

 

Description: https://www.testexchangeconnectivity.com/Images/Success.png

Testing SSL mutual authentication with the RPC proxy server.

 

Mutual authentication was verified successfully.

 

Description: https://www.testexchangeconnectivity.com/Images/Minus.gif

Additional Details

 

Certificate common name mail.cdpl.org matches msstd:mail.cdpl.org.

 

Description: https://www.testexchangeconnectivity.com/Images/Success.png

Attempting to ping RPC proxy mail.cdpl.org.

 

RPC Proxy was pinged successfully.

 

Description: https://www.testexchangeconnectivity.com/Images/Minus.gif

Additional Details

 

Completed with HTTP status 200 - OK

 

Description: https://www.testexchangeconnectivity.com/Images/Error.png

Attempting to ping RPC endpoint 6001 (Exchange Information Store) on server mail.cdpl.org.

 

The attempt to ping the endpoint failed.

 

Description: https://www.testexchangeconnectivity.com/Images/GreenRtArrow.jpg Tell me more about this issue and how to resolve it

 

Description: https://www.testexchangeconnectivity.com/Images/Minus.gif

Additional Details

 

The RPC_S_SERVER_UNAVAILABLE error (0x6ba) was thrown by the RPC Runtime process.

 

Open Registry Editor on the Client Access server or on the front-end server, and verify that the ValidPorts registry value exists under HKEY_LOCAL_MACHINE\Software\Microsoft\Rpc\Rpcproxy. Also confirm that the key includes the NetBIOS and FQDN for all mailbox servers and for each required port (that is, for ports 6001, 6002, and 6004).

 

FORSETI:6001-6002;FORSETI:6004;forseti.cdpl.org:6001-6002;forseti.cdpl.org:6004 is the result.

The thing that I just noticed is that there is a difference in the old self signed certificate and the new one we just purchased.

 

old self signed certificate CertificateDomains : {forseti, forseti.CDPL.org}

 

New certificate CertificateDomains : {mail.cdpl.org, www.mail.cdpl.org}

 

Could that be the reason for the RPC over http failing?  Should I revise/replace the certificate  with the addition of the other names as well?

 

I am able to telnet into the ports.   This machine is the only server, so it is file, and exchange.

 

It is a server 2003 r2 server and exchange 2007 and is scheduled to be decommissioned this year.

  I have looked through the links here and haven't seen one with the same problem.    I am stumped.   I have tried the suggestions that have been posted in other threads without any luck.

 

Any help or suggestions would be appreciated.