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 xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxxx@domain.com: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