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]

I didn't say it didn't work.

I asked if anyone had tried it.

[GCatt]

Read one page back. Someone tried it on Windows 10 1703 and ANS doesn't work.

[JAase]

What do you know.

Build on final RS2 is 1703, NOT 15063 . It's out on MSDN now.

Anyone tried it?

Since it's oficially out on MSDN now, and rollout is starting tomorrow, I would guess we will have new working drivers within a few weeks ... it they don't work on 1703.

[CLuce]

johnkristian wrote:

Build on final RS2 is 1703, NOT 15063 .

1703 is Version. 15063 is Build. RedStone 2, commonly known as "Creator's Update" is Windows 10 Version 1703 Build 15063.14.

If you right-click on the Start Button, then click 'System', on RS2 it will show:

Edition: Windows 10 xxxxxxx where x = Home, Professional, Enterprise

Version: 1703

OS Build: 15063.14

All this pedantry over version/build/name is not helping. Intel says these features work on Windows 10. For the majority of the time Windows 10 has been available, they have not. That needs to change.

[CARL_W_Intel]

RS2 ANS/teaming will be supported in revision 22.3 of the SW driver, due out the end of May/early Jun 2017. This is to fix a new issue not related to the blocking issue with RS1. I will also update the other thread.

[CLuce]

Is it now the policy of Intel to offer very limited support for flagship features on their NICs? It seems ridiculous to pay as much as Intel is asking for NICs and never knowing if the the features are going to break, and waiting a year and a half for them to be resolved.

In this specific case, End of May is outside the 35-day update delay allowed by Windows 10. Any Windows 10 Intel ANS customer not on LTSB is going to have promised functionality broken, AGAIN. Is Intel doing anything to address the big picture issue of their premium features not being reliable?

[LJ]

Not sure whats happened here but without teaming both my NIC's windows 10 Creators (15063.13) is now abled to transfer files @235MS/s Checking both nic's via task manager/Performance and i can see both nic's running at 998mbps. So it seems MS have done something that makes both nic's team without using intels ANS. Can some else confirm this?

Update: SO it seems MS have deployed code within Creators Update (15063.13+) which bonds multiple ethernet ports together automatically . Vlans and teaming will not work via ANS as you know. So the picture im building is this... MS have allowed windows 10 to Auto team (bond) without any user config. This is probably why intel cant get teaming to work. As for Vlan..... We could be seeing the end of this with win10 if this is in fact the way MS is going. Maybe MS has future plans to add Vlan to the OS but for now im guessing this is the end for intel's ANS?.

[rShie1]

Whats your setup? Managed switch? Please tell use what you did. Thanks.

[DMcCo3]

Thanks for pointing that out! I have gotten used to either disconnecting one of the network cables or disabling one of the ports with the updates/upgrades until installing ANS drivers as it'd cause whatever Windows OS not to function network wise in the past. Seems to work well enough with what it's doing so far. Looking forward to future ANS versions but at least have something in the meantime.

[GCatt]

On Windows 10 Pro, Enterprise, and Education editions, you can set a group policy to delay feature updates for up to 180 days. Read this article to find out how:

http://pureinfotech.com/prevent-windows-10-installing-creators-update/ How to prevent Windows 10 from installing the Creators Update • PUREinfoTech

Cheers!

[LJ]

I dont believe my setup has anything to do with this, I do have a managed switch but done no config, In fact my switch has been at default ever since ANS stopped working. i have also noticed MS bonding/Teaming only works from Windows to windows systems running latest version of Windows10, My NAS boxes have dual ethernet and i cannot get any of my windows systems (8) to transfer to Nas aboxes above 115MB/s (even thous NAS boxes are using donded ethernet). This maybe due to switch config but ill be looking into this today and will report back.

Carl_Wilson has suggested a newer driver will be availble in may/june (thats as insult to users IMO) but if this is the direction MS is taking Networking within windows then i wouldnt use ANS anymore because i see a world of conflict between the two.

TBH i'd would rather MS take over networking features because Intel developers havnt got a clue and there time scale for updates/fixes is a freaking joke at best. Roll on RYZEN.....!

[CUllr]

Memories4Life wrote:

without teaming both my NIC's windows 10 Creators (15063.13) is now abled to transfer files @235MS/s

Is it possible what you are seeing is this? https://blogs.technet.microsoft.com/josebda/2012/06/28/the-basics-of-smb-multichannel-a-feature-of-windows-server-2012-and-smb-3-0/ The basics of SMB Multichannel, a feature of Windows Server 2012 and SMB 3.0 – Jose Barreto's Blog

I cannot find any mention of this being newly available in 1703 for when the server is a client version, but who knows? If this surprising speed improvement only affects file transfer, this might be the reason. The headline says "a feature of Windows Server 2012", but the linked article mentions, among the requirements, "[a]t least two computers running Windows Server 2012 or Windows 8". This might be interpreted to mean that it has worked between clients from the start.

