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

[CARL_W_Intel]

Unfortunately, after a full test and validation run, it was determined that the hot fixes introduced new issues that prevented VLAN/teaming support from being re-enabled in this release. I have escalated to the SW development team for a plan and point release. As soon as I have more details I will provide it.

[idata]

What is your confidence in this happening in June at this time?

I certainly understand your need to get information from them to be able to forecast with a higher degree of confidence, but given what was found in testing and validation and taking into account the development teams normal cadence, would it be unheard of to see a fix for this turned around within a few weeks or are we talking months (i.e, no matter how simple the fix, it's going to be at least on the order of a few months to complete all testing procedures)?

Thanks for the update!

Joey

[RJarr]

8 months waiting to have the drivers working... Very pathetic

[CGros3]

Intel has been working on it as well as they can for this relatively niche feature. Put all the blame on Microsoft.

[idata]

Any updates on this in the last few weeks, Carl_Wilson?

[MKarl2]

Any updates?

This is really rather frustrating, as when I originally upgraded from Windows 7 Pro to Windows 10, teaming was working, and then it stopped working.

I'm trying to team my two onboard intel chips. (82574L and 82579V).

The most frustrating part is that this is a dual boot machine. I priomarily use Linux, and almost never boot up in Windows. (Only occasionally when I feel like distracting myself with a game).

Teaming works great in Linux with the Linux Kernel bonding driver, but every time I boot into Windows now, I have to unplug my teamed connection and plug a single wire in, or it doesn't get any network connectivity at all. The real kicker is, I don't even need teaming in Windows. I only use it for the occasional game. It's just really frustrating to have to unplug and plug back in Ethernet cables every time I boot into it.

One of these days Windows just won't be worth booting into anymore. I've just about had it.

Please advise on the status!

[HHawk2]

Sheesh Intel is also going downhill rapidly.

Still no possibility to create a team with Intel PRO/1000 PT Dual Port Server Adapter. They don't even care about support.

And I was told nonsense a few months ago here: This was on my home machine.

I use the Dual Port here for work, but without teaming, I think it's time to move on to a more reliable brand for our networking needs.

[CARL_W_Intel]

Nomgle is correct. The only driver packages that are certified for use on Windows 10 are the ones outlined in the post above (for teaming, once the OS is patched to support it).

And this makes sense. The Ethernet Controller on the Intel(r) PRO/1000 PT Dual Port Server Adapter card you are using is built using the Intel(r) 82571EB Gigabit Ethernet Controller (http://ark.intel.com/products/20720/Intel-82571EB-Gigabit-Ethernet-Controller?q=82571eb Intel® 82571EB Gigabit Ethernet Controller Specifications), which launched in summer of 2005 and has already announced EOL. The last Microsoft certified driver for that card was for Windows 7/Windows Server 2008 R2. After those OS releases, Microsoft no longer provides WHQL driver certification for Intel's publically released drivers for any new operating systems (due to a lack of features required for WHQL certification). This means that the driver moves from an Intel supported/released driver (from the Intel web site) to what is known as 'inbox driver' - meaning the driver is included native "in the box" of the Operating System (with the driver support goes through the OS vendors at this stage).

Since Windows 8.1/Windows Server 2012 and beyond - the driver for any products based on the 82571EB are only inbox. Unfortunately, MS does not have native LBFO support for their client OSes, therefore Teaming on any 'inbox only' driver is not possible. For Windows 8/Windows Server 2012, Intel did release a driver on our public download site for those customers requiring teaming, however these drivers were not WHQL certified. For Windows 10, the silicon was just too old to take this extra step.

Due to the age of the controller (10+ years old now), and the lack of silicon features required to receive WHQL certification - Intel's driver support team can no longer even work on new OS support for this silicon (or the card). My recommendation is use a card or controller that is on the Windows 10 support list to take advantage of the features you are looking for. We do support teaming in Windows 10 Client with the silicon listed in Nomgle's post.

* Disclaimer. I am an Intel employee, and own the silicon that is on the Intel(r) PRO/1000 PT Dual Port Server Adapter. In fact, I owned it before it launched.

[N_3]

Thanks for the update Carl.

I updated a few of my machines to the latest build of Windows 10 today - Version 1522 Build 10586.3 ... and it broke my working Team.

For some reason the "Upgrade" process replaced some of my drivers with the Microsoft Inbox versions ! Once I'd got my Intel RST and Intel ProSet and Creative Audio drivers installed again, I got the teaming options back in Device Manager.

But after creating a Team, it only shows in Device Manager - it does not show in Network and Sharing Centre (ie, Windows 10 doesn't even recognise it as a network device). So no Teams at all now.

I'll also point out that Windows 10 replacing my Network drivers left me with ZERO connectivity until I reinstalled ProSet - so if you're doing this on a Remote machine, you'll be screwed after the upgrade completes.

[RJarr]

Got Windows 10 64b 1511 10586.3

Today, I've tried to install a teaming on my Intel(R) Gigabit ET Dual Port Server Adapter, I haven't the option to active the teaming

Then tried another network card Intel(R) Ethernet Server Adapter I350-T2 (suposed to work), I have the option button, but always greyed out, can't active

It was working fine with Win7, Win8, Win8.1

I'm very desapointed by the Intel drivers

[ASiga]

Oh, man... I was hoping it was some odd bug on my machine. Prior to this latest "November Threshold" Win 10 update, my Ethernet Server Adapter I350-T4 was working great. I used LACP to my switch with four Cat-6 cables and was loving life. Now I have four separate NIC channels, my surveillance software is confused by my machine having four different IPs and nothing works...https://downloadcenter.intel.com/product/59063/Intel-Ethernet-Server-Adapter-I350-T4

[CARL_W_Intel]

Nomgle , When you upgrade to a new Operating System such as Windows 10, your drivers will up 'updated' by the OS install to what the OS has certified as current (in other words, what it will support). Unfortunately, this means that the hardware you were using before becomes subject to the OS WHQL certifications required for that version of the OS. Thus, the loss of teaming. (This again is due to the fact that inherently, the OS does not support Teaming, and the controller silicon on the adapter you used before does not have WHQL certifications for that OS.) IN this instance, a PROSet reinstall still will not allow for teaming to setup (it requires a device to initial the team that the OS will support as WHQL certified). To support teaming using Intel hardware under Windows 10, you will need a device that has a certified driver for Windows 10 (see my post above for why).

mimi74, you are in the same boat with the Intel(r) Gigabit ET Dual Port Server Adapter, which is based on the 82576EB controller which launched in Q2'08. Like the 82571EB controller, it also does not have Windows 10 driver from Intel (only Inbox from Windows 10). The last 'Retail' driver available for that controller is Windows 8 and Server 2012. Windows 8.1 and Windows 2012 R2 and beyond are inbox only support. The Intel(r) Ethernet Server Adapter I350-T2 should work with Teaming etc., assuming you have the most current driver.

VirtualPanther and mimi74, you should also be able to download our latest driver from the Intel support site for Windows 10 for the I350-based cards. This also should allow you to create a team from the Windows device manager (there is no longer a separate PROSet application as it is integrated into Device Manager). Once you create a team you will be able to have the 1 IP address you need for your application and switch. My guess is when you upgraded the Inbox Driver that is native to the OS removed your teaming settings. Installing the Windows 10 driver from our web site should allow you to reconfigure the team you need.

[ASiga]

So... The only download I have for the I350-T4 card for Win 10 x64 is here: https://downloadcenter.intel.com/download/25016/Network-Adapter-Driver-for-Windows-10 Download Network Adapter Driver for Windows® 10

I downloaded it, right after installing the dreaded Win 10 v1511 threshold update. It is https://downloadcenter.intel.com/downloads/eula/25016/Network-Adapter-Driver-for-Windows-10?httpDown=https://downloadmirror.intel.com/25016/eng/PROWinx64.exe PROWinx64.exe and it installs in a similar fashion as before, but teaming is disabled, with pretty much the same note as on the download page: doesn't work on Win 10. I do not see a way to create a team to test if it will function and my previously created and working teaming for this card on Win 10 was destroyed by the threshold update. I do not see any other driver available anywhere else. I am more than willing to try something, if you know where I can get it. In response to my support ticket with Intel Networking, the answer was to blame Windows 10, with a suggestion to contact Microsoft

[RJarr]

Then I've tried another network card Intel(R) Ethernet Server Adapter I350-T2 (suposed to work), I have the teaming option button, but always greyed out, can't active

It was working fine with Win7, Win8, Win8.1 !

Perhaps I've forget to explain with the last drivers 20.4.1

[ASiga]

Here is the reply I received from Intel Support:

This is on regards of service ticket 184630.

In order for you to get teamning working you will need to get Intel(R)Advanced network services

set up with the operating system but Windows(R) 10 is not supported for this feature.

Creating Intel® ANS teams and VLANs on Microsoft Windows® 10 is currently not supported.

As a result, when created, teams and VLANs do not pass traffic.

We expect that ANS will be supported on Microsoft Windows 10 client in a future release

The future releases will require modifications from Microsoft in the O.S, unfurntately

it is not possible for us to provide an ETA.

We will not be able why it worked before since we are not Microsoft support we will not have the information

about the previous update you installed.

In this case we may suggest you to contact Microsoft support to check if they have another solution available

since their update was taking that feature away and and from us Intel this feature will not be supported on your

operating system.

Please let us know if further assistance is required and/or if we can proceed to close this service ticket.

We will be waiting for your response.

Have a great day!

Regards,

========

Intel Customer Support

[CARL_W_Intel]

VirtualPanther Yes, that is correct. My steps will be for once it is re-enabled within the OS framework. Sometimes a get a bit ahead of myself.

We had hoped the potential fix expected in the August 27, 2015 Microsoft release of KB3081448 would correct the OS limitation, but our testing revealed that the blocking issue still exists. Although it doesn't appear to be a driver issue, we are continuing to work with the MS Windows 10 NDIS teams in Redmond to root cause the issue.

Due to the OS limitation we are still seeing, this why you get a warning message during the PROset install on Win10 that should warn you that you will be unable to create VLANs/Teams. This is also why you see those fields grayed out the tabs in advanced properties. Once the issue is root caused and a fix identified, we can then re-enable the ANS functions (Teaming and VLANs). I will also post a reply to this thread when I hear anything.

The key thing is you have the right I350 silicon to enable it since the driver will have WHQL certifications.

I would also suggest pinging the Microsoft Windows 10 team for a status. A bit more noise in the signal can't hurt.

[DBrun6]

Hello, are there any news about this? I have a I218-v and I211, everything was working fine in Windows 8.1.

I thought these two cards were supported in Windows 10, but if I install the Intel drivers the teaming option is greyed out.

If I use the drivers supplied by Asus, the option is available. I create the team and everything seems fine, but the the team NIC stays disabled and if I try to enable it it says "enabled" and then it stays disabled all the same. No way to enable it.

So I hope this gets worked out.

[SHuan51]

Carl I am disappointed that the Intel ET dual port server adapter will not have Windows 10 drivers. Intel website still lists this card as launched and not end of life and that is why I purchased the card.

[CARL_W_Intel]

There are Windows 10 drivers for this card, however they are only available as base drivers found in Windows 10. The Controller on the board (the Intel(r) 82576EB Gigabit Ethernet Controller) does not pass the Microsoft WHQL certifications required for a full featured driver from Intel. Thus, the basic driver included within the OS. Windows 10 does not have a native teaming capability to bond the two ports together.

[KKuhl]

So Microsoft disabled (removed support) for ANS teaming with the great (sarcastic) 1151 patch, and since they probably don't care about the relatively small number of consumers that use ANS teaming, I suspect they never will issue a patch or Hotfix. I don't see Microsoft changing their position, especially since the heart of the matter is the chip (82576EB) on the NIC and WHQL testing.

Is this problem limited to older cards or does it affect all Intel multi-port NICs? If this only affects a portion of Intel NICs, does Intel have a list of cards that pass WHQL (newer/different controller) and still support ANS teaming (link aggregation)?

[LGran4]

Well, my card is neither old or multiport. I have a NUC with the I219-V (launched Q2'15). Still no ANS support. It's rather disappointing.