I would recommend to check without bonding in the windows side.
Did you check the port counters, are there any errors?
Thank you for comment. There is no bonding on windows side configured. There are no port counters errors, ibdiagnet show no errors at all.
So far recently I've installed new WinOF and firmware. So things are going better now, but still I have some issues with packet loss. As before, linux to linux communications are good and linux to windows are not. I've ran few flood ping tests to understand how does latency and loss rate depend on WinOF and fw versions. Here is test summary:
Win 2012, WinOF 4.40, fw 2.30.3200
2156359 packets transmitted, 2127781 received, 1% packet loss, time 471502ms
rtt min/avg/max/mdev = 0.032/0.043/3.439/0.019 ms, ipg/ewma 0.218/0.043 ms
Win 2012, WinOF 4.40, fw 2.30.8000
197278 packets transmitted, 193214 received, 2% packet loss, time 57419ms
rtt min/avg/max/mdev = 0.020/0.022/3.742/0.026 ms, ipg/ewma 0.291/0.022 ms
Win 2012, WinOF 4.60, wf 2.30.8000
45086 packets transmitted, 44350 received, 1% packet loss, time 10878ms
rtt min/avg/max/mdev = 0.021/0.025/2.431/0.024 ms, ipg/ewma 0.241/0.023 ms
This case I had low packet loss rate and average latency.
Win 2012 R2, WinOF 4.60, fw 2.30.8000
699589 packets transmitted, 698741 received, 0% packet loss, time 57022ms
rtt min/avg/max/mdev = 0.041/0.051/12.418/0.073 ms, ipg/ewma 0.081/0.048 ms
The only case I had no packet loss, but high latency.
Win 2012 R2, WinOF 4.45, fw 2.30.8000
347256 packets transmitted, 347256 received, 0% packet loss, time 39444ms
rtt min/avg/max/mdev = 0.081/0.098/13.205/0.087 ms, pipe 2, ipg/ewma 0.113/0.097 ms
In short: WinOF 4.45 provides best reliability, while WinOF 4.40 provides best latency.
Still looking forward to find solution to combine it into one.
I would recommend trying the new WinOF release 4.60.
Let me know if that helps.
I've tried installing it already, but it didn't help. You can see some statistics in my comment above.