# How can I ping a range of IP addresses simultaneously

I have a bunch of machines on an IP address range which I want to ping simultaneously as a quick and dirty way of telling which ones are switched on. What (free) software can I use to do this?

I'm using Windows Vista.

-
I tried angry ip scanner and free ip scanner and angry seems faster after increasing it's maximum thread count to the range of IPs I was after. –  Jon Cage Sep 24 '09 at 7:59
there's a slight chance this might trip off some kind of security. It might be a better bet to have the machines set to ping a central server at certain intervals, or check at the router. –  Journeyman Geek May 20 '11 at 0:43

The quickest way is to use Angry IP Scanner

I use it for the same way you want to!

-
It is free? I have been using it for years. –  William Hilsum Sep 23 '09 at 16:01
Er.. yes it is? –  Jon Cage Sep 23 '09 at 16:03
That's so good! :D +1 –  BloodPhilia Jun 23 '10 at 19:54
This sets off some Antivirus signatures for "Potentially Unwanted Program". I suggest using NirSoft's PingInfoView instead. –  Iszi Sep 5 '12 at 17:31
@iszi False positive... I still think this is the best program for the job. –  William Hilsum Sep 5 '12 at 23:26

Angry IP Scanner is great, but I prefer CLI tools. See if you can get this powershell script running in Vista. https://github.com/webstersprodigy/PowerSploit/blob/Portscan/Recon/Invoke-Portscan.ps1

I also suggest getting access to a Linux CLI by using a linux live cd/usb, dual boot, or a vm in VirtualBox. (Install VirtualBox, add a new vm, install Debian.) A linux CLI is invaluable.

From a linux CLI, run the following:

for ip in 172.10.1.{1..254}; do ping -c 1 -w 1 $ip > /dev/null && echo$ip "$(nslookup$ip | grep 'name = ' | awk -F ' = ' '{print $2}')"; done Adjust for your network range (the '172.10.1' part,) and you're off. This will provide a list of all hosts on the network that respond to ICMP echo (ping) requests, and resolve them against your DNS server. Note: This is not the most reliable way to test for live hosts as they may have ICMP blocked. # nmap Based Scan nmap -sP 192.168.1.0/24 Note: Nmap is more reliable as it is a port scanner and bases its results on the activity on more than just ICMP responses. It's heavily used by pentesters and is worth learning. - You could just write a Bash script that loops through an IP address range and pings them. An example that pings addresses in the range 10.1.1.1 to 10.1.1.255 (inclusive): for i in {100..255} do ping 10.1.1.$i
done
-
I think that "500" wants to be 255 or less? –  David Mackintosh Sep 24 '09 at 2:41
And I think ping 10.1.1.i probably wants to be ping 10.1.1.\$i. –  Adam Luchjenbroers Jan 4 '10 at 6:14
also not simultaneous –  hpavc Aug 2 '13 at 14:03

Save the below script on the server with an extension of .bat or .cmd and call the file from the command prompt. It should prompt you to enter the IP address range.

@echo off

SET count=0

:start
SET /a count=%count%+1

cls
ECHO. & ECHO Trying %subnet%.%count% & ECHO.

ping -n 1 -w 1000 %subnet%.%count% >nul
IF %errorlevel%==0 echo %subnet%.%count% UP >> c:\pingnet.log
IF %errorlevel%==1 echo %subnet%.%count% DOWN >> c:\pingnet.log

IF %count%==254 goto :eof

GOTO start

Once the command has run, it will create a text file name pingnet.log in the root of C drive. That file should give you a list of used and down (free) IP addresses.

For example:

10.2.214.1 UP
10.2.214.2 UP
10.2.214.3 UP
10.2.214.4 DOWN

It is pretty simple to run, and it should save you loads of time.

-
This is actually pretty slow compared to angry IP scanner as it does them one at a time. Unless most of the IP range is used, you'd have to wait minutes for this approach to give you an answer. –  Jon Cage Dec 14 '11 at 7:25

Nmap is available for Windows:

# nmap -sP 10.0.10.1-100
-
nmap is absolutely a great piece of software –  Ram Sep 24 '09 at 4:06

## Free IP Scanner 1.6

Here is the range of IP addresses as you can notice in:

-

Open a Command Prompt and type:

FOR /L %i IN (1,1,254) DO ping -n 1 192.168.0.%i | FIND /i "Reply">>C:\ipaddresses.txt

-n 1 means that only 1 ping packet will be sent to each computer.

Change 192.168.0 to match you own network ID.

This will ping all IP addresses on the 192.168.0.0 network segment and create a text file called ipaddresses.txt in C:\, where it will list only the IP addresses that gave a reply.

You can also add -a to the ping command to resolve all the responding IP addresses to hostnames, but doing so will cause the script to take a considerable time to finish:

FOR /L %i IN (1,1,254) DO ping -a -n 1 192.168.0.%i | FIND /i "Reply">>C:\ipaddresses.txt
-
This still pings them one at a time though doesn't it? Angry IP scanner pings all IP's in the subnet at once by launching multiple threads so it takes very little time to complete a whole scan. –  Jon Cage Apr 12 '10 at 8:38

try fping

-
It's available on brew for OSX too (incase anyone surfed from Google and missed Windows in the title.) –  Ross Aug 4 '14 at 18:44

I've used this command

for %%i in 200 to 254 do ping 10.1.1.%%i

in a batch file for a similar reason

-
are you sure it does a simultaneous ping? or is it one machine after another! –  Vineet Menon Nov 29 '11 at 10:52
agreed, not simultaneous –  hpavc Aug 2 '13 at 14:02
You're right it's sequential rather than simultaneous –  Col Aug 23 '13 at 8:33

## protected by Community♦May 3 at 20:55

Thank you for your interest in this question. Because it has attracted low-quality answers, posting an answer now requires 10 reputation on this site.