Ping an IP address and log results

[mrforgetful]

Hi,

 

I'm wanting to ping an IP address for long period of time and log the results in a test file.

 

I've got some programs but nothing quite like I want.

 

I obviously need the response time and if packets were received 100% or not but I also want the time and date of the ping too.

 

I'm surprised there isn't a parameter for the windows ping command for these but anyway, any ideas?

[beast_gts]

A single IP address?

 

You could script it easily or there are numerious *Nix apps. Or you could try this: http://www.tools4ever.com/products/free/freeping/

[mrforgetful]

I'm on Windows so no *nix I'm afraid (

 

A single IP will work, two maybe.

 

Basically out ISA server connection to the LEA's upstream server gets really slow and timesout numerous times a day. They say it's the ISA not them so I'm setting up a laptop connected straight to connection doing a continuous ping that I can then show them so they know it's not my ISA.

 

At the minute ISA will redirect to a backup upstream if the primary dies, I'd like to ping that too but it's not as important if I cant.

 

Will check out that link, thanks.

[CyberNerd]

ping address -t > file.txt

 

?

[mrforgetful]

lol it's that simple! Knew it could do it, bless it.

 

The only thing missing is a timestamp of each request, know of any way to get one?

 

And thanks for that.

[indie]

Could you not use the time stamp on the actual file? Or are you continually adding to the file?

 

If so, you could use the "time /t" command to output the time to the DOS prompt?

[mrforgetful]

It will be running constantly for around a week, or at least a file each day.

 

The command suggested previously gets me a log looking like

 

Pinging 192.168.1.1 with 32 bytes of data:

 

Reply from 192.168.1.1: bytes=32 time<1ms TTL=128

Reply from 192.168.1.1: bytes=32 time<1ms TTL=128

.

.

.forever

 

Ping statistics for 192.168.1.1:

 

Packets: Sent = 11, Received = 11, Lost = 0 (0% loss),

 

Approximate round trip times in milli-seconds:

 

Minimum = 0ms, Maximum = 0ms, Average = 0ms

 

Which is fine for a short time, but I could do with it saying at what times each request is so I know when it's not responding and for how long.

 

The program I've found that am using at the moment logs like such:

 

7/7/2006 9:32:39 ----- Started service -----

7/7/2006 9:32:39 10.21.0.191 Ok [10ms %100]

7/7/2006 9:32:39 10.21.0.200 Ok [10ms %100]

7/7/2006 9:33:39 10.21.0.200 Ok [0ms %100]

7/7/2006 9:33:39 10.21.0.191 Ok [0ms %100]

7/7/2006 9:34:39 10.21.0.191 Ok [0ms %100]

7/7/2006 9:34:39 10.21.0.200 Ok [0ms %100]

7/7/2006 9:35:39 10.21.0.191 Ok [0ms %100]

7/7/2006 9:35:39 10.21.0.200 Ok [0ms %100]

Thinking about it, I'm not sure now what's not good enough about that.

[steve]

Try Servers Alive http://www.woodstone.nu/salive/

 

Its free for up to 10 devices - does time logged ping and much much more.

[MkII]

whateveryourname was: do you need to do this internaly? I'm using l8nc.com to monitor my home router - it only displays todays and yesterdays results but may be what your after

 

Here's my graph: http://www.l8nc.com/graph.php?jid=729c217f3f2949dad87b049c73d780ec

[Guest]

You could try Angry IP Scanner

 

http://ipscan.sourceforge.net/ipscan.exe

 

It can be run from the command line to append info to a txt file like this

 

Scanned 192.168.1.1 - 192.168.1.1

07/07/2006 11:03:08

 

192.168.1.1 9 ms SERVER 122

 

Scanned 192.168.1.1 - 192.168.1.1

07/07/2006 11:04:22

 

192.168.1.1 8 ms SERVER 122

 

Scanned 192.168.1.1 - 192.168.1.1

07/07/2006 11:04:30

 

192.168.1.1 7 ms SERVER 122

 

So you is you created 2 batch files say run1 and run2. Put the command line to run the ping and then have each batch file call the other batch file after the ping it would run forever collecting the data you need.

 

Oooo my head hurts now lol

[OutToLunch]

Might be misunderstanding what your intentions are, but are you intending to continually ping your ISA server or the upstream caches? If anyone's in charge of monitoring the caches, they may be a little irked if you ping -t them for a week!

 

If you're working internally and you just want a nice timestamped list of the pings, have a look at RoboTest. Multiple targets supported and logging too.

 

http://www.hahntech.com/robotest.htm

 

Example output on 5 second intervals...

 

1 12:02:42 Jul 07, 2006 Success: 0.00 secs 192.168.0.1

1 12:02:42 Jul 07, 2006 Success: 0.00 secs 192.168.16.2

1 12:02:42 Jul 07, 2006 Success: 0.00 secs 192.168.0.2

 

2 12:02:47 Jul 07, 2006 Success: 0.00 secs 192.168.0.1

2 12:02:47 Jul 07, 2006 Success: 0.00 secs 192.168.16.2

2 12:02:47 Jul 07, 2006 Success: 0.00 secs 192.168.0.2

 

3 12:02:52 Jul 07, 2006 Success: 0.00 secs 192.168.0.1

3 12:02:52 Jul 07, 2006 Success: 0.00 secs 192.168.16.2

3 12:02:52 Jul 07, 2006 Success: 0.00 secs 192.168.0.2

[mrforgetful]

That'll do just fine OutToLunch.

I'd actually tried that along with a dozen others but somehow forgot about it, tut.

 

I'm sure they'll get rather pissed at me pinging them constantly, but it's their idea!

 

Thanks people.

[m25man]

Look@Lan Freeware does a good job - more than your average ping tool.

 

http://www.lookatlan.com

 

I have seen this in use at a couple of schools recently.

[Ric_]

I use the monitoring feature in ISA 2004 to do this. Every X minutes a ping is sent upstream to the proxy and the round trip time recorded. I also do this for DNS requests upstream. This allows me to monitor connection to CLEO.