Can you post ping plotter image please to IP address 82.133.85.65

Noggo · 06-02-2008, 16:12

Note: forgot to remove `ping plotter image' and add ping results in header sorry.

Hi,

I was wondering if you could be so kind as to post your `ping' results to this IP address: 82.133.85.65 as well as your county eg Worcestershire

Regardless of whether or not you are having problems with your Virgin Media cable connection.

Goto windows command prompt:
windows key + R key together, then type CMD and then hit enter.
Copy and paste the following

ping 82.133.85.65 -n 20

into window and hit enter (remember to right click, then select paste. As ctrl + V doesn't work)

To copy the results, right click and `select all' (this should highlight all text)
hit Enter key, then copy ctrl+V your results on the thread.

Mine is as follows:

E:\Documents and Settings\Bob>ping 82.133.85.65 -n 20

Pinging 82.133.85.65 with 32 bytes of data:

Reply from 82.133.85.65: bytes=32 time=30ms TTL=51
Reply from 82.133.85.65: bytes=32 time=28ms TTL=51
Reply from 82.133.85.65: bytes=32 time=65ms TTL=51
Reply from 82.133.85.65: bytes=32 time=29ms TTL=51
Reply from 82.133.85.65: bytes=32 time=29ms TTL=51
Reply from 82.133.85.65: bytes=32 time=36ms TTL=51
Reply from 82.133.85.65: bytes=32 time=35ms TTL=51
Reply from 82.133.85.65: bytes=32 time=44ms TTL=51
Reply from 82.133.85.65: bytes=32 time=29ms TTL=51
Reply from 82.133.85.65: bytes=32 time=26ms TTL=51
Reply from 82.133.85.65: bytes=32 time=34ms TTL=51
Reply from 82.133.85.65: bytes=32 time=41ms TTL=51
Reply from 82.133.85.65: bytes=32 time=35ms TTL=51
Reply from 82.133.85.65: bytes=32 time=53ms TTL=51
Reply from 82.133.85.65: bytes=32 time=29ms TTL=51
Reply from 82.133.85.65: bytes=32 time=44ms TTL=51
Reply from 82.133.85.65: bytes=32 time=27ms TTL=51
Reply from 82.133.85.65: bytes=32 time=38ms TTL=51
Reply from 82.133.85.65: bytes=32 time=36ms TTL=51
Reply from 82.133.85.65: bytes=32 time=33ms TTL=51

Ping statistics for 82.133.85.65:
Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 26ms, Maximum = 65ms, Average = 36ms

E:\Documents and Settings\Bob>

Location: Worcestershire, cable.ubr01.brom.blueyonder.co.uk

TIA

Cerberus · 06-02-2008, 16:23

C:\Documents and Settings\Chilli>ping 82.133.85.65 -n 20

Pinging 82.133.85.65 with 32 bytes of data:

Reply from 82.133.85.65: bytes=32 time=25ms TTL=53
Reply from 82.133.85.65: bytes=32 time=21ms TTL=53
Reply from 82.133.85.65: bytes=32 time=33ms TTL=53
Reply from 82.133.85.65: bytes=32 time=22ms TTL=53
Reply from 82.133.85.65: bytes=32 time=21ms TTL=53
Reply from 82.133.85.65: bytes=32 time=26ms TTL=53
Reply from 82.133.85.65: bytes=32 time=25ms TTL=53
Reply from 82.133.85.65: bytes=32 time=25ms TTL=53
Reply from 82.133.85.65: bytes=32 time=24ms TTL=53
Reply from 82.133.85.65: bytes=32 time=27ms TTL=53
Reply from 82.133.85.65: bytes=32 time=21ms TTL=53
Reply from 82.133.85.65: bytes=32 time=20ms TTL=53
Reply from 82.133.85.65: bytes=32 time=24ms TTL=53
Reply from 82.133.85.65: bytes=32 time=23ms TTL=53
Reply from 82.133.85.65: bytes=32 time=44ms TTL=53
Reply from 82.133.85.65: bytes=32 time=22ms TTL=53
Reply from 82.133.85.65: bytes=32 time=21ms TTL=53
Reply from 82.133.85.65: bytes=32 time=22ms TTL=53
Reply from 82.133.85.65: bytes=32 time=21ms TTL=53
Reply from 82.133.85.65: bytes=32 time=28ms TTL=53

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

C:\Documents and Settings\Chilli>

Location: South Lanarkshire cpc3-ruth2.renf.cable.ntl.com

May I also ask your reasoning for this?

Noggo · 06-02-2008, 16:29

You may. I what to find out if anyone else is having the same problems with erratic latency times and I think it's about the easiest way to do it, I think.

I was going to ask people to use Ping Plotter hence title, but after a writing a short story on how to use it. I changed my mind.

Cheers,

06-02-2008, 16:37

is that your ip address? wanna get hacked mate?

Cerberus · 06-02-2008, 16:39

Quote:

Originally Posted by zinglebarb

is that your ip address? wanna get hacked mate?

Zing

-Edit-

It's a Jolt Server

Delta Whiskey · 06-02-2008, 16:39

If you do it this way, you'll redirect the output to a text file:
ping 82.133.85.65 -n 20 > c:\ping.txt

-----

Pinging 82.133.85.65 with 32 bytes of data:

Reply from 82.133.85.65: bytes=32 time=32ms TTL=52
Reply from 82.133.85.65: bytes=32 time=27ms TTL=52
Request timed out.
Reply from 82.133.85.65: bytes=32 time=22ms TTL=52
Reply from 82.133.85.65: bytes=32 time=30ms TTL=52
Reply from 82.133.85.65: bytes=32 time=26ms TTL=52
Reply from 82.133.85.65: bytes=32 time=24ms TTL=52
Reply from 82.133.85.65: bytes=32 time=29ms TTL=52
Reply from 82.133.85.65: bytes=32 time=18ms TTL=52
Reply from 82.133.85.65: bytes=32 time=25ms TTL=52
Reply from 82.133.85.65: bytes=32 time=25ms TTL=52
Reply from 82.133.85.65: bytes=32 time=25ms TTL=52
Reply from 82.133.85.65: bytes=32 time=26ms TTL=52
Reply from 82.133.85.65: bytes=32 time=34ms TTL=52
Reply from 82.133.85.65: bytes=32 time=25ms TTL=52
Reply from 82.133.85.65: bytes=32 time=27ms TTL=52
Reply from 82.133.85.65: bytes=32 time=28ms TTL=52
Reply from 82.133.85.65: bytes=32 time=33ms TTL=52
Reply from 82.133.85.65: bytes=32 time=23ms TTL=52
Reply from 82.133.85.65: bytes=32 time=22ms TTL=52

Ping statistics for 82.133.85.65:

Packets: Sent = 20, Received = 19, Lost = 1 (5% loss),

Approximate round trip times in milli-seconds:

Minimum = 18ms, Maximum = 34ms, Average = 26ms

cybernetic_tiger · 06-02-2008, 16:51

No issues to that gameserver for me:

2620-TestLab-CE#pi ip
Target IP address: 82.133.85.65
Repeat count [5]: 20
Datagram size [100]:
Timeout in seconds [2]:
Extended commands [n]: y
Source address or interface:
Type of service [0]:
Set DF bit in IP header? [no]:
Validate reply data? [no]:
Data pattern [0xABCD]:
Loose, Strict, Record, Timestamp, Verbose[none]: v
Loose, Strict, Record, Timestamp, Verbose[V]:
Sweep range of sizes [n]:
Type escape sequence to abort.
Sending 20, 100-byte ICMP Echos to 82.133.85.65, timeout is 2 seconds:
Reply to request 0 (12 ms)
Reply to request 1 (32 ms)
Reply to request 2 (12 ms)
Reply to request 3 (20 ms)
Reply to request 4 (48 ms)
Reply to request 5 (8 ms)
Reply to request 6 (12 ms)
Reply to request 7 (28 ms)
Reply to request 8 (12 ms)
Reply to request 9 (12 ms)
Reply to request 10 (12 ms)
Reply to request 11 (48 ms)
Reply to request 12 (24 ms)
Reply to request 13 (32 ms)
Reply to request 14 (12 ms)
Reply to request 15 (20 ms)
Reply to request 16 (24 ms)
Reply to request 17 (32 ms)
Reply to request 18 (28 ms)
Reply to request 19 (24 ms)
Success rate is 100 percent (20/20), round-trip min/avg/max = 8/22/48 ms
2620-TestLab-CE#

Location: Luton, Bedfordshire - lutn-lutn-ubr-3 cable 3/0

Noggo · 06-02-2008, 17:21

Quote:

Originally Posted by zinglebarb

is that your ip address? wanna get hacked mate?

There is no hacking involved in this thread, why not google the IP then???
It's a jolt games server. I bet you that's what Cerberus did before pinging.

I understand where you're coming from, but I little common sense like googling the IP address first. Then posting a reply back, if you find out its not part of a major player in the gaming world.

Laters,

AntiSilence · 06-02-2008, 17:28

C:\>ping 82.133.85.65 -n 20

Pinging 82.133.85.65 with 32 bytes of data:

Reply from 82.133.85.65: bytes=32 time=13ms TTL=55
Reply from 82.133.85.65: bytes=32 time=13ms TTL=55
Reply from 82.133.85.65: bytes=32 time=22ms TTL=55
Reply from 82.133.85.65: bytes=32 time=28ms TTL=55
Reply from 82.133.85.65: bytes=32 time=32ms TTL=55
Reply from 82.133.85.65: bytes=32 time=16ms TTL=55
Reply from 82.133.85.65: bytes=32 time=17ms TTL=55
Reply from 82.133.85.65: bytes=32 time=18ms TTL=55
Reply from 82.133.85.65: bytes=32 time=26ms TTL=55
Reply from 82.133.85.65: bytes=32 time=19ms TTL=55
Reply from 82.133.85.65: bytes=32 time=13ms TTL=55
Reply from 82.133.85.65: bytes=32 time=16ms TTL=55
Reply from 82.133.85.65: bytes=32 time=15ms TTL=55
Reply from 82.133.85.65: bytes=32 time=13ms TTL=55
Reply from 82.133.85.65: bytes=32 time=14ms TTL=55
Reply from 82.133.85.65: bytes=32 time=15ms TTL=55
Reply from 82.133.85.65: bytes=32 time=27ms TTL=55
Reply from 82.133.85.65: bytes=32 time=12ms TTL=55
Reply from 82.133.85.65: bytes=32 time=12ms TTL=55
Reply from 82.133.85.65: bytes=32 time=15ms TTL=55

Ping statistics for 82.133.85.65:
Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 12ms, Maximum = 32ms, Average = 17ms

Location: Nottinghamshire.

nquinnathome1 · 06-02-2008, 17:36

ping -c 20 82.133.85.65
PING 82.133.85.65 (82.133.85.65) 56(84) bytes of data.
64 bytes from 82.133.85.65: icmp_seq=2 ttl=54 time=24.3 ms
64 bytes from 82.133.85.65: icmp_seq=3 ttl=54 time=25.0 ms
64 bytes from 82.133.85.65: icmp_seq=5 ttl=54 time=34.8 ms
64 bytes from 82.133.85.65: icmp_seq=6 ttl=54 time=27.5 ms
64 bytes from 82.133.85.65: icmp_seq=7 ttl=54 time=39.0 ms
64 bytes from 82.133.85.65: icmp_seq=8 ttl=54 time=51.7 ms
64 bytes from 82.133.85.65: icmp_seq=9 ttl=54 time=19.5 ms
64 bytes from 82.133.85.65: icmp_seq=10 ttl=54 time=28.7 ms
64 bytes from 82.133.85.65: icmp_seq=11 ttl=54 time=16.2 ms
64 bytes from 82.133.85.65: icmp_seq=12 ttl=54 time=35.5 ms
64 bytes from 82.133.85.65: icmp_seq=13 ttl=54 time=15.2 ms
64 bytes from 82.133.85.65: icmp_seq=14 ttl=54 time=14.8 ms
64 bytes from 82.133.85.65: icmp_seq=15 ttl=54 time=40.2 ms
64 bytes from 82.133.85.65: icmp_seq=16 ttl=54 time=23.5 ms
64 bytes from 82.133.85.65: icmp_seq=17 ttl=54 time=41.2 ms
64 bytes from 82.133.85.65: icmp_seq=18 ttl=54 time=18.2 ms
64 bytes from 82.133.85.65: icmp_seq=19 ttl=54 time=20.5 ms
64 bytes from 82.133.85.65: icmp_seq=20 ttl=54 time=21.2 ms

--- 82.133.85.65 ping statistics ---
20 packets transmitted, 18 received, 10% packet loss, time 19039ms
rtt min/avg/max/mdev = 14.858/27.650/51.726/10.263 ms

Loc: Hertfordshire

06-02-2008, 17:39

Quote:

Originally Posted by Noggo

There is no hacking involved in this thread, why not google the IP then???
It's a jolt games server. I bet you that's what Cerberus did before pinging.

I understand where you're coming from, but I little common sense like googling the IP address first. Then posting a reply back, if you find out its not part of a major player in the gaming world.

Laters,

That would of course have meant I had to assume you had common sense and why would I for all I knew you could have been just another noob doing something silly why would I think otherwise? Now a clever guy would have informed everyone where he wanted them to ping but still maybe thats asking to much

Ben B · 06-02-2008, 17:45

Here's what I get (currently on a sky broadband connection as not at home):

Quote:

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Compaq_Owner>ping 82.133.85.65

Pinging 82.133.85.65 with 32 bytes of data:

Reply from 82.133.85.65: bytes=32 time=84ms TTL=57
Reply from 82.133.85.65: bytes=32 time=84ms TTL=57
Reply from 82.133.85.65: bytes=32 time=84ms TTL=57
Reply from 82.133.85.65: bytes=32 time=84ms TTL=57

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

C:\Documents and Settings\Compaq_Owner>

bigdavep · 06-02-2008, 18:06

Pinging 82.133.85.65 with 32 bytes of data:

Reply from 82.133.85.65: bytes=32 time=27ms TTL=52
Reply from 82.133.85.65: bytes=32 time=17ms TTL=52
Reply from 82.133.85.65: bytes=32 time=16ms TTL=52
Reply from 82.133.85.65: bytes=32 time=17ms TTL=52
Reply from 82.133.85.65: bytes=32 time=19ms TTL=52
Reply from 82.133.85.65: bytes=32 time=16ms TTL=52
Reply from 82.133.85.65: bytes=32 time=17ms TTL=52
Reply from 82.133.85.65: bytes=32 time=17ms TTL=52
Reply from 82.133.85.65: bytes=32 time=36ms TTL=52
Reply from 82.133.85.65: bytes=32 time=19ms TTL=52
Reply from 82.133.85.65: bytes=32 time=38ms TTL=52
Reply from 82.133.85.65: bytes=32 time=42ms TTL=52
Reply from 82.133.85.65: bytes=32 time=17ms TTL=52
Reply from 82.133.85.65: bytes=32 time=18ms TTL=52
Reply from 82.133.85.65: bytes=32 time=17ms TTL=52
Reply from 82.133.85.65: bytes=32 time=22ms TTL=52
Reply from 82.133.85.65: bytes=32 time=32ms TTL=52
Reply from 82.133.85.65: bytes=32 time=17ms TTL=52
Reply from 82.133.85.65: bytes=32 time=16ms TTL=52
Reply from 82.133.85.65: bytes=32 time=16ms TTL=52

Ping statistics for 82.133.85.65:
Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 16ms, Maximum = 42ms, Average = 21ms

Location : Bolton, Gtr Manchester

Cerberus · 06-02-2008, 18:10

Quote:

Originally Posted by Noggo

There is no hacking involved in this thread, why not google the IP then???
It's a jolt games server. I bet you that's what Cerberus did before pinging.

I understand where you're coming from, but I little common sense like googling the IP address first. Then posting a reply back, if you find out its not part of a major player in the gaming world.

Laters,

In all fairness Noggo, Zing was looking out for you and not criticising. There have been people here before that have posted their actual IP Address, without thinking of the consequences or just because they are pure stupid enough to do so. I don't think of you as either.

I actually did a tracert on the IP to see where it was heading.

Jonathan90 · 06-02-2008, 18:13

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Jonathan>ping 82.133.85.65 -n 20

Pinging 82.133.85.65 with 32 bytes of data:

Reply from 82.133.85.65: bytes=32 time=16ms TTL=53
Reply from 82.133.85.65: bytes=32 time=13ms TTL=53
Reply from 82.133.85.65: bytes=32 time=14ms TTL=53
Reply from 82.133.85.65: bytes=32 time=14ms TTL=53
Reply from 82.133.85.65: bytes=32 time=13ms TTL=53
Reply from 82.133.85.65: bytes=32 time=16ms TTL=53
Reply from 82.133.85.65: bytes=32 time=17ms TTL=53
Reply from 82.133.85.65: bytes=32 time=14ms TTL=53
Reply from 82.133.85.65: bytes=32 time=14ms TTL=53
Reply from 82.133.85.65: bytes=32 time=13ms TTL=53
Reply from 82.133.85.65: bytes=32 time=13ms TTL=53
Reply from 82.133.85.65: bytes=32 time=13ms TTL=53
Reply from 82.133.85.65: bytes=32 time=13ms TTL=53
Reply from 82.133.85.65: bytes=32 time=13ms TTL=53
Reply from 82.133.85.65: bytes=32 time=15ms TTL=53
Reply from 82.133.85.65: bytes=32 time=13ms TTL=53
Reply from 82.133.85.65: bytes=32 time=13ms TTL=53
Reply from 82.133.85.65: bytes=32 time=13ms TTL=53
Reply from 82.133.85.65: bytes=32 time=14ms TTL=53
Reply from 82.133.85.65: bytes=32 time=13ms TTL=53

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

C:\Documents and Settings\Jonathan>

Wolverhampton **-**-**-**.cable.ubr02.wolv.blueyonder.co.uk