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.
Charles -----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Chris Mason Sent: Sunday, July 16, 2006 12:47 AM To: [email protected] Subject: Re: TCPIP - Ping tool By some sort of mistake navigating Outlook Express last night, this response was sent privately although it was supposed to be destined for the list. Let's try again. Mike, I've glad you've explained what "IPS" means. Precision helps to get faster answers. Strangely enough the answer was under your nose all along, namely PING. If your "internal network" corresponds to a Local Area Network (LAN), let us assume Ethernet - although I guess there's still an outside chance it is Token Ring or even Fiber Distributed Data Interface (FDDI) - then, theoretically, you need merely to enter the PING command with the subnet value followed by "all ones" for the host portion. Taking your example, I assume the subnet address for your LAN is 192.168.10.0 and the subnet mask is 255.255.255.0, then the command PING 192.168.10.255 should ensure that the IP node behind each of the 254 possible interfaces on the LAN will return a response. That is because the subnet portion of all the IP addresses on the LAN is the first 24 bits and the host portion is the last 8 bits as defined by the subnet mask 255.255.255.0. It's not guaranteed that your subnet mask is 255.255.255.0 but the way you wrote your post, "ping 192.160.10.nn", indicates that it might be. Of course, you'll get responses only from the IP nodes that happen to be powered on at the time you enter the command. I said theoretically above since it is possible that not all the nodes attached to the LAN have been properly configured with the correct subnet mask and thus may not respond to the PING. It so happens that I was involved in some tests long ago when the LAN where I worked needed to move the subnet ---------------------------------------------------------------------- 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
