2007
A HACKING ODYSSEY PART 2:
NETWORK SCANNING & NMAP CONTINUED...
Ping Sweep
To go hand in hand with traceroute you can also PING a target or a
targets subnet to see what hosts are active on it.
There are hundreds of tools available but I suppose the most common is
Nmap.
Use the –sP option to Ping Sweep a subnet. For example if we ping sweep
the IP addresses adjacent to Google (we found Google’s IP from our
trace route) we will be able to see what is alive:
Code:
C:\Documents and Settings\Nokia>nmap -sP 72.14.207.0-255
Starting Nmap 4.03 ( http://www.insecure.org/nmap ) at 2007-02-13 20:38
GMT
Standard Time
Host 72.14.207.4 appears to be up.
Host 72.14.207.5 appears to be up.
Host 72.14.207.6 appears to be up.
Host 72.14.207.8 appears to be up.
Host eh-in-f9.google.com (72.14.207.9) appears to be up.
Host eh-in-f19.google.com (72.14.207.19) appears to be up.
Host eh-in-f32.google.com (72.14.207.32) appears to be up.
Host eh-in-f33.google.com (72.14.207.33) appears to be up.
Host eh-in-f34.google.com (72.14.207.34) appears to be up.
Host eh-in-f35.google.com (72.14.207.35) appears to be up.
Host eh-in-f36.google.com (72.14.207.36) appears to be up.
Host eh-in-f37.google.com (72.14.207.37) appears to be up.
Host eh-in-f38.google.com (72.14.207.38) appears to be up.
Host eh-in-f39.google.com (72.14.207.39) appears to be up.
Host eh-in-f40.google.com (72.14.207.40) appears to be up.
Host eh-in-f41.google.com (72.14.207.41) appears to be up.
Host eh-in-f42.google.com (72.14.207.42) appears to be up.
Host eh-in-f43.google.com (72.14.207.43) appears to be up.
Host eh-in-f44.google.com (72.14.207.44) appears to be up.
Host eh-in-f45.google.com (72.14.207.45) appears to be up.
Host eh-in-f46.google.com (72.14.207.46) appears to be up.
Host eh-in-f47.google.com (72.14.207.47) appears to be up.
Host eh-in-f48.google.com (72.14.207.48) appears to be up.
Host eh-in-f49.google.com (72.14.207.49) appears to be up.
Host eh-in-f50.google.com (72.14.207.50) appears to be up.
Host eh-in-f51.google.com (72.14.207.51) appears to be up.
Host eh-in-f52.google.com (72.14.207.52) appears to be up.
Host eh-in-f53.google.com (72.14.207.53) appears to be up.
Host eh-in-f54.google.com (72.14.207.54) appears to be up.
Host eh-in-f56.google.com (72.14.207.56) appears to be up.
Host eh-in-f57.google.com (72.14.207.57) appears to be up.
Host eh-in-f58.google.com (72.14.207.58) appears to be up.
Host eh-in-f59.google.com (72.14.207.59) appears to be up.
Host eh-in-f60.google.com (72.14.207.60) appears to be up.
Host eh-in-f61.google.com (72.14.207.61) appears to be up.
Host eh-in-f62.google.com (72.14.207.62) appears to be up.
Host eh-in-f63.google.com (72.14.207.63) appears to be up.
Host eh-in-f64.google.com (72.14.207.64) appears to be up.
Host eh-in-f65.google.com (72.14.207.65) appears to be up.
Host eh-in-f66.google.com (72.14.207.66) appears to be up.
Host eh-in-f67.google.com (72.14.207.67) appears to be up.
Host eh-in-f68.google.com (72.14.207.68) appears to be up.
Host eh-in-f69.google.com (72.14.207.69) appears to be up.
Host eh-in-f70.google.com (72.14.207.70) appears to be up.
Host eh-in-f71.google.com (72.14.207.71) appears to be up.
Host eh-in-f72.google.com (72.14.207.72) appears to be up.
Host eh-in-f73.google.com (72.14.207.73) appears to be up.
Host eh-in-f74.google.com (72.14.207.74) appears to be up.
Host eh-in-f75.google.com (72.14.207.75) appears to be up.
Host eh-in-f76.google.com (72.14.207.76) appears to be up.
Host eh-in-f77.google.com (72.14.207.77) appears to be up.
Host eh-in-f78.google.com (72.14.207.78) appears to be up.
Host eh-in-f79.google.com (72.14.207.79) appears to be up.
Host eh-in-f80.google.com (72.14.207.80) appears to be up.
Host eh-in-f81.google.com (72.14.207.81) appears to be up.
Host eh-in-f83.google.com (72.14.207.83) appears to be up.
Host eh-in-f84.google.com (72.14.207.84) appears to be up.
Host eh-in-f88.google.com (72.14.207.88) appears to be up.
Host eh-in-f91.google.com (72.14.207.91) appears to be up.
Host eh-in-f93.google.com (72.14.207.93) appears to be up.
Host eh-in-f95.google.com (72.14.207.95) appears to be up.
Host eh-in-f96.google.com (72.14.207.96) appears to be up.
Host eh-in-f97.google.com (72.14.207.97) appears to be up.
Host eh-in-f99.google.com (72.14.207.99) appears to be up.
Host eh-in-f100.google.com (72.14.207.100) appears to be up.
Host eh-in-f101.google.com (72.14.207.101) appears to be up.
Host eh-in-f104.google.com (72.14.207.104) appears to be up.
Host eh-in-f107.google.com (72.14.207.107) appears to be up.
Host eh-in-f112.google.com (72.14.207.112) appears to be up.
Host eh-in-f115.google.com (72.14.207.115) appears to be up.
Host eh-in-f117.google.com (72.14.207.117) appears to be up.
Host eh-in-f121.google.com (72.14.207.121) appears to be up.
Host eh-in-f123.google.com (72.14.207.123) appears to be up.
Host eh-in-f129.google.com (72.14.207.129) appears to be up.
Host eh-in-f133.google.com (72.14.207.133) appears to be up.
Host eh-in-f161.google.com (72.14.207.161) appears to be up.
Host 72.14.207.162 appears to be up.
Host 72.14.207.164 appears to be up.
Host 72.14.207.165 appears to be up.
Host eh-in-f176.google.com (72.14.207.176) appears to be up.
Host eh-in-f177.google.com (72.14.207.177) appears to be up.
Host eh-in-f178.google.com (72.14.207.178) appears to be up.
Host eh-in-f179.google.com (72.14.207.179) appears to be up.
Host eh-in-f180.google.com (72.14.207.180) appears to be up.
Host eh-in-f181.google.com (72.14.207.181) appears to be up.
Host eh-in-f182.google.com (72.14.207.182) appears to be up.
Host eh-in-f183.google.com (72.14.207.183) appears to be up.
Host eh-in-f184.google.com (72.14.207.184) appears to be up.
Host eh-in-f187.google.com (72.14.207.187) appears to be up.
Host eh-in-f190.google.com (72.14.207.190) appears to be up.
Host eh-in-f191.google.com (72.14.207.191) appears to be up.
Host eh-in-f196.google.com (72.14.207.196) appears to be up.
Host eh-in-f212.google.com (72.14.207.212) appears to be up.
Host 72.14.207.221 appears to be up.
Host 72.14.207.222 appears to be up.
Host 72.14.207.224 appears to be up.
Host 72.14.207.225 appears to be up.
Host 72.14.207.227 appears to be up.
Host 72.14.207.228 appears to be up.
Host 72.14.207.230 appears to be up.
Host 72.14.207.231 appears to be up.
Host 72.14.207.233 appears to be up.
Host 72.14.207.234 appears to be up.
Host 72.14.207.236 appears to be up.
Host 72.14.207.237 appears to be up.
Host 72.14.207.251 appears to be up.
Host 72.14.207.252 appears to be up.
Host 72.14.207.253 appears to be up.
Host 72.14.207.254 appears to be up.
Nmap finished: 256 IP addresses (109 hosts up) scanned in 22.328 seconds
Oh my, doesn’t Google have rather a lot of servers.
The last thing to note is that just like ICMP time exceeded messages;
ICMP replies can also be blocked by routers & firewalls and the
actual host can also be configured not to reply to ICMP requests.
Original Tutorial
by nokia for TheTAZZone-TAZForum
Originally posted on March 2nd, 2007 here
Do not use, republish, in whole or in part, without the consent of
the Author. TheTAZZone policy is that Authors retain the rights to the
work they submit and/or post...we do not sell, publish, transmit, or
have the right to give permission for such...TheTAZZone merely retains
the right to use, retain, and publish submitted work within it's
Network.