The obvious implication is that wireshark puts our network interface into promiscuous mode. Has anyone seen a similar problem? We've tried:
- Applying the hotfix located here that sounds just like our problem: http://support.microsoft.com/kb/263982
- We've tried messing with the NetworkThrottlingIndex in the registry
What else can we try? Any suggestions?
If it helps I can characterize our application as:
- joining and leaving multicast groups on the order of every few seconds (when busy)
- in our testing, we're joining ~10 multicast groups at any one time
- receiving multicast packets from each source between 20 and 100ms apart
- Edited by Larry_1971 Thursday, July 12, 2012 10:53 PM
Its a driver problem. We've seen it in two drivers. Both are signed drivers that passed MS's WHQL. I suppose few use multicast because its a pretty big and annoying issue.One vendor already had a fix and we're working with the other on getting a fix.
- Edited by Larry_1971 Friday, July 27, 2012 3:27 PM
You should set (add if it does not exist) the following key in the system registry: "DisableBandwidthThrottling=1" in "HKLM\system\CurrentControlSet\Services\LanmanWorkstation\Parameters\". The following document provides information on network tuning, including for workstations: http://msdn.microsoft.com/library/windows/hardware/gg463392.aspx.
- Proposed as answer by Michel Lagace Sunday, July 07, 2013 10:29 PM