troubleshooting Question

Connect to rpc directory

Avatar of mrodriques
mrodriquesFlag for United States of America asked on
ExchangeWindows Server 2003
13 Comments2 Solutions313 ViewsLast Modified:
I'm working on getting an Exchange 2003 server cut over to office 365.  I've installed and tested a certificate.  I've followed the guides for setting up RPC over http.  I can connect to OWA wither using SSL or not.

When I run an exchange connectivity test, I get an http authentication error.  If I try to browse to http(s)://mail.domainname.com/rpc I get a service unavailable screen.

I'm out of ideas here and would really like some suggestions.

I'd like to use the cutover migration rather than copying pst file because I have several remote users and export/import would severely slow the transition down.

Thanks in advance.

Results of the connectivity test...

Testing Outlook connectivity.
 The Outlook connectivity test failed.
 
Additional Details
 
Elapsed Time: 1498 ms.


 
Test Steps
 
Testing RPC over HTTP connectivity to server mail.kibel.com
 RPC over HTTP connectivity failed.
 
Additional Details
 
HTTP Response Headers:
Connection: close
Content-Length: 28
Content-Type: text/html
Date: Wed, 12 Nov 2014 21:27:04 GMT


Elapsed Time: 1498 ms.


 
Test Steps
 
Attempting to resolve the host name mail.kibel.com in DNS.
 The host name resolved successfully.
 
Additional Details
 
IP addresses returned: 100.38.142.34

Elapsed Time: 288 ms.



Testing TCP port 443 on host mail.kibel.com to ensure it's listening and open.
 The port was opened successfully.
 
Additional Details
 
Elapsed Time: 171 ms.



Testing the SSL certificate to make sure it's valid.
 The certificate passed all validation requirements.
 
Additional Details
 
Elapsed Time: 393 ms.


 
Test Steps
 
The Microsoft Connectivity Analyzer is attempting to obtain the SSL certificate from remote server mail.kibel.com on port 443.
 The Microsoft Connectivity Analyzer successfully obtained the remote SSL certificate.
 
Additional Details
 
Remote Certificate Subject: CN=mail.kibel.com, OU=Domain Control Validated, Issuer: CN=Go Daddy Secure Certificate Authority - G2, OU=http://certs.godaddy.com/repository/, O="GoDaddy.com, Inc.", L=Scottsdale, S=Arizona, C=US.

Elapsed Time: 338 ms.



Validating the certificate name.
 The certificate name was validated successfully.
 
Additional Details
 
Host name mail.kibel.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=mail.kibel.com, OU=Domain Control Validated.
 One or more certificate chains were constructed successfully.
 
Additional Details
 
A total of 2 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.

Elapsed Time: 20 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 = 11/11/2014 5:51:51 PM, NotAfter = 11/11/2015 5:51:51 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: 416 ms.



Testing HTTP Authentication Methods for URL https://mail.kibel.com/rpc/rpcproxy.dll?callisto.kibel.com:6002.
 The HTTP authentication test failed.
 
Additional Details
 
A Web exception occurred because an HTTP 503 - ServiceUnavailable response was received from Unknown.
HTTP Response Headers:
Connection: close
Content-Length: 28
Content-Type: text/html
Date: Wed, 12 Nov 2014 21:27:04 GMT


Elapsed Time: 227 ms.
ASKER CERTIFIED SOLUTION
Join our community to see this answer!
Unlock 2 Answers and 13 Comments.
Start Free Trial
Learn from the best

Network and collaborate with thousands of CTOs, CISOs, and IT Pros rooting for you and your success.

Andrew Hancock - VMware vExpert
See if this solution works for you by signing up for a 7 day free trial.
Unlock 2 Answers and 13 Comments.
Try for 7 days

”The time we save is the biggest benefit of E-E to our team. What could take multiple guys 2 hours or more each to find is accessed in around 15 minutes on Experts Exchange.

-Mike Kapnisakis, Warner Bros