Mastering Windows Server 2016 Hyper-V

(Romina) #1

SMBConnection PowerShell cmdlet, which will show the SMB connections to an SMB
share. In the following example, I see that I have only two connections to my server:


PS C:> get‐smbconnection


ServerName ShareName UserName Credential Dialect NumOpens




savdalsofs.sav... Virtuals NT VIRTUAL ... SAVILLTECH.N... 3.02 4
savdalsofs.sav... Virtuals SAVILLTECH... SAVILLTECH.N... 3.02 2


If I run the Get-SmbMultiChannelConnection cmdlet from the client, it shows me all of
the possible paths over which the server can accept connections, as shown in the
following output. Note that on the server side, networking uses a NIC team, which
means only one IP address, but it can still leverage SMB Multichannel.


PS C:> get‐smbmultichannelconnection


Server Name Selected Client IP Server IP Client Server
Client RSS Client RDMA
Interface Capable
Index




--------------  --------------

savdalsofs.... True 10.7.173.101 10.7.173.20 14 15
True False
savdalsofs.... True 10.7.173.23 10.7.173.20 15 15
True False


To confirm which path is being used between the client and the server, I can look at
the TCP connections to the remote port 445, which is used for SMB. This confirms
that I am using the two available paths with four connections for each path (which is
the default number).


PS C:> Get‐NetTCPConnection ‐RemotePort 445


LocalAddress LocalPort RemoteAddress
RemotePort State AppliedSetting






10.7.173.23 56368 10.7.173.20
445 Established Datacenter
10.7.173.23 49826 10.7.173.20
445 Established Datacenter
10.7.173.23 49825 10.7.173.20
445 Established Datacenter
10.7.173.23 49824 10.7.173.20
445 Established Datacenter
10.7.173.101 49823 10.7.173.20
445 Established Datacenter
10.7.173.101 49822 10.7.173.20
445 Established Datacenter
10.7.173.101 49821 10.7.173.20
445 Established Datacenter
10.7.173.101 49820 10.7.173.20

Free download pdf