Revision history [back]

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 meg 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:

1. 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.
2. What configurations does it touch/modify/change?
3. Which services does it start? If any?
4. Which processes does it use?
5. 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

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 meg 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:

1. 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.
2. What configurations does it touch/modify/change?
3. Which services does it start? If any?
4. Which processes does it use?
5. 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

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 Wireshark to try to figure out the issue. As soon as WireShark Wireshark began capturing the traffic, the copying files immediately sped up. Repeating the file copy (with WireShark Wireshark running), takes <1 minute. Very interesting.

We stopped WireShark, 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 meg 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:

1. What does WireShark Wireshark do on Startup startup that "fixes" our file copy issue? From our experience WireShark Wireshark does "something" we want to know what that is.
2. What configurations does it touch/modify/change?
3. Which services does it start? If any?
4. Which processes does it use?
5. Does it change any OS settings?

I am not sure if I am asking the right questions. But for some reason, Having WireShark having Wireshark capturing traffic fixes all the file copy issues.

Thanks,

Paul