Exchange 2013 Outlook Anywhere Issues

I have two Exchange servers in a coexistence environment.

1 x Exchange 2013 SP1 server with MB and CAS functionality.
1 x Exchange 2010 SP3 server with MB, HT, and CAS functionality.

I have successfully migrated my mail flow and CAS protocol functionality to the new 2013 server.  In performing the various tests on testconnectivity.microsoft.com, I have encountered the following error performing the Outlook Anywhere test, using autodiscover.  The test results are the same for mailboxes located on both the 2010 and 2013 servers.
Exchange-Connectivity-RPC-Failure.PNG
http://technet.microsoft.com/en-us/library/db543644-c252-47ee-a70b-4f60770083dc.aspx
Upon doing some research at the URL provided by the test results, here are my conclusions.

1. The frontend proxy can successfully resolve the hostname and NetBIOS name of both mailbox servers. On the 2013 server, the mailbox server and frontend are on the same server.
2.  The value for my "ValidPorts" registry key is "SERVERNAME:593;SERVERNAME:49152-65535"
3.  Here are my telnet results from the frontend proxy to the mailbox server (same server) with firewall disabled.
     6001 = responds with "ncacn_http/1.0" message
     6002 = no response
     6003 = no response
     6004 = no response
     6005 = responds with no message
     6006 = response with no message
     6007 = responds with no message
     6008 = no response
     6009 = no response
     6010 = no response
4.  I'm not running Exchange 2007

I've tried a few suggestions such as creating a hostfile, adding values for the FQDN and NetBIOS names for the 6000-range ports in the ValidPorts key, and experimenting with Basic authentication.  Nothing seems to help.  I do not get this error when I manually specify the server settings - only when I attempt to use autodiscover.  My autodiscover record resolves perfectly, and RPC is the only CAS feature I'm having problems with.  Any ideas?
LVL 1
marrjAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

marrjAuthor Commented:
I talked to Microsoft about this.  They were very opposed to the idea of using testexchangeconnectivity.com to test Outlook connectivity.  That's pretty funny, given that it is their product.  They said that as long as Outlook was working externally, the 6001 error was nothing to worry about.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
marrjAuthor Commented:
I did the research myself.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.

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.