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

Article translations Article translations
Article ID: 2814954 - View products that this article applies to.
Expand all | Collapse all

Symptoms

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.

Cause

This problem occurs because the Test-OwaConnectivity and Test-EcpConnectivity cmdlets in external mode cannot log on successfully to the Exchange Server 2013 server.

Workaround

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:

Test-OwaConnectivity

Test-EcpConnectivity


Properties

Article ID: 2814954 - Last Review: February 19, 2013 - Revision: 2.0
Applies to
  • Microsoft Exchange Server 2013 Enterprise
  • Microsoft Exchange Server 2013 Standard
Keywords: 
kbsurveynew kbexpertiseinter kbprb KB2814954

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com