Very slow file file copy is fixed when running Wireshark
We have a Windows 10 Enterprise VM. It is used to Build and Deploy one of our applications. Part of the process is copying files from Server A (a Windows 2019 server VM) to Server B (aother Windows 2019 server VM).
When this process fires, it takes between 45 minutes to well over an hour to complete. Way too slow. This is impacting our software deployments.
I fired up Wireshark to try to figure out the issue. As soon as Wireshark began capturing the traffic, the copying files immediately sped up. Repeating the file copy (with Wireshark running), takes <1 minute. Very interesting.
We stopped Wireshark, and it was slow again (but some times, it remained fast. No idea why). After rebooting the VM though, the file copy was very slow again.
We are only copying 386 files, about 66 MB in size. So, it's not a crazy amount of data.
We have tested the file copy from Server A to Server B and Vice Versa, bypassing the Windows 10 VM all together. We have copied files from other workstations (such as mine) to Server A with zero issues, and same to Server B.
My questions:
- What does Wireshark do on startup that "fixes" our file copy issue? From our experience Wireshark does "something" we want to know what that is.
- What configurations does it touch/modify/change?
- Which services does it start? If any?
- Which processes does it use?
- Does it change any OS settings?
I am not sure if I am asking the right questions. But for some reason, having Wireshark capturing traffic fixes all the file copy issues.
Thanks,
Paul
When you're running Wireshark, is it capturing in promiscuous mode or not? (I'm assuming this is not a copy over Wi-Fi.) If so, does changing the promiscuous mode (leaving it off if it was on, turning it on if it was off) make a difference?
Guy, thanks for responding. This is Wireshark Portable, freshly installed, no changes other than to auto resolve IP's to their names. I don't even know where to look for promiscuous mode.
No, this is not over WIFI, as far as I know, the Win 10 VM and the 2 Win 2019 VM's are in the same data center. Ping times are usually < 1ms and number of TraceRt hops are 1.
That doesn't make a difference when it comes to promiscuous mode.
Select "Options" from the "Capture" menu. In that dialog box, there's a "Enable promiscuous mode on all devices" check box. If it's checked, un-check it; if it's not checked, check it. Then select the interface(s) on which you want to capture, and click "Start".
Guy, thanks. I hadn't had a chance to get back to this... I did find the Promiscuous mode and it made no difference whether or not it was checked or not. It was Checked by default. I is now currently checked (after I tested Unchecked)