Solved

Exchange 2013 Outlook Anywhere Issues

Posted on 2014-07-28
2
365 Views
Last Modified: 2014-08-06
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?
0
Comment
Question by:marrj
  • 2
2 Comments
 
LVL 1

Accepted Solution

by:
marrj earned 0 total points
ID: 40243933
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
 
LVL 1

Author Closing Comment

by:marrj
ID: 40243955
I did the research myself.
0

Featured Post

Top 6 Sources for Identifying Threat Actor TTPs

Understanding your enemy is essential. These six sources will help you identify the most popular threat actor tactics, techniques, and procedures (TTPs).

Join & Write a Comment

Sometimes Outlook might have problems sending a message. There may be various causes- corrupted PST, AV scanner etc. The message, instead of going to the Sent Items folder, sits in the Outbox indefinitely. To remove it you can use a free tool cal…
This process describes the steps required to Import and Export data from and to .pst files using Exchange 2010. We can use these steps to export data from a user to a .pst file, import data back to the same or a different user, or even import data t…
In this video we show how to create a User Mailbox in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Recipients >> Mailb…
In this video we show how to create a mailbox database in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Servers >> Data…

758 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

17 Experts available now in Live!

Get 1:1 Help Now