F5F Stay Refreshed Hardware Desktop NIC partnerships 2021? Windows 10 or 11?

NIC partnerships 2021? Windows 10 or 11?

NIC partnerships 2021? Windows 10 or 11?

T
thdj432
Member
54
04-12-2021, 01:01 AM
#1
Is there a solution for Windows 10 that supports NIC teaming? Also, does Windows 11 currently permit NIC teaming? I'm interested in setting up multi-gigabit local networks and have looked through old threads, but they seem outdated. With the latest Windows 10 updates and the new Windows 11 release, anyone have tried these approaches? Thanks in advance!
T
thdj432
04-12-2021, 01:01 AM #1

Is there a solution for Windows 10 that supports NIC teaming? Also, does Windows 11 currently permit NIC teaming? I'm interested in setting up multi-gigabit local networks and have looked through old threads, but they seem outdated. With the latest Windows 10 updates and the new Windows 11 release, anyone have tried these approaches? Thanks in advance!

F
fiona12
Member
139
04-30-2021, 02:33 PM
#2
Many Intel Ethernet devices enable teaming, but only when using an Intel NIC on both ends. Ensure you have proper switching hardware in place—such as dual switches or a 10G switch with teaming capability. Broadcom adapters can also support this feature. Avoid relying on generic Realtek solutions.
F
fiona12
04-30-2021, 02:33 PM #2

Many Intel Ethernet devices enable teaming, but only when using an Intel NIC on both ends. Ensure you have proper switching hardware in place—such as dual switches or a 10G switch with teaming capability. Broadcom adapters can also support this feature. Avoid relying on generic Realtek solutions.

W
Womble42
Junior Member
2
05-14-2021, 03:13 AM
#3
I've got every piece of gear ready, but the problem lies in Microsoft disabling it on Windows 10 some time back. Unless you're using a Windows Server edition, you won't be able to turn it on.
W
Womble42
05-14-2021, 03:13 AM #3

I've got every piece of gear ready, but the problem lies in Microsoft disabling it on Windows 10 some time back. Unless you're using a Windows Server edition, you won't be able to turn it on.

K
kingboo812
Junior Member
3
05-18-2021, 11:53 AM
#4
You need to depend on the network driver instead of Microsoft for this task. PS C:\Windows\system32> new-NetLBFOTeam 10G-Team "10G-1","10G-2" new-NetLBFOTeam The LBFO function isn't active right now, or it's not supported for this model. At line:1 char:1 + new-NetLbfoTeam you can opt for Intel Proset if your system meets the requirements. Otherwise, you might need to transfer the files from the server to Windows 10 Home/Pro, with guides available online if you prefer that approach.
K
kingboo812
05-18-2021, 11:53 AM #4

You need to depend on the network driver instead of Microsoft for this task. PS C:\Windows\system32> new-NetLBFOTeam 10G-Team "10G-1","10G-2" new-NetLBFOTeam The LBFO function isn't active right now, or it's not supported for this model. At line:1 char:1 + new-NetLbfoTeam you can opt for Intel Proset if your system meets the requirements. Otherwise, you might need to transfer the files from the server to Windows 10 Home/Pro, with guides available online if you prefer that approach.

N
NooLele
Posting Freak
847
05-20-2021, 01:12 AM
#5
Windows 11 doesn't support NIC teaming anymore. Microsoft removed the feature from Windows Server, leaving Intel as the only option. You can still use Intel PROSet or a managed switch to achieve similar results. Some alternatives are available on GitHub like DisProxy and Connectify Dispatch Pro.
N
NooLele
05-20-2021, 01:12 AM #5

Windows 11 doesn't support NIC teaming anymore. Microsoft removed the feature from Windows Server, leaving Intel as the only option. You can still use Intel PROSet or a managed switch to achieve similar results. Some alternatives are available on GitHub like DisProxy and Connectify Dispatch Pro.

