Home Dashboard Directory Help
Search

Possible Get-NetTcpConnection Scriptlet Output Bug by mhetherington


Status: 

Active


1
0
Sign in
to vote
Type: Bug
ID: 844825
Opened: 4/1/2014 12:22:39 PM
Access Restriction: Public
0
Workaround(s)
view
0
User(s) can reproduce this bug

Description

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.
Details
Sign in to post a comment.
Sign in to post a workaround.