Bug in powershell cmdlet Test-NetConnection

Question

Bug in powershell cmdlet Test-NetConnection

Anonymous

I'm not sure if this is the right place to report bugs.

I'm using Test-NetConnection to test if a portis open on a remote server.

Test-NetConnection <server> -port <port#>

I get a response like this:

ComputerName : <server>

RemoteAddress : <server>

RemotePort : <port#>

InterfaceAlias : Ethernet

SourceAddress : 192.168.1.52

PingSucceeded : False

PingReplyDetails (RTT) : 0 ms

TcpTestSucceeded : False

On the testing server I have defined multiple ipv4 addresses - but only one have Skip as Source set to false (192.168.1.140)

Unfortunately the SourceAddress in the output uses the old way of selecting SourceAddresses - ie. the address closest to the gateway.

The environment is 2012R2 std with poweshell

Major Minor Build Revision

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

4 0 -1 -1

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

3 answers

Answer 1

Anonymous

You are welcome.

They should be able to help you there.

Cheers.

0 comments

Answer 2

Anonymous

Hi Bill

Thanks.

Question asked in TechNet Server Forum

Cheers

Leif Sommerdal

0 comments

Answer 3

Hi,

Your question is beyond the scope of these Forums

This Community is mainly for home users and their computer problems, not business systems.

Kindly post your question in the TechNet Server Forums.

http://social.technet.microsoft.com/Forums/windowsserver/en-US/home?category=windowsserver

TechNet Forums:

https://social.technet.microsoft.com/Forums/en-US/home

MSDN Forums:

https://social.msdn.microsoft.com/Forums/en-US/home

Cheers.

Share via

Bug in powershell cmdlet Test-NetConnection

3 answers