Couple notes: Many customers that I work with are experiencing this issue. Based on the Intel Support Community post associated with this issue https://communities.intel.com/message/220048#220048 , Intel posted this message
"Yes Intel is aware of this issue. Please retest using our latest LAN driver version 19.0 release, available from our Download Center, and let us know if this driver helps resolve your issue. Thanks!"
We have had customers test this version and it does appear to eliminate the problem without the need to turn off power saving and IPv6. Please try this out and post your results..
If your network teams are interested (and they should be), here is the actual packet debug of the IPv6 multicast ..
Hey, just wanted to chime in here that I was having the same issue on my network with HP Elitedesk PCs with this same onboard NIC, and this was the first link Google suggested. Sure enough, disabling AMT fixed it, and other strange issues I've been having on older machines were also resolved.
AMT sounds not ready for actual deployment in any sized business other than a lab. Which is surprising, since it's had time to mature a bit. It'ss interesting that this is ON by default, and that Intel doesn't advertise this ability to cripple the network and machines its used on in the product literature.
I'm not really sure if my problem is related to the issues described so far in this thread but I have a very annoying problem with our Dell 9020 towers with I217-LM NICs running Windows 8.1. When the computers wake up from sleep (standby) all connections to open network shares and open Office 2010 documents are lost. All shares are on a Windows 2012 R2 ESSENTIALS server + domain controller which runs as a VM. So after waking up a Dell 9020 from standby I get my Win 8.1 login prompt, log in, but for any open shares that were open when the PC went to sleep in explorer, now I randomly get either a domain authentication error message or a new authentication prompt that asks me for domain username and password. The connection to open Word 2010 docs is always lost and Word tells me that the computer came back from standby but a connection problem occured and the document is now read-only, i.e. it must be saved as a new document. Very annoying!
I found out that similar problems date back to Windows 7 or even XP and people suggested to disable "computer can turn off this device to save power" on the network adapter in device manager. I tried this with the latest Dell NIC drivers but this did not help at all. I also tried installing the latest Intel NIC drivers but this did not help either. I also don't see the "computer can turn off this device to save power" in Intel's latest drivers. Maybe those NICs just don't support the option to stay on during standby? BTW I have not enabled AMT so it should not interfere.
Any help or hints are welcome. Thanks in advance
Basically I was having the same issues on my network that they were flooding it with broadcasts/multicast.
I had to enable storm control just to get by so it wouldn't crash my network or would take much longer.
I just want to confirm 3 things.
1.The IPV6 fix has that fixed the issue for you guys it seems too from what I read.
2.Disable Power saving features on adapter from what I can tell fixes the issue.
3.Update driver from Intel -- This is the one I would like to use as it's more permanent solution, Can anyone vouch for this solution in terms of it solved there problem without doing the above two steps.
Apologies, I meant to update this post earlier. When this was happening for me, Dell worked with me over four months or so before we got a more permanent fix.
The latest drivers provided from Dell should fix the issue. I was receiving 9020s with older drivers from the factory, but I implemented the latest drivers from Dell into our SCCM task sequence. Since then, the new machines have not repeated the behavior.
I'm surprised that Dell still ships their factory image with the defective drivers. I suppose they expect that most enterprises will re-image with their own. But still....
Anyway, I'm thankful that Dell assigned someone to work with us directly. It took some time, but they did release a fix and I appreciated their attention to the matter.
The problem you are describing does not appear to be the same problem we were having with the multicast storms occurring. At first glance, it appears that it might be a software/windows issue and not specific to the NIC itself.
Do you see this behavior on other machines on your network that do not have this NIC?