The attempt to ping the MAPI Mail Store endpoint endpoint failed

Question

Hi,
We have just moved from Exchange 2010 to 2013 (completely new organisation/ad, there were lots of problems with the old one). All roles are performed by a single server (budgets). Everything went perfectly however Outlook cannot connect, creating a new profile
finds the settings via Autodiscover (via 3rd party cert) but then the following error occurs:
(There were images before, but apparently I am not allowed to post any images so apologies for the typing out)
The action could not be completed. The connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action.
The check name doesn't work and the account cannot be created (and from what I have read Exchange 2013 doesn't support non-autoconfigure connections anymore).
Before I enabled Outlook anywhere any Outlook connections would just constantly ask for credentials, however I can't go back now it seems. Does Exchange 2013 only support RPC via HTTP connections for Outlook? That is something new if true.
Then I checked https://testconnectivity.microsoft.com/ and the following is displayed:
Attempting to ping the MAPI Mail Store enpoint with identity [email protected]:6000
The attempt to ping the endpoint failed
The RPC_S_SERVER_UNAVAILABLE error (0x6ba) was thrown by the RPC Runtime process.
Cue some intensive Googling (sorry Binging?) and several suggestions were found to resolve the issue from various threads here and blog posts:
Add IP  SERVER to the hosts and lmhosts.sam files
Disable IPv6
edit HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Rpc\RpcProxy\ValidPorts to everything I could think of: 
NETBOIS:593;NETBOIS:49152-65535;FQDN:49152-65535;localhost:49152-65535;Outlook anywhere FQDN:49152-65535;
Telnet into port 6001, 6002 and 6004 from the server. This throws an interesting result:
Port 6001: ncacn_http/1.0 (which seems fine)
Port 6002: can't connect
Port 6004: can't connect
This looks to be my issue, but I can't see why it's not connecting and I don't know how to check any further. The other thing is the Remote Connection Analyser is looking for port 6001 and it can't connect.
Any help is much appreciated, I think I have tried everything I can think of and have reached the end of my intelligence.
-macole1

Answer 1

Hi Mavis,
Many thanks for the reply. You are thinking along similar lines to me. I have re-enabled IPv6, I never worked out how to turn off Outlook Anywhere.
1. DNS is working correctly, I can telnet into port 6001 using the FQDN and localhost
2. My VaildPorts key is as follows: I think it is okay.
COMPUTERNAME:593;COMPUTERNAME:49152-65535;FQDN:49152-65535;localhost:49152-65535;OUTLOOKANYWHEREADDRESS:49152-65535;
3. This is where I was thinking the error comes from, however I can't find any information on how to test this.
netstat -a shows:
Active Connections
  Proto  Local Address          Foreign Address        State PID
TCP    0.0.0.0:6001           BOSTON:0               LISTENING       13764
  TCP    0.0.0.0:6005           BOSTON:0               LISTENING       356
  TCP    0.0.0.0:6006           BOSTON:0               LISTENING       760
 TCP    [::]:6001              BOSTON:0               LISTENING       13764
  TCP    [::]:6005              BOSTON:0               LISTENING       356
  TCP    [::]:6006              BOSTON:0               LISTENING       760
So it's not even listening on 6002 or 6004.
These are what the PID are. Looks like only 6001 is related.
PID    Process
13764  Microsoft.Exchange.RpcClientAccess.Service.exe
356    wininit.exe
760    svchost.exe
4. I tried turning off Windows firewall (the only firewall) to test it and it made no difference therefore it was re-enabled. As all the roles are on the same server I assume that would make no difference.
Do you have any ideas why there would be no service at 6002 or 6004? This looks to be the root of the issue.
Many thanks for your help so far.
-macole1