Slow Content Deployment transportation / TCP connection was forcibly closed
We were having issues with slow Content Deployment for the transporting phase and it was sometimes failing with this error:
Publishing: Content deployment job failed. Error: 'System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a receive. ---> System.IO.IOException: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. ---> System.Net.Sockets.SocketException: An existing connection was forcibly closed by the remote host at System.Net.Sockets.Socket.Receive(Byte[] buffer, Int32 offset, Int32 size, SocketFlags socketFlags) at System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size)
A collegue of mine sent me something about TCP chimney (first time I heard about this!) and a simple command to run in the command line : Netsh int ip set chimney ENABLED. After this, the transporting phase was much faster and without errors. You can find the information about this command from knowledge base 912222.
Maxime