I don't suppose you have never tried it with two interfaces on each side before, have you?

[LJ]

chrullrich that is what im experiencing. So this is what MS have included in 15063.XXX which now explains why intel are not abled to have ANs working. Sounds like ANs is in conflict with SMB Multi 3.0. i'd rather MS take over/include all nework tools vlan/teaming etc as intel are way too slow.

I don't suppose you have never tried it with two interfaces on each side before, have you? Not sure what you mean?

[CUllr]

Memories4Life wrote:

chrullrich that is what im experiencing. So this is what MS have included in 15063.XXX which now explains why intel are not abled to have ANs working. Sounds like ANs is in conflict with SMB Multi 3.0. i'd rather MS take over/include all nework tools vlan/teaming etc as intel are way too slow.

I don't suppose you have never tried it with two interfaces on each side before, have you? Not sure what you mean?

You know, I keep being amazed at what conclusions people reach from zero, and even contrary, data.

• There is no evidence that SMB3 multichannel has not been available between (only) client SKUs before. Perhaps your environment recently changed in some way that now allows it to work.
  • There are plenty of posts on various forums that at least imply that multichannel connections between client OSs have been working since Windows 8.1 at least.
• Unless you have packet traces to that effect there is, in fact, no evidence that SMB3 multichannel is even responsible for your transfer speed, although it does appear likely.
• There is no evidence whatsoever that the current lack of ANS functionality on 1703 has anything at all to do with the availability of SMB3 multichannel.
• On the contrary, @Carl_Wilson recently stated that ANS will be working on 1703 with a driver release expected in late May, which I interpret as meaning that the current drivers were never meant to work on 1703 from the start.

Wishing for Microsoft to provide this functionality rather than the hardware manufacturer is also surprising, given that this entire thread exists only because Microsoft consciously decided to withhold it from client OSs.

When I asked about using two interfaces on each side, I meant whether this might be the first time you had the opportunity to notice increased speed because you did not have two parallel network interfaces on both systems involved before. Just a guess.

[LJ]

For the past 2 yrs i have had multi Nic's open on 8 systems waiting for intel to fix this. Up untill last week the Max speeds i was getting was 115.MB/s using only 1 nic out of multiple installed on 1 system. Last Tuesday i update to RS2 (15063.13) then noticed my speeds had gone up to 235MB/s (2 Nic's). Yesterdays update 15063.138 and all is the same. So it does look like SMB (props for finding that artical) is what is allowing this to happen (but only between win10 clients), i also removed intel drivers today and re-installed (different versions) without installing ANS and system is still bonding the Nic's.

IMO.. Networking is an important part of todays systems and if intel cannot provided working drivers that fully support all protocals then step aside and let MS deal with it. Realtek had the same problem and issued a fix promptly why has intel taken over 2yrs?

[JAase]

Multichannel SMB works on win10 and is nothing new, and has nothing to do with this post:

https://www.youtube.com/watch?v=K4VnWQPW-f4 https://www.youtube.com/watch?v=K4VnWQPW-f4

https://www.youtube.com/watch?v=K4VnWQPW-f4 Quadruple Your Network Speed for $100 with SMB 3.0 Multichannel! - YouTube

Carl Wilson has been wery clear what we can expect, and has explained well that (not why) current drivers doesn't work in build 1703. So keep calm and carry on.

I've had intel wifi issues with the RS2 build, but it doesn't have to do anything with this post ... what happend to staying on topic?

[ssean3]

OOOOOOFFFF

I thought for sure this issue was fixed, but then as soon as I upgraded to 1703, my team was gone. I can add a new team, but the NIC team stays disabled.

When this happened last year, you couldn't even add the team, but now you can add a team, but it sits there disabled.

So is there an "official" statement from Intel stating the the new builds of W10 will cause teaming to fail?

What a mess.

[ssean3]

ALSO:

After you remove the non-working team and try to reapply that same IP that was used by the Team you'll get an error like the following:

"The IP Address xxxxxxx you have entered or this network adapter is already assigned to another adapter "Team1" ....

When I initially set this up I remember you had to delete some registry values in order to free up that IP address again.

I searched around, but I can't find that Intel article.

ANYONE? Our webserver has been down for a good 6 hours now.

Cool.

[CLuce]

Smartest thing you can do is roll-back the update.

[ssean3]

ROGER THAT. However, it looks like they won't have an update to the driver until JUNE?! I mean, if it goes anything like last year, add 3 months on to that.

Impossible to go that long without updating.

Also, if anyone needs to uninstall their team, going thru the NIC properties won't remove it completely.

Gotta do this:

http://www.intel.com/content/www/us/en/support/network-and-i-o/ethernet-products/000005781.html Unable to Uninstall Teams, Intel® Network Connections, or Intel®...

[JAase]

oh, ok.