Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Limitations .Net Core to migrate Test-Connection cmdlet

See original GitHub issue

It is only a tracking issue.

We plan to migrate Test-Connection cmdlet from WMI to .Net but underlying .Net Core have still Issue System.Net.Ping ignores PingOptions on unix. Related code. There are no plans yet to fix it in 2.0.0 timeframe.

Issue Analytics

State:
Created 6 years ago
Comments:10 (2 by maintainers)

Top GitHub Comments

1reaction

iSazonovcommented, Jun 21, 2018

@SteveL-MSFT No. It is a tracking issue - we are waiting a fix in .Net Core repo.

1reaction

iSazonovcommented, Jan 11, 2018

@artisticcheese You can load the build from #5328, test the new ported cmdlet and leave a feedback in the #5328.

Top Results From Across the Web

TestConnectionCommand Class

The implementation of the "Test-Connection" cmdlet. ... The default (from Windows) is 32 bytes. Max value is 65500 (limitation imposed by Windows API)....

Creating a Python Replacement for the Test-Connection ...

I've been working on a PowerShell script to automatically power up and shut down all devices in my home lab. Both in the...

Using Get-Job to test-connection, but quite different

In your example, in the Start-Job scriptblock you are trying to access $_ which is not available in the codeblock scope.

Use PowerShell to Test Connectivity on Remote Servers

When I ran into problems, I decided to write a really quick script to ping the most critical servers on my network to...

16 PowerShell commands for network troubleshooting

These 16 Windows PowerShell cmdlets, including Get-NetIPAddress and Test-Connection, help network administrators troubleshoot their network environments.