On Sun, 16 Jul 2006 19:05:50 -0700, Charles Mills <[EMAIL PROTECTED]> wrote:
>If ping 192.168.10.255 does not work then it should not be too difficult to >write a Rexx script that generates 255 or some other appropriate number of >ping commands. Same limitations on "won't see devices that aren't turned on >or are disconnected" and will take a while due to timeouts. > And same caveat regarding intrusion detection. In addition, 192.168.10.0/24 is just one subnet in the large range of private IP addrs 192.168.0.0-192.168.255.255. Pinging 192.168.10.255 will find devices on the local LAN segment only. There are probably other subnets. There are undoubtably public IP addrs, too. If they are all be mapped to private addresses you don't need to know about them, but they may be directly reachable. And Pings may be blocked on routers so you may not be able to find anything beyond you local segment. The bottom line is that there is no technique guaranteed to give you the information you need, and there is a reasonable chance that your trying to find out by these technique will run you afoul of your security department. Your best bet is to locate people that might know something about your configuration and start asking lots of questions. Pat O'Keefe ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
