Test-NetConnection bug in PingSucceeded property

[QyhOfficial]

Prerequisites

• Write a descriptive title.
• Make sure you are able to repro it on the latest released version
• Search the existing issues.
• Refer to the FAQ.
• Refer to Differences between Windows PowerShell 5.1 and PowerShell.

Steps to reproduce

When running Test-NetConnection command with parameter -Port, if TcpTestSucceeded get True, then the ICMP ping will be skipped, and the PingSucceeded property will not be displayed in the console. However, the result object does contain a PingSucceeded property and it's value is always False in this case, you can explicitly check it by$testresult.PingSucceeded. This will cause confusion in some automation testing scenario.

PS C:\Users\Chin> $testresult=test-netconnection -computername 8.8.8.8 -port 53
PS C:\Users\Chin> $testresult

ComputerName     : 8.8.8.8
RemoteAddress    : 8.8.8.8
RemotePort       : 53
InterfaceAlias   : vEthernet (external switch)
SourceAddress    : 192.168.30.162
TcpTestSucceeded : True

PS C:\Users\Chin> $testresult.PingSucceeded
False
PS C:\Users\Chin> test-netconnection -computername 8.8.8.8

ComputerName           : 8.8.8.8
RemoteAddress          : 8.8.8.8
InterfaceAlias         : vEthernet (external switch)
SourceAddress          : 192.168.30.162
PingSucceeded          : True
PingReplyDetails (RTT) : 35 ms

Expected behavior

When TcpTestSucceeded=True, ICMP ping test should not be skipped, and PingSucceeded should be True most of time.

Actual behavior

PS C:\Users\Chin> $testresult.PingSucceeded
False

Environment data

Windows 11, Powershell 7.5.2

Visuals

No response

[kasini3000]

Powershell 7.5.2 ,PowerShell 7.6.0-preview.4
I can reproduce the problem: inconsistent actions when opening and closing ports.
If the port is closed, icmp will be detected continue, Is this By design?

@QyhOfficial
btw:
Welcome to the temporary, community based port detection solution I provide:
https://gitee.com/chuanjiao10/kasini3000/blob/master/tcp--ping-v6.ps1

[QyhOfficial]

Powershell 7.5.2 ,PowerShell 7.6.0-preview.4 I can reproduce the problem: inconsistent actions when opening and closing ports. If the port is closed, icmp will be detected continue, Is this expected?

That is expected, if TcpTest failed, Test-NetConntion will continue to test ICMP then the PingSucceeded value is reliable.

[realslacker]

It sounds like the ping is not performed if the TCP test succeeds. I would argue that PingSucceeded should be null unless the ping was performed.

[SteveL-MSFT]

This cmdlet is from the NetTCPIP module which is part of Windows and not part of PowerShell (so not serviced by this repo). You'll need to report your concern through the Windows Feedback Tool to get the appropriate attention.

[microsoft-github-policy-service]

This issue has been marked as external and has not had any activity for 1 day. It has been be closed for housekeeping purposes.