Adding the above issue on my blog to help me remember as I forgot the commandlet to check for replication network communication issues between members of a DAG (damn limited memory of mine) – may be valid for Exchange 2013 as well (have to double-check this on my lab when I’ll have time between kids, regular work, administrative work, etc, etc)

SYMPTOMS:

If we encounter the following behavior :

1- Issues trying to Update-DatabaseCopy (error message saying that "An error occurred while communicating with server '<Server_Issue>'. Error: Unable to read data from the transport connection: an existing connection was forcibly closed by the remote host.")

2- 2153 MSExchangeRepl errors in the Application Log and NO OTHER RELATED ERRORS

3- Get-MailboxDatabaseCopyStatus -ConnectionStatus gives the above error on the "IncomingLogCopyingNetwork" parameter.

An error occurred while communicating with server '<Server_Name>'. Error: Unable to read data from the transport connection: an existing connection was forcibly closed by the remote host.

CAUSE:

Some network error on the Replication network causing the network replication to have issues…

WORKAROUND:

3 facts to remind first:

• DAGs have 2 defined networks: MAPI Network and Replication Network.
• Replication traffic (Log replication, Heartbeat traffic) goes through the Replication Network
• Exception: Database seeding or re-seeding always goes through the MAPI network.

ACTION: disable replication on "Replication Network" + enable replication on "MAPI Network". then RESTART the MSExchange Replication service.

To see if it worked:

Get-MailboxDatabaseCopyStatus -ConnectionStatus | FT Identity,IncomingLogCopyingNetwork

You should see something like "{Server_Name,MAPI-Network}" on the IncomingLogCopyingNetwork column, and no "Error: Unable to read data...." subsequent message.

Raw issue data:

IncomingLogCopyingNetwork

SERVER_NAME

Replication_Network_name

An error occurred while communicating with server 'SERVER_NAME'. Error: Unable to read data from the transport connection: an existing connection was forcibly closed by the remote host.

Sam.

Intro:

In this article, I’ll provide a quick reference guide and an Excel-based tool that allows you to build monitoring consoles using HTML without being a scripting star.  I call it the Document-Tool-Walkthrough (DTW).

This is a new concept document/tool built using Excel that can help you to build System Monitor consoles that are centrally stored to monitor your servers.  You can build as many consoles as you want using this tool, with each console being responsible for monitoring a specific area of your IT infrastructure (e.g. one for Exchange databases, another for disk latencies, another for core resources of DC servers, etc.), You can store these in a central place where administrators will be able to open them and monitor (or troubleshoot) their servers.  People using this tool won’t need any knowledge about scripting (or at least very little) as the code is generated automatically through the Excel tabs.

Please note this tool is provided as is, but feedback and input is appreciated.

The remainder of my article is there:

How To Build A Simple and Efficient Windows Monitoring Solution (DTW)

http://blogs.technet.com/b/mspfe/archive/2011/03/10/how_2d00_to_2d00_build_2d00_a_2d00_simple_2d00_and_2d00_efficient_2d00_windows_2d00_monitoring_2d00_solution_2d00_dtw.aspx

The Excel spreadsheet/tool is there:

Version Excel 2003 (may not work as good as Excel 2007-2013 version above):