Ethernet Products
Determine ramifications of Intel® Ethernet products and technologies
5658 Discusiones

I211/I217-V Windows 10 LACP teaming fails

FKurt
Novato
184.155 Vistas

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

1 Solución
CARL_W_Intel
Empleados
144.387 Vistas

OK, lets clear a few things up. Lets start with Windows Release Basics.

Windows 10 Version 1507 (build 10.0.10240), codenamed "Threshold 1"

Windows 10 Version 1511 (build 10.0.10586), codenamed "Threshold 2"

Windows 10 Anniversary Update, or Windows 10 Version 1607 (build 10.0.14393), codenamed "Redstone 1"

Windows 10 Creators Update[202] or Windows 10 Version 1703, codenamed "Redstone 2"

1) MS Windows 10 Redstone 1 is where the fix was rolled out by Microsoft was for Windows 10 Anniversary Update, or Windows 10 Version 1607 (build 10.0.14393). Versions prior to 1607 do not have the hot-fix available. Versions after 1511 are "Redstone 2" which is in Beta has not been released yet.

2) Beta releases of operating systems are not tested and validated on posted drivers on the web. If you install the v22.0.1 driver package on releases after Windows 10, version 1607 you will need to escalate any bugs directly to Microsoft.

3) All the issues I see above on these threads are related to a Beta version of Windows 10. propergol , deecol

4) Famaku , you are on Windows 10 version 10240 ("Threshold 1"). MS did not port the Hot Fix for that OS to TH1. Please upgrade to RS1

5) I don't know about this one MassimoS.. You might want to make sure that your system has all available updates from MS. If that doesn't fix the issue, then the Intel support team will need to look into it.

That's the best I can do. My recommendation is to move the request to a new thread for those systems that are RS1 that have all the correct patches installed (please verify they were successful). That way, it can be addressed as a new issue (which it will be) vs. the OS limitation that this string is about.

Ver la solución en mensaje original publicado

567 Respuestas
MWagn8
Principiante
4.447 Vistas

Adding my vote to get this fixed too. Seems that one can't use VLAN aware VMs or virtual networks (via VMWare Workstation 12 nesting ESXi 6) on Windows 10, also fails because of lack of Windows 10 support for VLANs. Anyone try Windows 10 HyperV to see what happens?

Thanks

DHrad
Principiante
4.605 Vistas

Hello from Europe,

same problem by me.

I have Asus X99E-WS with 2 Intel NIC. (I218 and I210)

I cannot make team´s. Same issue as Cooperdooper with the drivers (original Intel and Asus drivers)

No problem at Windows 7 and Windows 8.1.

Why blocked MS this at Windows 10 ?

CARL_W_Intel
Empleados
4.605 Vistas

There are blocking issues within the OS that prevents the teaming from working correctly. We are working with MS on the issue. Once the OS releases a patch to correct the blocking issue we can release drivers that support the teaming features.

My recommendation is to contact MS and ask when their OS will support teaming again.

RBirk
Principiante
4.605 Vistas

Hi,

Just for statistical purposes I have the same issue with Intel Nic Teaming on Windows 10. My configuration is almost the same as Famaku.

Board: ASRock Z87 Extreme 6 a/c (Intel Z87 chipset)

Onboard NIC: Intel I217-V + Intel I211

OS: Windows 10 Professional x64 Build10586

Drivers from Intel and Asrock webpage not working.

I hope it will be sorted out until free upgrade to Windows 10 is available.

Regards,

badzi0r

PChec1
Principiante
4.605 Vistas

I've contacted MS but there is no way to get through their thick customer support line. Does Intel know if this is going to be addressed?

CARL_W_Intel
Empleados
4.447 Vistas

I've requested from my engineering team to let me know as soon as both 1) the MS Hotfix is released, and 2) when we plan to re-release the driver to support these features. As soon as I am aware, I will post on this string.

ssupo
Principiante
4.605 Vistas

Hi,

Unfortunately, I have the same problem.

Before windows 10 update, all vlan works perfectly.

Now I cannot use VLAN with anyone driver version.

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

OS Windows 10 PRO x64.

HP Computer, Intel Hardware, Microsoft Software !!! All regularly purchased.

It's is really true that I will need to change hardware or maybe complain to the ???????.

 

I really need VLAN to Work... !!!

