Question Locked

Extended ping in windows

0 helpful
7 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
what is the cmd in windows for extended ping??

7 replies

by bizintelligence

if there is inbuilt substitute for extended ping in Windows. But you can download extended ping utility and install it.

Cheers !

by balge

hi
I thought extended ping was Cisco , Windows only has Ping?
cheers

by rob miners

Running this Batch File will increment the last digit by one.

Example: (1,1,10) the first 1 is the Starting number the second 1 is the Increment and the 10 is the ending number.

So if you had an IP Address and you wanted to check all of the IP Addresses in that range you would change the 10 to 254.

@echo off
C:
set IP=c:\IP_1_10.txt

For /L %%i in (1,1,10) do ping 192.168.1.%%i >nul >> %IP%

OutPut is in this form

Pinging 192.168.1.1 with 32 bytes of data:
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64

Ping statistics for 192.168.1.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 1ms, Average = 1ms

Pinging 192.168.1.2 with 32 bytes of data:
Reply from 192.168.1.2: bytes=32 time<1ms TTL=128
Reply from 192.168.1.2: bytes=32 time<1ms TTL=128
Reply from 192.168.1.2: bytes=32 time<1ms TTL=128
Reply from 192.168.1.2: bytes=32 time<1ms TTL=128

Ping statistics for 192.168.1.2:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

Pinging 192.168.1.3 with 32 bytes of data:
Reply from 192.168.1.5: Destination host unreachable.
Reply from 192.168.1.5: Destination host unreachable.
Reply from 192.168.1.5: Destination host unreachable.
Reply from 192.168.1.5: Destination host unreachable.

Ping statistics for 192.168.1.3:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Pinging 192.168.1.4 with 32 bytes of data:
Reply from 192.168.1.4: bytes=32 time<1ms TTL=128
Reply from 192.168.1.4: bytes=32 time<1ms TTL=128
Reply from 192.168.1.4: bytes=32 time<1ms TTL=128
Reply from 192.168.1.4: bytes=32 time<1ms TTL=128

Ping statistics for 192.168.1.4:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

Pinging 192.168.1.5 with 32 bytes of data:
Reply from 192.168.1.5: bytes=32 time<1ms TTL=128
Reply from 192.168.1.5: bytes=32 time<1ms TTL=128
Reply from 192.168.1.5: bytes=32 time<1ms TTL=128
Reply from 192.168.1.5: bytes=32 time<1ms TTL=128

Ping statistics for 192.168.1.5:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

by rob miners

ping -t < ip address >

The command will send 1 ping per second until the process is halted by pressing CTRL-C.

I knew that I had seen something somewhere about it.

by jdclyde

anytime I suspect a connectivity issue that is sporadic. Let the ping go for an hour or so and then look at the percent dropped.

Will also let it go all night and do the same.

by rob miners

I posted to a question awhile back and added the -t -w to the command. I knew that I had some information on it somewhere but I added it to a different file and couldn't remember the command and I also couldn't find it until today. Who wants to get old? :D
I haven't worked on a live network for awhile so I'm getting rusty.

This discussion is closed to new replies.