David Bar-On

> It takes some time to appear but after that repeatedly. I assume that the problem is in the server, not the client. When the problem happens, does it happen...

> .... this message sometimes shown instead of "connection refused" when, for example, destination port blocked by a firewall or iperf3 server even not runned. I saw it when tried...

@embermctillhawk, regarding: > The only readily available version of iperf3 for Windows is 3.1.3 Newer iperf3 version for Windows is available [here](https://files.budman.pw/) (although not an official iperf3 site - maintained...

Few comments that may help the evaluation: > it's important to consider if we're pushing bytes as quickly as possible or measuring the performance of the entire system with sending...

~~Note that PR #648 fixed an issue related to `-t 0` around version 3.3, so it is better that you will use a newer version (than 3.1.3 and see if...

The problem probably happens because iperf and iperf3 are not compatible, so iperf (iperf3) server can work only with iperf (iperf3) client.

> What would have been useful was something saying "if you [are silly enough to] have both iperf and iperf3 installed, make sure you're using the same at each end."...

@Vishal6ji2, can you add more information: 1. What was the client command that caused this error? (You can hide IP addresses / host names.) 2. Did you get this error...

> Question: Shouldn't --skip-rx-copy be a server side option instead of a client side? (or both if using the -R option) The client send this option (as several of the...

I now understand why you asked to have the option on the server side, a use case that I didn't think about. I am not sure it is better to...