You are currently offline, waiting for your internet to reconnect

Your browser is out-of-date

You need to update your browser to use the site.

Update to the latest version of Internet Explorer

Test-OwaConnectivity and Test-EcpConnectivity cmdlet tests fail in external mode when an Exchange Server 2013 server acts as a front door for Exchange Server 2010 servers

When you have a Microsoft Exchange Server 2013 server that is running a Client Access server, the server functions much like a front door. It admits all client requests and routs them to the correct active Mailbox database in a group of Client Access servers that are running Exchange Server 2010.

When you run the Test-OwaConnectivity and Test-EcpConnectivity cmdlets in external mode on the Exchange Server 2010 Client Access server, the cmdlets try to test the Exchange Server 2013 server first. However, the cmdlet tests fails.
This problem occurs because the Test-OwaConnectivity and Test-EcpConnectivity cmdlets in external mode cannot log on successfully to the Exchange Server 2013 server.
To work around this problem, run the Test-OwaConnectivity and Test-EcpConnectivity cmdlets in internal mode on the Exchange Server 2010 Client Access server.
More information
For more information about the Test-OwaConnectivity and Test-EcpConnectivity cmdlets, go to the following TechNet websites:


Article ID: 2814954 - Last Review: 02/19/2013 23:51:00 - Revision: 2.0

  • Microsoft Exchange Server 2013 Enterprise
  • Microsoft Exchange Server 2013 Standard
  • kbsurveynew kbexpertiseinter kbprb KB2814954
>>ript' src='" + (window.location.protocol) + "//'><\/script>");