Stop network traces on both client and server sides.
Check the <filename>.csv file:
If NetworkErrors or ProtocolErrors are displayed in the file, go to the next step.
If no error is displayed, stop and discard the network trace. Collect a new trace on the client and the server. Try with an increasing number of connections (-connections:) in step 1 until the error occurs.
Find the client socket number of the error in the <filename>.csv file and apply this number as a filter to check for a packet loss, a packet retransmission, or a TCP reset that wasn't initiated from either endpoint. With this information in hand, contact the network team for help.
There are errors, but no issues are found in the packet capture.
The original packet reaches the destination, but the sender retransmits the same packet because there's no acknowledgment (ACK) by the receiver.
The packet discards might be caused by the network card driver or by the processor being unavailable to process incoming packets on the receiver. Make sure the Network card driver is up to date and that the RSS/VMMQ is set up correctly. For example, to use more base processors on a server such as SQL server, customize RSS/VMMQ not to use the base processor and to start processing from the next physical core.
Learn to troubleshoot on-premises connectivity and hybrid network connectivity. Diagnose common issues with DHCP, name resolution, IP configuration, and routing that can cause reliability and connectivity problems in an on-premises and a hybrid environment.