G
GanOnPlay
Junior Member
20
05-21-2021, 02:43 AM
#6
It's frustrating about Intel's decision to remove NIC Teaming support. I'm planning to remove the Intel ProSet software as a workaround.
G
GanOnPlay
05-21-2021, 02:43 AM #6

It's frustrating about Intel's decision to remove NIC Teaming support. I'm planning to remove the Intel ProSet software as a workaround.

I
iNaomiPlays
Senior Member
609
05-21-2021, 03:55 AM
#7
Are there any new developments yet? I understand Intel and Microsoft won't back down, which keeps me from upgrading to Windows 11 right now. I’m open to purchasing certain third-party NICs that still support drivers handling bonding like PROSet does in Windows 10. It would be unrealistic if there’s no way at all, particularly on the Pro version.
I
iNaomiPlays
05-21-2021, 03:55 AM #7

Are there any new developments yet? I understand Intel and Microsoft won't back down, which keeps me from upgrading to Windows 11 right now. I’m open to purchasing certain third-party NICs that still support drivers handling bonding like PROSet does in Windows 10. It would be unrealistic if there’s no way at all, particularly on the Pro version.

F
finnigan01
Junior Member
23
05-21-2021, 11:40 AM
#8
Dear @ll, encountered the same problem on Windows 11. Just purchased a new machine and tried to set up a Dual Intel Network Card as I did on my Server 2022 (Hyper-V) and Unifi Switch with 2 Gbit/s in place. Right now I’m not ready to spend that much money on a 10G network or an SSD File Server. I followed this guide: https://codeinsecurity.wordpress.com/202...emoved-it/ and the GitHub repo: https://github.com/gsuberland/lbfo_win10. It also worked on Windows 11 with Server 2022. The key was to match article 1:1 and install the driver in Windows Recovery Mode, since it detects an invalid driver signature in the *.inf file. Note that the *.sys file’s signature depends on the *.cat file from your Windows Server Image. Make sure the automated Kernel Service startup is set up correctly: Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MsLbfoProvider\Start=2. I hope this helps, Daniel.
F
finnigan01
05-21-2021, 11:40 AM #8

Dear @ll, encountered the same problem on Windows 11. Just purchased a new machine and tried to set up a Dual Intel Network Card as I did on my Server 2022 (Hyper-V) and Unifi Switch with 2 Gbit/s in place. Right now I’m not ready to spend that much money on a 10G network or an SSD File Server. I followed this guide: https://codeinsecurity.wordpress.com/202...emoved-it/ and the GitHub repo: https://github.com/gsuberland/lbfo_win10. It also worked on Windows 11 with Server 2022. The key was to match article 1:1 and install the driver in Windows Recovery Mode, since it detects an invalid driver signature in the *.inf file. Note that the *.sys file’s signature depends on the *.cat file from your Windows Server Image. Make sure the automated Kernel Service startup is set up correctly: Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MsLbfoProvider\Start=2. I hope this helps, Daniel.

H
hunthorsegirl
Member
182
05-21-2021, 12:28 PM
#9
You can continue using the provided commands in both Windows 10 and Windows 11. The script allows creating a new network switch team with specified members or directly issuing the command to prompt for team name, then entering NIC names from the Control Panel interface. I usually label each NIC with short identifiers like NIC1, NIC2, etc. This should assist you! Edited March 8, 2023 by dflorey For more details: https://learn.microsoft.com/en-us/powers...ver2022-ps
H
hunthorsegirl
05-21-2021, 12:28 PM #9

You can continue using the provided commands in both Windows 10 and Windows 11. The script allows creating a new network switch team with specified members or directly issuing the command to prompt for team name, then entering NIC names from the Control Panel interface. I usually label each NIC with short identifiers like NIC1, NIC2, etc. This should assist you! Edited March 8, 2023 by dflorey For more details: https://learn.microsoft.com/en-us/powers...ver2022-ps