Someone need to solve these problems.

Regards.

Mario.

CARL_W_Intel
Empleados
4.605 Vistas

There will be two actions that will be required in order to get Teaming and VLANs working under Windows 10.

1) Once the OS fix has been identified (either through a Hot Fix or Knowledge Base Article), users will need to implement those changes.

2) Intel will need to release a Windows 10 driver that re-enables the capabilities.

At this point, we need to have # 1 identified before we can proceed with a plan for # 2.

I will update this post once I have more information

RBirk
Principiante
4.605 Vistas

Thanks in advance.

Meanwhile I have restored Windows 8.1 from backup.

LGran4
Principiante
4.447 Vistas

+1 with the same issue. Can't create vlans in windows 10 with the latest intel 20.4.1 driver.

Is this Windows issue (that needs the hotfix) exclusive to Intel NICs?

Because teaming and vlans works fine for me with the latest Windows 10 and a realtek nic.

CARL_W_Intel
Empleados
4.447 Vistas

This is relation to how Windows works with our specific SW implementation with any of our advanced features. It requires MS Hotfix/SP to correct before we can re-enable the drivers.

MMath7
Principiante
4.447 Vistas

Hello Carl,

we own 2 X710-DA4 and 2 X520_DA2 and of course, we are faing right the same problem described in this thread with teaming and windows 10 pro.

Do you have some hint about the probability the MS fix will eventually show up and the expected timeschedule ?

I understand this affects only a tiny fraction of Windows 10 users but this is still a quite serious regression, I hope you Intel guy have means to put some pressure on them about that.

By the way, I have a second issue that may be related :

one X520-DA2 is installed on a Dell Precision T7500 station, and both links are hooked to an Arista DCS7124S switch in DAC mode (1 m cables)

OS is Windows 10 pro.

Only one link (# 2) detects the connexion and the other one remains "unconnected" on both switch and computer sides.

If I move this second link to one of the Netgear Prosafe 728TXS switch rigth above, both links are detected correctly. Any clue ?

Regards

NAlle1
Principiante
4.446 Vistas

Hello, I was just wondering if anyone took a registry Snapshot of a older windows 10 build with working team then update and do a compare Wint the Broke build to see if there is changes in the registry that is ether missing or changed that applys to ANS or the windows network stack in general. Maby there is a string in the Registry that is missing or passably we could do a file compare to find out what patched file broke it I do believe the KB artical for that patch should list affected files

BBolf
Principiante
4.459 Vistas

This is absolutely ridiculous. No wonder my company is just now settled in with windows 7. At least we know it still works!

BBolf
Principiante
4.459 Vistas

Just installed Windows 2016 Server Technical Release 4 and seems to a working feature there.... I hope this isn't something they are omitting from Windows 10 Pro.......

CARL_W_Intel
Empleados
4.459 Vistas

The issue is with Client-based Windows OSes. Server does not have the issue.

MZies1
Principiante
4.459 Vistas

FYI, cross-linking to http://hardwarerecs.stackexchange.com/questions/2422/usb-to-ethernet-adapter-supporting-multiple-virtual-lans networking - USB to Ethernet adapter supporting multiple virtual LANs - Hardware Recommendations Stack Exchange . This includes details as to why this support is needed by many of us asking here.

Also, 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. We're not aware of any USB Ethernet adapter that provides such capabilities for Windows, nor have we seen any other vendors creating any USB Ethernet adapters of their own that would compare to their internal components. (Hint, hint! Build it, and then http://knowyourmeme.com/memes/shut-up-and-take-my-money take our money!)

EAlle2
Principiante
4.404 Vistas

Sorry to be a noob, but will there be a driver update that allows teaming for my I340-T4?

I'm just about to reach the end of my return window with Amazon and need to make a decision. I was following this thread waiting for an Intel person to announce the release, but the last few posts are making me wonder if my card is reaching EOL and will not get an updated driver.

Thank you.

CARL_W_Intel
Empleados
4.404 Vistas

Yes. There will be a driver release in June for this card which will enable teaming and VLANs once again.

EAlle2
Principiante
4.404 Vistas

Thank you Carl.

Everyone,

This card says it uses the 82580 chip and it will be getting a driver.

jkim931
Principiante
4.404 Vistas

will the new drivers work with the Intel x540-t2 10Gbe nic cards?

Responder