How do you actually CONFIGURE SMB 3.0 multichannel?

_{Monday, February 22, 2016 9:03 PM}

Hello,

I found a TON of articles about the theories, the arcane PowerShell commands you could try  and some showing the performance benefits but I couldn't find a single video or good straightforward article on configuring 2 or more nics for multichannel.      Supposedly any dumb switch will do and supposedly most nics are capable (rss capable) but OK, now what?   Install a role / feature, right click on 2 nics  - no idea what is next.   I'm sure it is easy but I still haven't actually found  a quick bullet point article on how it actually is accomplished (not the theories or potential background stuff - I just want the ikea instruction manual on building a wooden desk - not  the biology of plant cells, photosynthesis and turgor.)

_{Tuesday, February 23, 2016 8:18 PM ✅Answered}

Thanks - I should make it a little clearer - I just want the steps involved in making SMB multichannel work on 2 PCs running Windows 10 - I don't really want to get into a dissertation on lag vs lacp vs bridge vs teaming vs etherswitching vs trunking; I'm not really interested in packet headers or MTU.   No interest in large Send offload or jumbo packets.   I don't care about checkbits.      

What I'd like is a quick step by step to get SMB multichannel working- e.g.

1. Install multiport nic on each PC (assume it is rss capable)

2. Connect all ports to an unmanaged switch

3. Assign the same ip to each nic port via....

4. enjoy

Or perhaps the only way to do multichannel SMB is with multiple IPs all registered in DNS.   This is all I really want to know.

      

Point 3 would to create a team out of the multiple NICs, they would then all share the one assigned IP. The teaming would either done in the NIC driver software or software that came with the NIC, or using Windows. On Windows 10 this is a PowerShell command. As I mentioned NIC teaming does currently work on Windows 10 TH2 as far as I am aware.

_{Monday, February 22, 2016 9:35 PM}

When you link to nic's together  this is called a network BRIDGE the main purpose of this is if you wanted to share a internet connection without installing a router

but you can achieve kind of a fake multi adapter setup to help offload task say your Ethernet is fast and better then you Wi-Fi card for what ever reason's

I have tried all kinds of bridged network setup's

1 when you do this while both card will work in tandem the only real advantage is task offloading where you have more then one chip doing the load of through put

2 net stat commands are the key to turning on features that are available  such as chimney etc.

3 because of a single connection at most users Homes you wont see any whooping record breaking speed gains

4 double barrel  internet connection's  mainly are 2 cable modems and a router and switch before you get that speed boost

5 it is like having more then one processor to weed through all the headers datagrams ip addresses SMB's etc

6 so while there is an advantage you weigh the options of what you are trying to achieve like to Ethernet cards hooked to one router basically all your doing is adding and extra pipeline

7 where as bridging a WI-FI connection with a Ethernet card the only Advantage is TASK OFFLOADING where you use 2 chips instead of one to tasks  

_{Monday, February 22, 2016 9:55 PM}

When you link to nic's together  this is called a network BRIDGE the main purpose of this is if you wanted to share a internet connection without installing a router

but you can achieve kind of a fake multi adapter setup to help offload task say your Ethernet is fast and better then you Wi-Fi card for what ever reason's

I have tried all kinds of bridged network setup's

1 when you do this while both card will work in tandem the only real advantage is task offloading where you have more then one chip doing the load of through put

2 net stat commands are the key to turning on features that are available  such as chimney etc.

3 because of a single connection at most users Homes you wont see any whooping record breaking speed gains

4 double barrel  internet connection's  mainly are 2 cable modems and a router and switch before you get that speed boost

5 it is like having more then one processor to weed through all the headers datagrams ip addresses SMB's etc

6 so while there is an advantage you weigh the options of what you are trying to achieve like to Ethernet cards hooked to one router basically all your doing is adding and extra pipeline

7 where as bridging a WI-FI connection with a Ethernet card the only Advantage is TASK OFFLOADING where you use 2 chips instead of one to tasks  

Bridging (networking)"Network bridging is the action taken by network equipment to create an aggregate network from either two or more communication networks, or two or more network segments".

Link aggregation "In computer networking, the term link aggregation applies to various methods of combining (aggregating) multiple network connections in parallel in order to increase throughput beyond what a single connection could sustain"

_{Monday, February 22, 2016 10:04 PM}

SMB EnableMultiChannel is on by default in Windows 10 looking at the PowerShell command Get-SmbClientConfiguration.

Teaming of the NICs with Windows 10 currently does work;

Teaming not possible in Win10pro Insider Builds 10565 and 10576 - error 87

NIC Teaming failed (Build 10568) Windows 10

NIC teaming in Windows 10 is via a PowerShell command when it is working, an example of a command;

New-NetLBFOTeam -Name "1GBitTeam" -TeamNICName "1GBitTeam" -TeamMembers Ethernet* -TeamingMode SwitchIndependent -LoadBalancingAlgorithm IPAddresses -Confirm:$false

The provided information for the New-NetLbfoTeam command.

_{Tuesday, February 23, 2016 6:02 PM}

Thanks - I should make it a little clearer - I just want the steps involved in making SMB multichannel work on 2 PCs running Windows 10 - I don't really want to get into a dissertation on lag vs lacp vs bridge vs teaming vs etherswitching vs trunking; I'm not really interested in packet headers or MTU.   No interest in large Send offload or jumbo packets.   I don't care about checkbits.      

What I'd like is a quick step by step to get SMB multichannel working- e.g.

1. Install multiport nic on each PC (assume it is rss capable)

2. Connect all ports to an unmanaged switch

3. Assign the same ip to each nic port via....

4. enjoy

Or perhaps the only way to do multichannel SMB is with multiple IPs all registered in DNS.   This is all I really want to know.

_{Tuesday, February 23, 2016 6:16 PM}

Thanks I knew most of that but didn't understand it fully thanks for the info

I had a dell that I pull out the wireless cell phone card and added another WI-FI card to which gave me

4 nic's after bridging them all I found that only one of the wireless nic's would connect to a wireless connection at

any one time

back in the early 90's they called that a double barrel connection where you could use 2 cable modems and

2 Ethernet cards  but I also found that task offloading greatly improved  because of the 4 NIC processors

you can also apply that in the registry with out using PowerShell can't you cause to turn on

PS C:\Users\Windows____Admin___1> Get-NetOffloadGlobalSetting

ReceiveSideScaling           : Enabled
ReceiveSegmentCoalescing     : Disabled
Chimney                      : Enabled
TaskOffload                  : Enabled < is what I was referring too
NetworkDirect                : Disabled
NetworkDirectAcrossIPSubnets : Blocked
PacketCoalescingFilter       : Enabled  

that what the netstat stuff was about