Comments on: Quickly Ping A Range of IP to Find Dead IP on Windows

By: Crapflinger

Crapflinger — Thu, 06 Oct 2022 12:18:11 +0000

if (!$status)
{
$computer + ” – available”
}
else
{
$computer + ” – not available”
}

will give you “both” available and not available, i know it’s simple to infer not available from the list of available but if you’re exporting for a report it would be cleaner for the list to not have gaps. like if you’re trying to find a contiguous block it’ll be easier to pick one out of the list if everything is in there.

By: Matt

Matt — Mon, 20 Jun 2022 13:23:12 +0000

Simple solution, I like it. Very easy to expand the one liner to multiple subnets as well! Thanks heaps for the post!

Also, I did a test with Test-Connection and using the Ping class directly on the same network and subnet and the ping class directly seem to be quite a lot quicker.
Test-Connection TotalMinutes: 17.550881065
Ping Class TotalMinutes: 3.81168999

A version of the final one liner I ended up using:
0..254 | foreach { $i = $_; 1..254 | foreach{ $isOnline = (New-Object System.Net.NetworkInformation.Ping).Send(“192.168.$i.$_”, 1000); “192.168.$i.$_`: $($isOnline.Status)” }}

Thanks for the post!

By: Shawn

Shawn — Thu, 26 Aug 2021 16:12:49 +0000

In reply to Kent Chen. Thank you Kent. I appreciate your help.

By: Kent Chen

Kent Chen — Wed, 25 Aug 2021 22:45:26 +0000

In reply to Shawn.

taking out the ! in the if line.
if ($status) {
$computer + ‘- taken’
}

By: Shawn

Shawn — Wed, 25 Aug 2021 22:41:27 +0000

What parameters would you change to make the top script show active connections as opposed to dead IPs?