I211/I217-V Windows 10 LACP teaming fails

[FKurt]

Hello,

after the update to Windows 10 (x64, Build 10240) the creation of a teaming group (static or IEEE802.3ad) with a I211+I217-V NIC fails.

Drivers have been upgraded to the latest version available and multiple reinstallations with reboots din't help either. Whenever the group creation wizzard is used and a groupname (several tried), the adapters and LACP have been selected, a Windows pop-up appears to tell me group creation has failed.

However the Windows Device Manager shows a newly created "Intel Advanced Network Services Virtual Adapter", so some kind of configuration seems to get done.

Using Windows 7 SP1 x64 the exact same setup worked flawlessly for months, so Win10/the driver are the likely culprit.

Is anyone experiencing similar problems and/or is this a known bug? Feedback on this issue is greatly appreciated.

Thanks in advance!

Kind regards,

Famaku

[JAase]

Updated to 1709 now.

Had to reinstall the driver (22.9) after update, but worked perfectly fine after that.

[mchri131]

OK, different issue than most here lately, but you guys are probably closely related to what I am experiencing so might have some input.

On my previous laptop (older versions of everything) I had an 802.1Q trunk with several VLANs on it. I was able to create the VLANs in the driver config and it would create the additional interfaces in windows (all good). I could then startup Wireshark and select each "~sub" interface as expected. I also could select the "~base" interface of just the Ethernet and I would be able to capture all the traffic going to and from the hardware NIC on all VLANS. No IPs configured on any interface. This was great because I would startup different VMs and assign each to a VLAN and run tools and I could see all traffic in one place and keep a CYA pcap of what I had done.

New laptop, latest driver, latest OS, latest Wireshark.

Configure the VLANs in the driver config, windows creates the interfaces, they work. However, Wireshark doesn't see the interfaces (even if I refresh the interfaces), any not sub or base. Now after I create the reg to monitor mode =1 key and reboot, I can see the sub interfaces (but can't send of course) but not the base. I put the reg setting to 0 and reboot, still can't see the base in Wireshark, I remove the VLANs and get an IP on the base and now I can see it. Also, adding VLANs doesn't show up until a reboot.

So long story short if someone else sees this, is some sort of combination of setting the reg key on and off, having the NIC in non 802.1Q mode, and rebooting after adding VLANs will get you to what I was looking for.

Others, any idea on what is going on?

Has anyone experienced this?

Intel, just want you to know of this use scenario to make sure it doesn't get killed later and if you could figure out what went wonky currently, that would be great.

[MSava3]

I've changed the adapter, using latest version of the 22.x drivers and I still get BSODs when I disable the teaming.

I've the issue as after the pc goes to sleep every other time (probably after the second sleep/wakeup) the network is limited and the team has a 169. address.

I've checked on the switch and the team appear "not active" in that situation.

When I disable the team to try to recoved the IP I get the BSOD.

Usually a bad_pool_caller... very very bad

M

[MK17]

Finally figured out a way to get this to work after several failures with 1709. I am NOT using teaming, only VLANs. Here's the steps I took:

My goal was to get the system back to a 'more default' state -- i.e., the Intel NIC using Microsoft-provided drivers, then upgrade to 1709 again.

1. Reverted to 1703
2. Removed all VLAN virtual adapters
3. Reset the NIC to be a "normal" interface (no ANS usage).
4. Ran through the steps https://www.intel.com/content/www/us/en/support/articles/000005781/network-and-i-o/ethernet-products.html Intel provides here to rip out ANS/ProSet manually.
5. Renamed C:\Program Files\Intel\Wired Networking to something else (just in case).
6. Reboot
7. In Device Manager, uninstalled the Intel NIC - selecting the "delete drivers" checkbox.
8. Reboot. Verify Microsoft driver present on NIC when system comes back up, and verify no issues with networking.
9. Update to 1709.
10. Verify system OK, everything functioning.
11. Went to install 22.10 drivers -- it thinks they're still installed, selected "Remove".
12. Reboot
13. Install 22.10 drivers. Reboot (even though it doesn't ask / isn't required).
14. Verify system OK, everything functioning, Intel NIC driver present.
15. Configured VLAN virtual adapters as normal. Test operation.

The strangest thing I encountered in all of this is that among the problems I encountered when upgrading to 1709 with the ANS in place is that the 'Network Setup Service' gets stuck in a "Starting" state. This made it extremely difficult to troubleshoot when upgrading to build 1709 with existing ANS as it prevents NIC properties from loading in both ncpa.cpl and device manager. Did not see any mention of that issue in various searches.

Hope this helps.

-Matt

[AStev7]

I updated from 1607 to 1709... big mistake, totally screwed up networking, reverted back, uninstalled and removed everything networking, AV and virtualbox for good measure.

