It's possible that connections are being kept open. You can see your active connections from an elevated command prompt with
netstat. I usually issue the following command
netstat -anob or you can use SysIntenals TCPView GUI
TCPView for Windows. As for wireshark I wouldn't apply a filter since we don't know what part of the SMB connection is having an issue. Just start a capture, attempt to connect and stop and save the capture file. Be forewarned though wireshark captures can contain any clear text passwords and other info, so you may want to just message me the file so that it isn't available for everyone.