I have a small organization with Exchange 2010 and Exchange 2013 servers. The Exchange 2013 server has the mailbox and client access roles. We use the same URL internally and externally. There are no client connectivity issues to Exchange 2013 (including Outlook clients, mobile clients and browser/OWA clients) except for the one machine: the Exchange 2013 serve itself (which is installed on Windows Server 2012).
On the Exchange 2013 server, I am forced to use OWA for mailbox access as Outlook 2013 is unable to connect to Exchange 2013. I ran the Microsoft Office Outlook Connectivity Test on the server and both tests passed with no issues. The Microsoft Connectivity Analyzer Tool which did find some issues listed below:
Checking the IIS configuration for client certificate authentication.
The test passed with some warnings encountered. Please expand the additional details.
Additional Details
Additional Details: Client certificate authentication couldn't be determined because an unexpected failure occurred. WinHttpSendRequest failed with error 12030.
Testing HTTP Authentication Methods for URL https://<server>/rpc/rpcproxy.dll?467e33c4-98ff-496d-b019-afdc65ce1d28@<domain>:6002.
The HTTP authentication test failed.
Additional Details
Additional Details: Exception details: Message: The underlying connection was closed: An unexpected error occurred on a send. Type: System.Net.WebException
Testing HTTP Authentication Methods for URL https://<server>/rpc/rpcproxy.dll?467e33c4-98ff-496d-b019-afdc65ce1d28@<domain>:6002.
The HTTP authentication test failed.
Additional Details
Additional Details: Exception details: Message: The underlying connection was closed: An unexpected error occurred on a send. Type: System.Net.WebException
I think this may be related to authentication or RPC Proxy. Can anyone help me solve this so I can load an Exchange profile on Outlook 2013 on the Exchange 2013 server? Thanks.