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

[ssean3]

It's a good question. I'm assuming Intel AND MS would need to patch software. There's no way that updated NIC software from Intel would bring thing function back.

[idata]

I asked this question of Carl_Wilson and the response I got was essentially that, no, the Intel solution is NOT a front-end for the Microsoft "new-netLBFOTeam" command. The way Intel handles teaming is not simply a front-end for this command nor does it require this Microsoft command to work in order for it to create a NIC team.

That said, there were a few updates that needed to be put forth by Microsoft in order for the Intel software to work right, and it's my understanding those patches were released a number of months ago.

The fact those patches came out months ago from Microsoft, and the new-netLBFOTeam command is still *not* working, and all the while Intel has been able to get it working (at least in lab) nonetheless leads me to believe they are truly independent from one another.

Carl, can you confirm?

[CARL_W_Intel]

Correct. The Microsoft codes is their own and is not what we base our ANS software on. Intel's Advanced Network Services (ANS) is our own code-base.

[DDoc]

Thanks for your work Carl.

I have the same issue (and had to fully reinstall Windows 10 due to Teaming mess some months ago). I can't wait for fixed drivers.

Anyway, can you confirm that iscsi offloading on i350-T2 is not affected by any bugs on Windows 10 ?

I found a very odd (and probably not related) issue with PRO/Set 20.x and that Dual Port NIC : if you configure MS iSCSI Initiator with 2 connections (MCS) to a NAS, then put one of the 2 RJ45 in port mirroring mode on your switch, you will get a BSOD on msiscsi.sys with PAGE_FAULT_ON_NONPAGED_AREA after some minutes. Reproduced with a fresh install and 3 different motherboards. Anyway, it's a rare condition and a pure nightmare to debug (and its probably a MS bug)...

Last question : can you confirm that the new X550-T2 will be working on Team/VLAN with the corrected drivers ? We just got some of them in our hands.

[CLuce]

Is it amateur hour at Intel now? Working with your # 1 partner, Intel can't resolve an issue over a year old involving a couple lines of code???

This is absolutely unacceptable that a key differentiating feature of a NIC using code NOT SUPPORTED IN MICROSOFT CODING GUIDELINES is not fixed for over a year. You could've re-written the entire driver stack several times over in that time.

This, after forcing sidegrades to new hardware to supposedly support VLANS and Teaming, and you don't even bother to support the features forcing the upgrade. "Yeah, all these networking features missing on Intel Adapters in Windows 10, you can get them if you buy essentially the same card, just newer." "Oh, the features don't work on the new card? I meant the features will work when we bother to code them properly. When will that be? Who knows, it's probably Microsoft's fault!"

I know you are excited about having a team reporting to you, but from my perspective absolutely nothing has been accomplished for a YEAR except false advertising, false promises, and inability to deliver features on a premium network adapter- included on a Realtek NIC.

One thing you have consistently failed to explain, Carl, is how can every other single NIC manufacturer succeed where Intel can only invent excuses? I have 5-year old ASIX USB ethernet adapters with better VLAN support than your brand-new premium NICs. Can you explain that one, Carl?

And yeah, don't bother upsetting your precious release schedule to fix a year-old problem that doesn't affect a competent NIC manufacturer, where you have issued failed promise after poor excuse. Do you recommend we wait until August for the latest batch of excuses, or just buy fully functional Network Adapters from practically anyone else?

BTW, your information page on ANS still lists support for VLANs in Windows 10 when that is known to be a lie. https://www-ssl.intel.com/content/www/us/en/support/network-and-i-o/ethernet-products/000006048.html Intel® Advanced Network Services (Intel® ANS)

[JLe6]

Is there an update to release date of the driver?

Thanks

[aasd4]

Any update? you said 15 of july. Will it be in the august patch?

[VInga]

Any further information Carl? I came here and registered to find out more info on this. By the looks of it, Intel found a solution they just need to deliver it. There's going to be some updates coming out very soon. They seem to have a few new features but nothing related to network handling. More UI and features - Dubbed "The Windows 10 Anniversary Update"

I just bought an I350 dual nic. Popped it in and sure enough I was dumbfounded. Not until I searched around did I come here.

Can you please provide more info, any ETA or a roadmap?

[idata]

Carl_Wilson ,

Any update on this? When will the August release be made available?

Have there been any setbacks, or are things full steam ahead as far as you are aware?

Thanks for the follow-up.

PS: Sorry that some of the folks here have let their emotions get the best of them. Most of us watching this thread are very appreciative of the work involved to fix these issues and realize that at the end of the day there isn't any reason to make this a bash fest. Just ignore those that can't pull up their big boy pants and act like adults!

[MKuiv]

Hi there

I'am also desperately waiting for suitable drivers for Windows 10. Hope to see em soon. It would be very nice if there is any kind of estimate of release date?

[jbond5]

