Windows PowerShell Home
Possible Get-NetTcpConnection Scriptlet Output Bug
4/1/2014 12:22:39 PM
User(s) can reproduce this bug
I suspect there is a bug in the Get-NetTcpConnection scriptlet on Windows Server 2012 R2. Running New-NetTransportFilter to create a new transport filter with SettingName DatacenterCustom, I can confirm the appropriate transport filter is created via Get-NetTransportFilter (i.e., the filter appears in the resultant output with the correct SettingName of DatacenterCustom). However, upon establishing a TCP connection covered by the filter and running Get-NetTcpConnection, the output suggests the connection is covered by InternetCustom by way of the AppliedSetting column. But, looking at the traffic details via a network sniffer, the behavior of the underlying connection seems to following DatacenterCustom.
The reverse seems true too. That is, when a transport filter is created using SettingName InternetCustom, Get-NetTcpConnection reports the connection is instead covered by DatacenterCustom, but the actual behavior of the TCP connection matches that of InternetCustom.
Hence, I believe the AppliedSetting column of Get-NetTcpConnection output is incorrect, at least when it comes to InternetCustom and DatacenterCustom (it has them backwards). Other output may be wrong too, I haven't looked beyond those two SettingNames.
How often does this happen?
Have you seen this problem before in this product?
I do not know if this issue existed previously
1. Create a new transport filter with SettingName DatacenterCustom via New-NetTransportFilter.
2. Confirm transport filter was correctly created via Get-NetTransportFilter.
3. Establish new TCP connection covered by the new filter.
4. Run Get-NetTcpConnection, find the TCP connection in question and confirm AppliedSetting column shows (incorrectly) InternetCustom.
Instead, Step 4 in my reproduction steps above is expected to show DatacenterCustom, to match what was created via New-NetTransportFilter and confirmed via Get-NetTransportFilter.
to post a comment.
Please enter a comment.
to post a workaround.
Please enter a workaround.
© 2014 Microsoft