Содержание

How to Set up Teaming with an Intel® Ethernet Adapter in Windows® 10 1809?
Is Windows 10 Software NIC Teaming now possible?
4 Answers 4
Creating a NIC team on Win10 1809
12 Replies

How to Set up Teaming with an Intel® Ethernet Adapter in Windows® 10 1809?

Validated. This solution has been verified by our customers to fix the issue with these environment variables

Content Type Install & Setup

Article ID 000032008

Last Reviewed 08/27/2019

Teaming configuration is not available anymore in Device Manager after upgrading to or installing Windows® 10 October 2018 Update (also known as version 1809 and codenamed Redstone 5 or simply RS5).

Windows® 10 supported Intel® Ethernet Adapters.

Follow the steps below in the given order:

1. From Device Manager, disable the NIC device.

2. Remove all drivers and Intel® PROSet software as follows:

2.1. Access Device Manager*.

2.2. Expand Network Adapters.

2.3. Right-click each entry of an Intel® Ethernet Adapter.

2.4. Click Uninstall Device.

3. Once the adapter is uninstalled, cold boot the system (power off and then back on completely).

4. If the device is still disabled, enable it.

5. Download and install the latest driver for your Intel® Ethernet Network Adapter just doing double click on the file. If instead of the dedicated driver you downloaded the Complete Driver Pack, please install it as follows (if you downloaded an installer, which usually is a file with the extension .exe, you can skip these steps and continue from Step 6):

5.1. Open the Command Prompt as an Administrator.

5.2. Access the folder that is made after having unzipped the Intel® Ethernet Adapter driver package.

5.3. Within the Command prompt, go to APPS > PROSETDX > Winx64. In this folder, run the following command to install the driver along with PROSet and the Advanced Network Settings: DxSetup.exe BD=1 PROSET=1 ANS=1

6. Reboot the computer.

7. Open the Windows* PowerShell, as Administrator, and proceed as follows:

7.1. Run the following command (see below), which should take a few seconds, and it would not show any confirmation; it would just go back to the blinking cursor:

Import-Module -Name «C:\Program Files\Intel\Wired Networking\IntelNetCmdlets\IntelNetCmdlets»

7.2. Proceed adding team(s) by running this other command: New-IntelNetTeam

* This is an interactive tool. It will start by asking the Team Member Names. These names can be confirmed by the names of the ports in Device Manager > Network Adapters. For example, port 1 might be called Intel(R) Ethernet Server Adapter I350-T2V2 and port 2 might be Intel(R) Ethernet Server Adapter I350-T2V2 #2 (just an example of setting up a team using two ports within a single adapter). Alternatively, one can follow the following command line: New-IntelNetTeam -TeamMemberNames «», «» -TeamMode AdapterFaultTolerance -TeamName » «

* As for the different team types/modes (see the list below), please enter only the exact text that comes before each explanation, without spaces, bullets or dashes:

AdapterFaultTolerance — Provides automatic redundancy for a server’s network connection. If the primary adapter fails, the secondary adapter takes over. Adapter Fault Tolerance supports two to eight adapters per team. This teaming type works with any hub or switch. All team members must be connected to the same subnet.
SwitchFaultTolerance — Provides failover between two adapters connected to separate switches. Switch Fault Tolerance supports two adapters per team. Spanning Tree Protocol (STP) must be enabled on the switch when you create a Switch Fault Tolerance (SFT) team. When SFT teams are created, the Activation Delay is automatically set to 60 seconds. This teaming type works with any switch or hub. All team members must be connected to the same subnet.
AdaptiveLoadBalancing — Provides load balancing of transmit traffic and adapter fault tolerance. In Windows* operating systems, you can also enable or disable receive load balancing (RLB) in Adaptive Load Balancing teams (by default, RLB is enabled).
VirtualMachineLoadBalancing — Provides transmit and receive traffic load balancing across virtual machines bound to the team interface, as well as fault tolerance in the event of switch port, cable, or adapter failure. This teaming type works with any switch.
StaticLinkAggregation — Provides increased transmission and reception throughput in a team of two to eight adapters. This team type replaces the following team types from prior software releases: Fast EtherChannel*/Link Aggregation (FEC) and Gigabit EtherChannel*/Link Aggregation (GEC). This type also includes adapter fault tolerance and load balancing (only routed protocols). This teaming type requires a switch with Intel® Link Aggregation, Cisco* FEC or GEC, or IEEE 802.3ad Static Link Aggregation capability. All adapters in a Link Aggregation team running in static mode must run at the same speed and must be connected to a Static Link Aggregation capable switch. If the speed capability of adapters in a Static Link Aggregation team are different, the speed of the team is dependent on the lowest common denominator.
IEEE802_3adDynamicLinkAggregation — Creates one or more teams using Dynamic Link Aggregation with mixed-speed adapters. Like the Static Link Aggregation teams, Dynamic 802.3ad teams increase transmission and reception throughput and provide fault tolerance. This teaming type requires a switch that fully supports the IEEE 802.3ad standard.
MultiVendorTeaming — Adds the capability to include adapters from selected other vendors in a team.

8. Finally, it is just required to set any chosen name for the new team. Device Manager will confirm that the system is detecting the new team.

Cause & More Information:

Related topic

THE INFORMATION IN THIS ARTICLE HAS BEEN USED BY OUR CUSTOMERS BUT NOT TESTED, FULLY REPLICATED, OR VALIDATED BY INTEL. INDIVIDUAL RESULTS MAY VARY. ALL POSTINGS AND USE OF THE CONTENT ON THIS SITE ARE SUBJECT TO THE TERMS AND CONDITIONS OF USE OF THE SITE.

Is Windows 10 Software NIC Teaming now possible?

Windows Server 2012 brought with it NIC teaming of adapters by different manufacturers.

I mean teaming using 1 NIC from say Intel and the other from Realtek. It has been possible to do teaming or bonding at the driver level, but what was introduced in Windows Server 2012 is at the operating system level. I appreciate Linux has been doing this for years 🙂

It didn’t make it onto Windows 8/8.1. I’ve seen some article where people reported it was working on Windows 10 Preview but no longer working.

Is NIC Teaming supported on Windows 10 Pro? Or another edition.

4 Answers 4

This has been disabled in the most recent version of Windows 10 as well as the insider build 14295. The powershell command will error out or say that LBFO is not supported on the current SKU depending on the versin of Windows you are running. Hopefully MS will re-enable this feature sometime soon.

— Original Post Below —

Yes, This is possible! To anyone else who found this post by Googling:

I haven’t found a way to access this though a GUI, but running the following PowerShell command will create a team for you. Just replace the Ethernet names with your NIC names.

New-NetLbfoTeam TheATeam «Ethernet»,»Ethernet 6″

You should then get a 2GBs Switch Independent team. From there you can use the Network Connections screen to set it up how you want.

It seems this feature is coming back, at least for Intel NICs:

Intel mentions teaming support for Windows 10 in driver versions 22.3 or newer. Currently 23.5 is available.

This version comes with ANS (advanced network services, installed by default) which should allow teaming via powershell commands.

I havent tried it yet — the only mainboard I have with two intel nic’s is a bit bios upgrade stubborn.

If anyone could get this to work with the latest windows creator update mentioned in the release notes, let me know 🙂

Update: tried link aggregation on Windows 10 — so currently it works (Jan 2019)

An iperf3 run from two clients shows it seems to work:

No it is not possible to get NIC teamin in Windows 10 client SKUs. But available for Server SKUs.

From 14393 version (Anniversary update) this NIC teaming feature had been blocked or removed forever. It is seemed that the feature mistakenly added to client Windows 10 SKUs. When you put New-NetLbfoTeam command in PowerShell e.g. New-NetLbfoTeam -Name «NewTeam» -TeamMembers «Ethernet», «Ethernet2» , the error shows as follows