I am wondering how many more 10GB network cards Intel did sold since link aggregation is broken...

It certainly did help to increase sells on this ultra expensive hardware.

[NMoid]

Can some one suggest a good alternative good ethernet adapter (Desktop Workstation ) which will support vlans in windows 10 and possibly in future windows versions,

Thanks

[SAlle3]

Hi Nizam, we use U2L 100P-Y1 from Lenovo. This is a USB 2.0 device. We also use a USB 3.0 adaptor from Lenovo but I don't have the part number in front of me.

[NMoid]

Thanks man, my requirement need a gigabit link. Will check some PCI Ex cards

[MZies1]

stallen1 wrote:

Hi Nizam, we use U2L 100P-Y1 from Lenovo. This is a USB 2.0 device. We also use a USB 3.0 adaptor from Lenovo but I don't have the part number in front of me.

I don't believe that this adapter - nor any USB adapter (2.0 or 3.0) on the market today - supports anything that is being looked for here: Multiple, concurrent 802.1q VLANs (VLAN trunking), and/or LACP teaming. Given that this is the proper audience (though admittedly otherwise off-topic) - if anyone is aware of a supporting USB (laptop-compatible) device that offers such capabilities, please update this thread as well as http://hardwarerecs.stackexchange.com/questions/2422/usb-to-ethernet-adapter-supporting-multiple-virtual-lans USB to Ethernet adapter supporting multiple virtual LANs - Hardware Recommendations Stack Exchange. (I had mentioned something /message/386052# 386052 similar back on 4/6). The Stack Exchange post includes details as to why such support is needed by many of us asking here and awaiting the Intel fix.

Again - once this is working for the supported desktop and integrated network adapters, Intel should please consider making a supported USB network adapter - or at least a chipset that a partner could work with.

[sgsb2]

I am very disappointed with HP, Intel and Microsoft.

It's is an absurd this situation.

PC: HP Elite Desk 800 GI, NIC INTEL I217-LM.

OS Windows 10 PRO x64.

And STILL dont work VLAN !!!!

I think that we will need go to public justice to force these companies to delivery one basic service: IEEE VLAN.

it's is insane.

Why they don't do a RECALL like car industry.

I am wait for long time and still nothing !!!

[TED]

I could not believe my own eyes after spending 450€ in a Gigabyte GA-X99-Designare EX Intel X99 with a clear spec that it supports teaming (and VLANs) and then I attempt to create a miserable VLAN to find an absurd message "Intel(R) Advanced Network Services (Intel(R) ANS) Teams and VLANs are not supported on Microsoft* Windows* 10." I just traded off a 7 year old system (based on the original I7 920) with VERY OLD onboard Realtek cards that could do VLANs beautifully on Windows 10.

Even the intel download section mentions that we should download that driver to support teaming and VLANs. Guys get your stuff together, this can get a law suit against you.

I am absolutely disappointed AND frustrated to see an 8 months thread without any conclusion and to realize that I won't be able to run the necessary VLANs that are required by my network set. Unbelievable.

[CLuce]

Intel has known about it for longer than 8 months. There are discussions here going back at least a year detailing this issue.

Then they sit on their collective thumbs for 6 months saying it's a Microsoft issue, when Windows currently and always has handled VLANs in drivers. So Intel, knowing the ball was in their court, whined about 'a blocking issue from Microsoft' when every other NIC product isn't experiencing the issue. Only their driver doesn't work- but it's a Microsoft issue... Hmmmmm, doesn't pass the sniff test. Maybe they need to hire Realtek or Broadcom to write their drivers.

And they still advertise their product as supporting VLANs and Teaming EVERYWHERE but the actual driver download page. Even the current ANS info page (edited since this issue was known) claims support for VLANs and Teaming.

Straight-up false advertisement, and they won't release the fix they supposedly have because they think an actual working product will cause too much confusion???

Thanks for nothing, Intel.

[TED]

Man, this is un-f-believable. Indeed, they do advertise everywhere about these capabilities. It was a deal breaker for me to buy this motherboard just because of teaming capability and when I finally have my system up and running and try to install the drivers I get screwed by a messaged informing that VLAN and Teaming will be disabled due to lack of support for Windows 10. This is UNREAL. I kid you not, I had VLANs running in an old Realtek onboard NIC (on top of Win10 by 10 months already), the only thing I missed was teaming. I can imagine the level of frustration of everyone in this thread waiting forever for this thing to get sorted. I'm on day one and I still can't believe it. Intel, I would never dream you would be capable of doing that.

[CSetz]

i just want to say that i bought a new pc with intel nic lately and really need vlans too. i dont want to say something further. im just disappointed that this hasnt been resolved for such a long time.

i maybe try and buy a HP adapter and try my luck there if this isnt fixed in the next 2 weeks.

[CKlut]

Carl: Any Update on this?