PowerShell: Ping IP range

15 Replies to “PowerShell: Ping IP range”

1. Jeffery Hicks (MVP) says:

   November 3, 2011 at 3:12 pm

   First, if you want a bit more detail or more control over the ping, you could use the Test-Connection cmdlet. If you want a simple up/down you could use something like this:

   1..254 | foreach { new-object psobject -prop @{Address=”172.16.10.$_”;Pin
   g=(test-connection “172.16.10.$_” -quiet -count 1)}}

   I’m only sending a single ping in this example.

   The other problem with the ping class is that if the destination is unreachable, the address you get back is yours., I don’t think that is what you intended.

   Reply
2. Jeffery Hicks (MVP) says:

   November 7, 2011 at 4:46 pm

   I took this and ran with it.
   Ping IP Range with Windows #PowerShell http://bit.ly/sCjeCR

   Reply
3. mahmood says:

   December 2, 2011 at 9:39 am

   thanks. it was very usefull

   Reply
4. mahmood says:

   December 2, 2011 at 10:15 am

   It is possible to filter unreachable hosts and shows only “success” hosts?

   Reply
5. Lars Panzerbjørn says:

   October 18, 2013 at 12:08 pm

   I know I’m a bit late to the party, but I thought I’d add that when I run the commands, only xxx.xxx.xxx.1 is pinged…
   But if I run “1..254 | % { write-host $_ }” then it gives me the number 1 to 254, each on a separate line…

   Reply
6. Lars Panzerbjørn says:

   October 18, 2013 at 12:14 pm

   Hah, I figured it out, of course it only returns my machines own address until it finds an address that actually return a ping -_-

   Reply
7. Stefan Stranger says:

   March 5, 2014 at 3:44 pm

   Hi Thomas,

   I created a ping ip range script using PowerShell workflows :-)

   Check my github: https://github.com/stefanstranger/PowerShell/commit/61e676459e7eed70e811aafd3e03b83c37668821

   /Stefan

   Reply
   • Thomas Maurer says:

     March 6, 2014 at 10:58 pm

     Nice! :)

     Reply
8. Pablo from Argentina says:

   June 11, 2015 at 9:40 pm

   Hi all , i need to query specific segments and get the segment and description from sites and services

   199.52.213.0/24
   199.52.241.128/26
   199.49.54.0/23 (Segment not created)
   199.49.63.0/26 (Segment not created)
   199.49.65.0/26 (Segment not created)
   199.49.65.64/26 (Segment not created)
   199.49.70.0/26 (Segment not created)

   and os on

   is there a powerhsle to export all IP Segments to CSV file ?

   Reply
9. Mikael Hansen says:

   January 18, 2017 at 3:22 pm

   I know it’s old but if someone stumbles upon this and has the same question as Mahmood:

   Change the second line to this:
   1..254 | % { $ping.send(“192.168.1.$_”) | where {$_.status -eq “Success”} | select address, status }

   Reply
10. Niklas says:

    September 19, 2017 at 9:12 am

    Hi. I get this output, (address column truncated).
    Any easy way to fix that?

    Address Status
    150…. Success
    Timedout
    150…. Success

    Reply
11. BM says:

    January 30, 2018 at 9:28 pm

    1..254 | foreach { new-object psobject -prop @{Address=”172.16.10.$_”;Pin
    g=(test-connection “172.16.10.$_” -quiet -count 1)} | Format-Table -autosize}

    Reply
12. IdaM says:

    March 20, 2019 at 7:55 am

    This may work, but has horrible readability. I would never use a command like this in my code. I would prefer Stefan Strangers solution.

    Reply
13. Daniel Butler says:

    November 26, 2020 at 5:25 pm

    Thank for putting this up there, nice quick method to test a load of IPs :)

    Reply
    • Thomas Maurer says:

      November 26, 2020 at 5:52 pm

      thanks :)

      Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.