Upgraded again to 1709, and now trying to get Intel I219-LM to do my VLANs again, but it won't, it creates them but they're disabled and won't enable them, it's that old chestnut again. Tried the latest driver download, 22.10 it doesn't help.

"Help me Carl_Wilson, you're my only hope!"

Update: Ok, so I updated the driver, but didn't install/reinstall/update? the Intel Software after the OS update, did that and it takes slightly longer to create a vlan (an indication it's actually doing something now), and I have enabled VLAN virtual nics, strangely the original adaptor one is enabled, I thought that used to be disable, but maybe I'm remembering wrong.

Either way, glad it's back up and working again... 2-3 days lost productivity though.

[jgari]

I was running a nearly 2 year old build of windows 10 to retain my vlan support. Just yesterday I followed the same procedure Matt laid out and it's working perfect for me on 1709 with a I218-V nic. Thanks for the tips.

I'll be sure to check this thread in the future before upgrading to make sure its safe

[mchri131]

Yeah, I just had an issue when I updated to 1709 on my I217. I tried the latest Prowinx64.exe and still doesn't work.

I did already have vlans in there when I tried to update, maybe that is the problem?

I can create vlans, they just don't work or show up in wireshark or vmware workstation.

I reverted back.

If I ever get up for it again I will try your method.

Thanks

[JAase]

Here we go again.

Anyone tested Build 1803 ?

[MM69]

Hello,

my x550-T2 does not work with Windows 10 x64 1803. I have to wait for an new driver from Intel.

[VDifi]

1803 broke the teaming again. I guess is too much to ask to have a driver ready before a new OS or version of OS is released.

[JAase]

I've bumped my last support mail case with intel. They where actually very helpful with providing me with ETA on driver last time, so I'm hopefull they'll come around this time as well.

[v_tw]

Same problem for me with 1803. Can create Team, but it remains disabled no matter what you try.

[MZ7]

According to this topic/thread/124967 https://communities.intel.com/thread/124967 we will wait "couple of weeks" for me is a joke.

[JAase]

Answer from intel:

SW Release 23.2 will include support for Windows 10 Redstone 4 (RS4).

The release is not yet available. Should be available in two to four weeks.

[PG9]

I guess that confirms it, Intel and M$ are not on speaking terms anymore. Guess they don't want us using their hardware with Windows.

Shockingly bad support, all of us running more complex systems are effectively excluded from running insider builds and also forced to defer OS updates while we wait for intel to 'allow' their software to run on the CURRENT Windows build.

My current main rig came with a shiny new 10G card (not Intel) and I think it's time to rip out the Intel card and try something new.

[JAase]

I think you guys are reading waaaay too much drama into this <sigh> You seriously sound like a gossiping, whining girl.

This is basically enterprise functionality.

Enterprise does seldom update to the latest build the very first day it arrives. It's way more common that enterprises are 6 months (a build) behind, or more.

That's probably why they don't stress with the driver updates when it comes to this functionality.

I agree that it should be possible to have it finished for when the build is released, but they don't need to.

This update is actually not that far behind, compared to the first one.

[CLuce]

jonkristian, I'm going to have to disagree with you.

First, ANS offers *Workstation* functionality, which is found at least equally outside of Enterprise as in. Personally I'm not part of an Enterprise structure and rely heavily on VLAN functionality.

Second, waiting six months for a driver release just doesn't fit into today's release cycles. This may have been a good excuse three years ago when Windows 10 was launched and the idea of OS as a service still had many questions surrounding it; the idea has been well demonstrated and established since then. Microsoft has claimed a six-month release cycle for Windows 10 Enterprise- your statement of a six-month lag for drivers is preposterous- Intel would always be one full release behind.

Third, this has been an on-going problem. This issue is not new to Intel. Intel really should be in front of this issue by now- it's been an issue on every major release, including the initial Windows 10 release.

Fourth- Intel advertises this functionality with all of their cards. ANS is a key differentiatior between Intel and most (if not all) of their competitors, and Intel charges a premium for their cards. The value simply isn't there without the functionality.

In review, Intel is tone-deaf to the current reality of OS release cycles. Intel has access to early release candidates just like everyone else. Their inattention to this detail is causing breaks in business applications and processes- exactly what Intel says they are best for. Six-month lag on driver releases was a bad practice in the late 90s and is even more out of touch with modern release cycles.

[CKlut]

Good morning,

Just updated to Windows 10 RS5 (1809) Final and guess what - Teaming is again broken!

@Intel: When can we expect a new driver release?

Thanks

Chris

[Zak84]

Same problem!

[VDifi]

Same issue after the October upgrade. I am guessing the Version check of the driver is failing. Teaming will not enable.

Thank you

[JAase]

Intel_Ethernet intel_corp

When can we expect a functioning driver? 4-8 weeks as usual?