For the sake of speed, I have set the outer loop to only cycle twice and the inner loop only to cycle ten times. The outer loop cycles through the third set of decimal ranges and the inner loop cycles through the fourth set of decimal ranges. In the script below you can clearly see that there are two FOR loops. The First Script: Logging the IP of Active Machines in a Range of IPv4 Addresses In both scripts I also output the start and end times of the script to help you to know the total run time of the script. Although this second script runs more slowly, it can be very useful in putting meaning to the list of returned IP addresses. The second script will run more slowly because it also tries to derive a machine name for each machine. The first script will run fastest since it simply records ping responses to a log file.
If you want to scan more quickly then you can target a specific range, or modify the scripts to just scan the final dotted decimal range. These scripts do take a bit of time to run so patience is necessary. I have written the batch scripts in this article to loop through the IP address ranges of your choice and then to save a log to a text file to record the responses of active machines on the network. So for example, if you want to scan a standard network, you would want to ping the ranges: Specifically I will show how to scan the final two dotted decimal ranges. In this example I will be showing how to scan using IP version 4 ranges. There is a lot of downloadable software out there (NMap is awesome), but the simplest and most direct way to map out machines by IP addresses is to put together a batch file script and run it from a command prompt.
Querying the domain name server can be unreliable since some machines may be hidden, so sending a direct ping is the most reliable way of checking for the existence of a machine. Sometimes you will want to find out more about your local area network and what machines are running at certain IP addresses.
0 kommentar(er)
