SMB2 traffic crashes network?

Solution 1:

You think it's originating from your PC? Have you tried unplugging your Ethernet cord and seeing if it fixes the network wide issue?

I think you may be taking a too narrow view on a network wide issue by only looking at individual Wireshark logs, have you tried reviewing your switch and router logs and seeing if there are any errors?

To find the source of SMB traffic that is suspected to cause the issue I would run a netstat -a and look for what program is using TCP port 445 (Wikipedia also says UDP ports 137, 138 & TCP ports 137, 139) I would do this on both your workstation and on the file server. I would also set up some network related performance monitors on the file server to see if that is spiking during this time as well.

I don't think it would be safe to settle on SMB just yet without seeing the same sort of traffic on multiple workstations. The fact that it is happening at a specific time makes it seem like there is a scheduled task , program, or backup running at that time. WSUS settings and Windows Update GPOs have caused this issue for me in the past, I would double-check those.

It really sounds like the best solution would be to set up some sort of SNMP monitoring / NMS on all of the workstations / servers and their NICs. Quest Foglight and Solarwinds NPM, can do this. After monitoring SNMP traffic you would be able to see what interfaces are having high utilization during those trouble times. Buyer beware, this can be expensive. Quest Foglight will let you monitor up to 200 interfaces, so that may be enough for a good sample.

Solution 2:

Were you using the Windows quota-ing system (File Server Resource Manager)? Our network is having similar issues and i'm getting wireshark logs similar to what you posted.