Hi

I have a "growing" list of users where outlook anywhere will not work for them when they are internet only connected.  If they connect to the corporate network with a vpn tunnel everything works fine.

They either are getting a continual prompt for password, or outlook is just in a disconnected state.

I am fairly confident this is a server side issue somewhere.  I have tried multiple computers for the same user account and it still doesn't work, but on those same computers i can setup my own outlook profile and can get through just fine.

If I run through the MS Remote connectivity analyzer tool the user fails as well, but my account works just fine.  the error message from the MS Con Tool is :

************************************************ Attempting to ping the MAPI Mail Store endpoint with identity: ourmailsystem.company.local:6001.
	The attempt to ping the endpoint failed.
	<label for="testSelectWizard_ctl12_ctl06_ctl02_ctl06_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. Elapsed Time: 2915 ms.

I have also checked the "get-casmailbox" properties for the failing account and "MAPIBlockOutlookRpcHttp" is set to False as well.

Thanks

Primary reason for Outlook Anywhere failure is lack of trusted SSL certificate. Do you have a trusted certificate in place?

If this is affecting multiple, but not all, users then I would also check that permission inheritance is enabled on the account in ADUC.

The error you have posted I would expect to happen to all users, so it maybe a red herring.

Simon.

The SSL Certificate is good.  That passed through the connectivity analyzer tool as good as well.  I reviewed the Inheritance check box on the Security tab for that user and it is checked already.

Hi,

Please try to remove the saved credentials from client PC.

Control Panel > Users Account > Manage your credentials > Generic Credentials, remove the credential about outlook account.

Restart outlook.

If this doesnt work, create a new profile to check this problem.

Best Regards.

Hello

Did you also check ExternalHostNames for OutlookAnywere connection on all servers ?

Get-OutlookAnywhere | fl *host*

M.Rembas

MS Support was able to get me through the issue.  It ended up being a new CAS Server that was added that was causing the issue.  When Exchange 2010 got installed Exchange automatically added the server to my CAS array and I didn't want that to happen.  I had to run the following command: Set-ClientAccessServer <server> -IsOutofService $True

That removed the CAS server from any future proxy requests...Here are some additional details about it as well:

http://blogs.technet.com/b/exchange/archive/2014/03/12/client-connectivity-in-an-exchange-2013-coexistence-environment.aspx

Thanks

CB