What is also very interesting is by example, if I am executing a ping between the two local computers, this continue working, if I try to access the other computer using remote desktop, it works, it is only with this HTTP requests. While we activate the connection emulator communication with the browser (IE and Chrome), packages start failing with 'TCP Retransmission', 'TCP Zero Window', 'TCP Spurious Retransmission', 'TCP Out of Order' (all these coming from TCP dump from Wireshark) and at the end the browser fails to open the page, and this only happens with HTTP resources located in the same network, from the same browser, just in another tab we can connect to other web resources located in different networks without any problem. We have other servers outside on a different network with latency of about 20 ms.

We have multiple servers on the same network/subnet with a lantency under 1 ms.In the Connection Emulator we only have Transfer Rate of 2Mbps and Latency of by example 30 ms.

A packet trace would be perhaps the best way to examine what's happening at that level but you might see this issue too withing a ping test series.We are experiencing a very strange behavior while using Connection Emulator. Yes, excessive RTT can cause TCP re-transmission, although TCP generally tracks a RTT average so usually only highly variable RTTs would trip the timeout. Only too large packets, leaving a 元 interface, are fragmented. Interfaces receiving frames bigger than they are configured for should drop them. In no event shall Author be liable for any damages whatsoever (including, without limitation, damages for loss of use, data or profit) arising out of the use or inability to use the posting's information even if Author has been advised of the possibility of such damage. Usage of this posting's information is solely at reader's own risk. Information provided is for informational purposes only and should not be construed as rendering professional advice of any kind.

The Author of this posting offers the information contained within this posting without consideration and with the reader's understanding that there's no implied or expressed suitability or fitness for any purpose.

Tcp spurious retransmission wireshark