New-NetLbfoTeam : The LBFO feature is not currently enabled, or LBFO is not supported on this SKU. At line:1 char:1 + New-NetLbfoTeam -Name «NewTeam» -TeamMembers «Ethernet», «Ethernet2» +

+ CategoryInfo : NotSpecified: (MSFT_NetLbfoTeam:root/Standa rdCimv2/MSFT_NetLbfoTeam) [New-NetLbfoTeam], CimException + FullyQualifiedErrorId : MI RESULT 1,New-NetLbfoTeam

The main reason was given in Social.TechNet.Microsoft: Nic Teaming broken in build 10586 as follows (quoted):

«There are no native LBFO capabilities on Win10. Microsoft does not support client SKU network teaming.

It was a defect in Windows 10 build 10240 that “New-NetLbfoTeam” wasn’t completely blocked on client SKUs. This was an unintentional bug, not a change in the SKU matrix. All our documentation continued to say that NIC Teaming is exclusively a feature for Server SKUs.

While the powershell cmdlet didn’t outright fail on client, LBFO was in a broken and unsupported state, since the client SKU does not ship the mslbfoprovider.sys kernel driver. That kernel driver contains all the load balancing and failover logic, as well as the LACP state machine. Without that driver, you might get the appearance of a team, but it wouldn’t really do actual teaming logic. We never tested NIC Teaming in a configuration where this kernel driver was missing.

In the 10586 update (“Fall update”) that was released a few months later, “New-NetLbfoTeam” was correctly blocked again.

In the 14393 update (“Anniversary update”), we continued blocking it, but improved the error message.»

Creating a NIC team on Win10 1809

IT would appear that Microsoft has gone to lengths to ensure that NIC-teaming is no longer supported by any vendors on their client operating system. Namely Win10 1809 (haven’t tried in 1803)

(this is not about the NetLBFO commands that was included in Win10 at release by a fluke)

We have mostly intel NICs, but there are a few other manufacturers also thrown into the mix.
Both Intel and Realtek (at least) had a simple way to do this from a GUI in Intel Advanced Network services, and RealTek Ethernet Diagnostic Utility. But both are now crippled and does not support teaming or vLans.

We can still use intels Powershell applets to set up and administrate teams, but this requires at least one of the NICs (not really strange) to be an Intel NIC.

Microsoft refers to third party software that I can not seem to find, and intel has not even yet updated their website to reflect this

Has anyone had any success teaming non-intel NICs in Windows10 1809?

I can not find the one you link to 2.0.3.0 anywhere on an official Realtek site, but did find it online an have tried that as well now, still no change.

Using the latest (that I can find) Realtek drivers 10.28.1002.2018.

Newest win10 drivers of 10.031, all the diagnostics software, etc.. it’s the only offficial realtek site I know of, and the same source of the link I posted before.

I would not be surprised if your hypothesis is correct and the mfgs are removing the NIC teaming from the drivers because Microsoft’s is supposed to be vendor independent.

12 Replies

I have not tried it now (don’t have a non-Intel PC around here), but I guess, that the following powershell command should do the trick:

New-NetSwitchTeam -Name «SwitchTeam01» -TeamMembers «Ethernet 2″,»Ethernet 3»

Not tested here … 🙂

[EDIT]
I have just seen, that it is related to Hyper-V

Maybe «New-NetLbfoTeam» is the command to do that job.

«The New-NetLbfoTeam cmdlet creates a new NIC team that consists of one or more network adapters.»

Intel requires the use of their ANS software on windows 10. It does work.

They make a specific note about teaming and versions required: If you’re running Windows® 10 Creators Update (RS2) and are using Intel LAN software release v22.1 or v22.2, then ANS won’t function until you update to the Intel® LAN software v22.3 or newer.

Realtek requires the Nic Teaming protocol driver to be manually installed first from the Diagnostics software folder. It does not auto install the protocol driver anymore. the file is «0004-Diagnostic_v2.0.3.0_AllInOneRel_0803» (looks like you already had the download)