Proper way to scan a range of IP addresses
Posted
by Josh G
on Stack Overflow
See other posts from Stack Overflow
or by Josh G
Published on 2009-11-17T20:33:32Z
Indexed on
2010/03/18
6:31 UTC
Read the original article
Hit count: 257
Given a range of IP addresses entered by a user (through various means), I want to identify which of these machines have software running that I can talk to.
Here's the basic process:
Ping these addresses to find available machines
Connect to a known socket on the available machines
Send a message to the successfully established sockets
Compare the response to the expected response
Steps 2-4 are straight forward for me. What is the best way to implement the first step in .NET?
I'm looking at the System.Net.NetworkInformation.Ping class. Should I ping multiple addresses simultaneously to speed up the process? If I ping one address at a time with a long timeout it could take forever. But with a small timeout, I may miss some machines that are available.
Sometimes pings appear to be failing even when I know that the address points to an active machine. Do I need to ping twice in the event of the request getting discarded?
To top it all off, when I scan large collections of addresses with the network cable unplugged, Ping throws a NullReferenceException in FreeUnmanagedResources(). !?
Any pointers on the best approach to scanning a range of IPs like this?
© Stack Overflow or respective owner