Well Ill try to keep this as simple as it should

I had a exchange server and i was preparing it for a Casarray. so i created the casarray.domain.local and add the server original name to that array. Then I made the DNS records for the cassarray internally and externally. So, When i try to use autodiscover I got another certrificate that is not the one i want.

By the other hand if i test manually the outlook anywhere for mail.domain.com and then test using the ms remote connectivity: I've got this:

	Attempting to ping RPC endpoint 6001 (Exchange Information Store) on server correo.manapro.com.
	The attempt to ping the endpoint failed.
	<label for="testSelectWizard_ctl12_ctl06_ctl07_tmmArrow">Tell me more about this issue and how to resolve it</label>
	Additional Details   The RPC_S_SERVER_UNAVAILABLE error (0x6ba) was thrown by the RPC Runtime process I had searched and tested all already but I'm stuck... I cant figure it out what's wrong.

The server is MS Exchange 2010, TMG 2010 SP2, clients' PC running W7/W8

• Edited by j0rt3g4 Monday, July 01, 2013 5:08 PM

How did you create casarray.domain.local on the Internet?

Hello,

If you need to access you mailbox from internet, you need to register A record for public domain name and A record for autodiscover.

Here is the article for your reference.

RPC Server Unavailable Error was Thrown by the RPC Runtime

http://technet.microsoft.com/en-us/library/db543644-c252-47ee-a70b-4f60770083dc.aspx

Additional articles for your reference.

Demystifying the CAS Array Object - Part 1

http://blogs.technet.com/b/exchange/archive/2012/03/23/demystifying-the-cas-array-object-part-1.aspx

Demystifying the CAS Array Object - Part 2

http://blogs.technet.com/b/exchange/archive/2012/03/28/demystifying-the-cas-array-object-part-2.aspx

The solution in that case was quite simple, We have a certificate configure in the front end, but the certificate in the backend was different, So we go to the IIS configuration, navigate into the default web site and check that the certificate for the front end was the same that the backend and that's it.

The detailed information can be see in my blog, and I'm sorry for the delayed answer

http://mcsemessaging.blogspot.mx/2014/12/blank-screen-after-login-via-owa-in.html