"Is it my Line" Report Tool

N

Niner

Well-Known Member
Joined
Aug 11, 2012
Messages
477
If I'm not able to ping 155.239.255.250, what does that mean?

I'm on wifi on my pc - internet through ADSL.

Can't manage through main pc connected directly to ADSL either.

I can ping google, for instance.
 
LaraC

LaraC

Honorary Master
Joined
Mar 11, 2014
Messages
42,675
Niner said:
If I'm not able to ping 155.239.255.250, what does that mean?

I'm on wifi on my pc - internet through ADSL.

Can't manage through main pc connected directly to ADSL either.

I can ping google, for instance.
Click to expand...
Are you connected with a Telkom account? I'm guessing that Telkom restrict access to their equipment at newer exchanges.
 
Zertop

Zertop

Expert Member
Joined
Mar 9, 2013
Messages
3,105
Niner said:
If I'm not able to ping 155.239.255.250, what does that mean?

I'm on wifi on my pc - internet through ADSL.

Can't manage through main pc connected directly to ADSL either.

I can ping google, for instance.
Click to expand...

Only newer exchanges will be able to ping 155.239.255.250. For older exchanges, most likely like yours, the tool will automatically detect the correct IP to ping :)

You should be able to run the tool if Java is installed correctly!

Z
 
Drifter

Drifter

Honorary Master
Joined
Dec 19, 2012
Messages
22,825
Something is off. Linetool says I have a problem with my line, but linespeed tests show near perfect on three ISP's? Odd.
 
Drifter

Drifter

Honorary Master
Joined
Dec 19, 2012
Messages
22,825
Zertop said:
Could you post your detailed report here please :)

Z
Click to expand...

Sure: Linetool report , then two speed tests:

Pinging 155.239.255.250 with 32 bytes of data:
Reply from 155.239.255.250: bytes=32 time=284ms TTL=63
Reply from 155.239.255.250: bytes=32 time=156ms TTL=63
Reply from 155.239.255.250: bytes=32 time=161ms TTL=63
Reply from 155.239.255.250: bytes=32 time=239ms TTL=63
Reply from 155.239.255.250: bytes=32 time=164ms TTL=63
Reply from 155.239.255.250: bytes=32 time=226ms TTL=63
Reply from 155.239.255.250: bytes=32 time=144ms TTL=63
Reply from 155.239.255.250: bytes=32 time=180ms TTL=63
Reply from 155.239.255.250: bytes=32 time=183ms TTL=63
Reply from 155.239.255.250: bytes=32 time=296ms TTL=63
Reply from 155.239.255.250: bytes=32 time=134ms TTL=63
Reply from 155.239.255.250: bytes=32 time=225ms TTL=63
Reply from 155.239.255.250: bytes=32 time=117ms TTL=63
Reply from 155.239.255.250: bytes=32 time=363ms TTL=63
Reply from 155.239.255.250: bytes=32 time=204ms TTL=63
Reply from 155.239.255.250: bytes=32 time=181ms TTL=63
Reply from 155.239.255.250: bytes=32 time=216ms TTL=63
Reply from 155.239.255.250: bytes=32 time=187ms TTL=63
Reply from 155.239.255.250: bytes=32 time=367ms TTL=63
Reply from 155.239.255.250: bytes=32 time=162ms TTL=63
Reply from 155.239.255.250: bytes=32 time=182ms TTL=63
Reply from 155.239.255.250: bytes=32 time=171ms TTL=63
Reply from 155.239.255.250: bytes=32 time=173ms TTL=63
Reply from 155.239.255.250: bytes=32 time=315ms TTL=63
Reply from 155.239.255.250: bytes=32 time=186ms TTL=63
Reply from 155.239.255.250: bytes=32 time=281ms TTL=63
Reply from 155.239.255.250: bytes=32 time=216ms TTL=63
Reply from 155.239.255.250: bytes=32 time=367ms TTL=63
Reply from 155.239.255.250: bytes=32 time=141ms TTL=63
Reply from 155.239.255.250: bytes=32 time=212ms TTL=63

Ping statistics for 155.239.255.250:
Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 117ms, Maximum = 367ms, Average = 214ms


Telkom

Last Result:
Download Speed: 8794 kbps (1099.3 KB/sec transfer rate)
Upload Speed: 862 kbps (107.8 KB/sec transfer rate)
Latency: 21 ms
2015/09/24, 8:47:16 PM


MWEB

Last Result:
Download Speed: 8853 kbps (1106.6 KB/sec transfer rate)
Upload Speed: 865 kbps (108.1 KB/sec transfer rate)
Latency: 22 ms
2015/09/24, 8:50:48 PM
 
Zertop

Zertop

Expert Member
Joined
Mar 9, 2013
Messages
3,105
Drifter said:
Sure: Linetool report , then two speed tests:

Pinging 155.239.255.250 with 32 bytes of data:
Reply from 155.239.255.250: bytes=32 time=284ms TTL=63
Reply from 155.239.255.250: bytes=32 time=156ms TTL=63
Reply from 155.239.255.250: bytes=32 time=161ms TTL=63
Reply from 155.239.255.250: bytes=32 time=239ms TTL=63
Reply from 155.239.255.250: bytes=32 time=164ms TTL=63
Reply from 155.239.255.250: bytes=32 time=226ms TTL=63
Reply from 155.239.255.250: bytes=32 time=144ms TTL=63
Reply from 155.239.255.250: bytes=32 time=180ms TTL=63
Reply from 155.239.255.250: bytes=32 time=183ms TTL=63
Reply from 155.239.255.250: bytes=32 time=296ms TTL=63
Reply from 155.239.255.250: bytes=32 time=134ms TTL=63
Reply from 155.239.255.250: bytes=32 time=225ms TTL=63
Reply from 155.239.255.250: bytes=32 time=117ms TTL=63
Reply from 155.239.255.250: bytes=32 time=363ms TTL=63
Reply from 155.239.255.250: bytes=32 time=204ms TTL=63
Reply from 155.239.255.250: bytes=32 time=181ms TTL=63
Reply from 155.239.255.250: bytes=32 time=216ms TTL=63
Reply from 155.239.255.250: bytes=32 time=187ms TTL=63
Reply from 155.239.255.250: bytes=32 time=367ms TTL=63
Reply from 155.239.255.250: bytes=32 time=162ms TTL=63
Reply from 155.239.255.250: bytes=32 time=182ms TTL=63
Reply from 155.239.255.250: bytes=32 time=171ms TTL=63
Reply from 155.239.255.250: bytes=32 time=173ms TTL=63
Reply from 155.239.255.250: bytes=32 time=315ms TTL=63
Reply from 155.239.255.250: bytes=32 time=186ms TTL=63
Reply from 155.239.255.250: bytes=32 time=281ms TTL=63
Reply from 155.239.255.250: bytes=32 time=216ms TTL=63
Reply from 155.239.255.250: bytes=32 time=367ms TTL=63
Reply from 155.239.255.250: bytes=32 time=141ms TTL=63
Reply from 155.239.255.250: bytes=32 time=212ms TTL=63

Ping statistics for 155.239.255.250:
Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 117ms, Maximum = 367ms, Average = 214ms


Telkom

Last Result:
Download Speed: 8794 kbps (1099.3 KB/sec transfer rate)
Upload Speed: 862 kbps (107.8 KB/sec transfer rate)
Latency: 21 ms
2015/09/24, 8:47:16 PM


MWEB

Last Result:
Download Speed: 8853 kbps (1106.6 KB/sec transfer rate)
Upload Speed: 865 kbps (108.1 KB/sec transfer rate)
Latency: 22 ms
2015/09/24, 8:50:48 PM
Click to expand...

Now that's strange...

Let me have a look.

Z
 
B

Buglish

Active Member
Joined
Nov 21, 2005
Messages
84
Thanks this tools is super cool :)

Zertop's "Is it my Line" Results
Date/Time: Fri Oct 09 00:18:51 CAT 2015

Basic Report:

Your packet loss was 3%.
Your average ping was 1015ms.
Your maximum ping was 2314ms.

You seem to have some packet loss. This indicates an issue on the line.
Looking at your average ping, there is definitely something wrong with your line! Please post the results (at the end of the program) into the forum for advice!

Detailed Report:

Pinging 155.239.255.250 with 32 bytes of data:
Reply from 155.239.255.250: bytes=32 time=143ms TTL=63
Reply from 155.239.255.250: bytes=32 time=1785ms TTL=63
Reply from 155.239.255.250: bytes=32 time=1933ms TTL=63
Reply from 155.239.255.250: bytes=32 time=2275ms TTL=63
Reply from 155.239.255.250: bytes=32 time=2314ms TTL=63
Reply from 155.239.255.250: bytes=32 time=1892ms TTL=63
Reply from 155.239.255.250: bytes=32 time=1765ms TTL=63
Reply from 155.239.255.250: bytes=32 time=1662ms TTL=63
Reply from 155.239.255.250: bytes=32 time=1844ms TTL=63
Reply from 155.239.255.250: bytes=32 time=447ms TTL=63
Reply from 155.239.255.250: bytes=32 time=151ms TTL=63
Reply from 155.239.255.250: bytes=32 time=94ms TTL=63
Reply from 155.239.255.250: bytes=32 time=68ms TTL=63
Reply from 155.239.255.250: bytes=32 time=134ms TTL=63
Reply from 155.239.255.250: bytes=32 time=169ms TTL=63
Reply from 155.239.255.250: bytes=32 time=147ms TTL=63
Reply from 155.239.255.250: bytes=32 time=121ms TTL=63
Reply from 155.239.255.250: bytes=32 time=230ms TTL=63
Reply from 155.239.255.250: bytes=32 time=156ms TTL=63
Reply from 155.239.255.250: bytes=32 time=130ms TTL=63
Reply from 155.239.255.250: bytes=32 time=89ms TTL=63
Reply from 155.239.255.250: bytes=32 time=99ms TTL=63
Reply from 155.239.255.250: bytes=32 time=334ms TTL=63
Reply from 155.239.255.250: bytes=32 time=2117ms TTL=63
Request timed out.
Reply from 155.239.255.250: bytes=32 time=1673ms TTL=63
Reply from 155.239.255.250: bytes=32 time=1929ms TTL=63
Reply from 155.239.255.250: bytes=32 time=1943ms TTL=63
Reply from 155.239.255.250: bytes=32 time=1868ms TTL=63
Reply from 155.239.255.250: bytes=32 time=1946ms TTL=63

Ping statistics for 155.239.255.250:
Packets: Sent = 30, Received = 29, Lost = 1 (3% loss),
Approximate round trip times in milli-seconds:
Minimum = 68ms, Maximum = 2314ms, Average = 1015ms
Click to expand...

Zertop's "Is it my Line" Results
Date/Time: Fri Oct 09 00:24:32 CAT 2015

Basic Report:

Your packet loss was 0%.
Your average ping was 910ms.
Your maximum ping was 2290ms.

Looking at your average ping, there is definitely something wrong with your line! Please post the results (at the end of the program) into the forum for advice!

Detailed Report:

Pinging 155.239.255.250 with 32 bytes of data:
Reply from 155.239.255.250: bytes=32 time=1291ms TTL=63
Reply from 155.239.255.250: bytes=32 time=2087ms TTL=63
Reply from 155.239.255.250: bytes=32 time=2155ms TTL=63
Reply from 155.239.255.250: bytes=32 time=1745ms TTL=63
Reply from 155.239.255.250: bytes=32 time=1374ms TTL=63
Reply from 155.239.255.250: bytes=32 time=1404ms TTL=63
Reply from 155.239.255.250: bytes=32 time=1545ms TTL=63
Reply from 155.239.255.250: bytes=32 time=1773ms TTL=63
Reply from 155.239.255.250: bytes=32 time=1821ms TTL=63
Reply from 155.239.255.250: bytes=32 time=1730ms TTL=63
Reply from 155.239.255.250: bytes=32 time=1848ms TTL=63
Reply from 155.239.255.250: bytes=32 time=2290ms TTL=63
Reply from 155.239.255.250: bytes=32 time=1510ms TTL=63
Reply from 155.239.255.250: bytes=32 time=689ms TTL=63
Reply from 155.239.255.250: bytes=32 time=93ms TTL=63
Reply from 155.239.255.250: bytes=32 time=117ms TTL=63
Reply from 155.239.255.250: bytes=32 time=97ms TTL=63
Reply from 155.239.255.250: bytes=32 time=87ms TTL=63
Reply from 155.239.255.250: bytes=32 time=148ms TTL=63
Reply from 155.239.255.250: bytes=32 time=126ms TTL=63
Reply from 155.239.255.250: bytes=32 time=110ms TTL=63
Reply from 155.239.255.250: bytes=32 time=40ms TTL=63
Reply from 155.239.255.250: bytes=32 time=62ms TTL=63
Reply from 155.239.255.250: bytes=32 time=369ms TTL=63
Reply from 155.239.255.250: bytes=32 time=305ms TTL=63
Reply from 155.239.255.250: bytes=32 time=217ms TTL=63
Reply from 155.239.255.250: bytes=32 time=118ms TTL=63
Reply from 155.239.255.250: bytes=32 time=132ms TTL=63
Reply from 155.239.255.250: bytes=32 time=825ms TTL=63
Reply from 155.239.255.250: bytes=32 time=1192ms TTL=63

Ping statistics for 155.239.255.250:
Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 40ms, Maximum = 2290ms, Average = 910ms
Click to expand...
 
B

Buglish

Active Member
Joined
Nov 21, 2005
Messages
84
Zertop's "Is it my Line" Results
Date/Time: Fri Oct 09 08:58:57 CAT 2015

Basic Report:

Your packet loss was 0%.
Your average ping was 136ms.
Your maximum ping was 165ms.

Looking at your average ping, there is definitely something wrong with your line! Please post the results (at the end of the program) into the forum for advice!

Detailed Report:
Code: 
Pinging 155.239.255.250 with 32 bytes of data:
Reply from 155.239.255.250: bytes=32 time=158ms TTL=63
Reply from 155.239.255.250: bytes=32 time=96ms TTL=63
Reply from 155.239.255.250: bytes=32 time=89ms TTL=63
Reply from 155.239.255.250: bytes=32 time=128ms TTL=63
Reply from 155.239.255.250: bytes=32 time=131ms TTL=63
Reply from 155.239.255.250: bytes=32 time=129ms TTL=63
Reply from 155.239.255.250: bytes=32 time=140ms TTL=63
Reply from 155.239.255.250: bytes=32 time=118ms TTL=63
Reply from 155.239.255.250: bytes=32 time=122ms TTL=63
Reply from 155.239.255.250: bytes=32 time=122ms TTL=63
Reply from 155.239.255.250: bytes=32 time=158ms TTL=63
Reply from 155.239.255.250: bytes=32 time=134ms TTL=63
Reply from 155.239.255.250: bytes=32 time=127ms TTL=63
Reply from 155.239.255.250: bytes=32 time=135ms TTL=63
Reply from 155.239.255.250: bytes=32 time=124ms TTL=63
Reply from 155.239.255.250: bytes=32 time=126ms TTL=63
Reply from 155.239.255.250: bytes=32 time=108ms TTL=63
Reply from 155.239.255.250: bytes=32 time=156ms TTL=63
Reply from 155.239.255.250: bytes=32 time=158ms TTL=63
Reply from 155.239.255.250: bytes=32 time=156ms TTL=63
Reply from 155.239.255.250: bytes=32 time=145ms TTL=63
Reply from 155.239.255.250: bytes=32 time=160ms TTL=63
Reply from 155.239.255.250: bytes=32 time=165ms TTL=63
Reply from 155.239.255.250: bytes=32 time=111ms TTL=63
Reply from 155.239.255.250: bytes=32 time=130ms TTL=63
Reply from 155.239.255.250: bytes=32 time=156ms TTL=63
Reply from 155.239.255.250: bytes=32 time=150ms TTL=63
Reply from 155.239.255.250: bytes=32 time=146ms TTL=63
Reply from 155.239.255.250: bytes=32 time=143ms TTL=63
Reply from 155.239.255.250: bytes=32 time=164ms TTL=63

Ping statistics for 155.239.255.250:
    Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 89ms, Maximum = 165ms, Average = 136ms

So at night it is way worse.

Could this be a internal cable problem or the line hat goes to the DB box?
 
Zertop

Zertop

Expert Member
Joined
Mar 9, 2013
Messages
3,105
Buglish said:
Zertop's "Is it my Line" Results
Date/Time: Fri Oct 09 08:58:57 CAT 2015

Basic Report:

Your packet loss was 0%.
Your average ping was 136ms.
Your maximum ping was 165ms.

Looking at your average ping, there is definitely something wrong with your line! Please post the results (at the end of the program) into the forum for advice!

Detailed Report:
Code: 
Pinging 155.239.255.250 with 32 bytes of data:
Reply from 155.239.255.250: bytes=32 time=158ms TTL=63
Reply from 155.239.255.250: bytes=32 time=96ms TTL=63
Reply from 155.239.255.250: bytes=32 time=89ms TTL=63
Reply from 155.239.255.250: bytes=32 time=128ms TTL=63
Reply from 155.239.255.250: bytes=32 time=131ms TTL=63
Reply from 155.239.255.250: bytes=32 time=129ms TTL=63
Reply from 155.239.255.250: bytes=32 time=140ms TTL=63
Reply from 155.239.255.250: bytes=32 time=118ms TTL=63
Reply from 155.239.255.250: bytes=32 time=122ms TTL=63
Reply from 155.239.255.250: bytes=32 time=122ms TTL=63
Reply from 155.239.255.250: bytes=32 time=158ms TTL=63
Reply from 155.239.255.250: bytes=32 time=134ms TTL=63
Reply from 155.239.255.250: bytes=32 time=127ms TTL=63
Reply from 155.239.255.250: bytes=32 time=135ms TTL=63
Reply from 155.239.255.250: bytes=32 time=124ms TTL=63
Reply from 155.239.255.250: bytes=32 time=126ms TTL=63
Reply from 155.239.255.250: bytes=32 time=108ms TTL=63
Reply from 155.239.255.250: bytes=32 time=156ms TTL=63
Reply from 155.239.255.250: bytes=32 time=158ms TTL=63
Reply from 155.239.255.250: bytes=32 time=156ms TTL=63
Reply from 155.239.255.250: bytes=32 time=145ms TTL=63
Reply from 155.239.255.250: bytes=32 time=160ms TTL=63
Reply from 155.239.255.250: bytes=32 time=165ms TTL=63
Reply from 155.239.255.250: bytes=32 time=111ms TTL=63
Reply from 155.239.255.250: bytes=32 time=130ms TTL=63
Reply from 155.239.255.250: bytes=32 time=156ms TTL=63
Reply from 155.239.255.250: bytes=32 time=150ms TTL=63
Reply from 155.239.255.250: bytes=32 time=146ms TTL=63
Reply from 155.239.255.250: bytes=32 time=143ms TTL=63
Reply from 155.239.255.250: bytes=32 time=164ms TTL=63

Ping statistics for 155.239.255.250:
    Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 89ms, Maximum = 165ms, Average = 136ms

So at night it is way worse.

Could this be a internal cable problem or the line hat goes to the DB box?
Click to expand...

That definitely sounds like exchange congestion. However, your ping should, ideally, be sitting at around 20ms.

It's still waay to high!

Have you tried a port reset?

Z :)
 
J

Jakkels1991

Expert Member
Joined
Apr 4, 2014
Messages
1,347
Afternoon Z

Getting the below when trying to run the test:

Sorry, the tool was unable to detect an IP to ping.
Please ensure that you are connected to the internet.

Detailed:
java.lang.iiilegalStateException: No match found

Trecing route to zertop.com[154.127.61.124]
over a maximum of 2 hops:

1 <1ms <1ms <1ms 10.0.0.2
2 <397ms 400 ms 318ms rkmp-ip-bb-2.norh.dsl.telkomsa.net[105.224.204.1]

Trace complete.
 
E

electrofreeze

Expert Member
Joined
Jun 12, 2004
Messages
1,088
hi zertop

can you tell me why only the display results on screen works on the mac
when i click on the other 2 links nothing happens in the line tool
 
Zertop

Zertop

Expert Member
Joined
Mar 9, 2013
Messages
3,105
electrofreeze said:
hi zertop

can you tell me why only the display results on screen works on the mac
when i click on the other 2 links nothing happens in the line tool
Click to expand...

Hi There,

Ill have to check it out. Let me get back to you on that, as I don't have a mac to test on.

Z
 
Zertop

Zertop

Expert Member
Joined
Mar 9, 2013
Messages
3,105
Jakkels1991 said:
Afternoon Z

Getting the below when trying to run the test:

Sorry, the tool was unable to detect an IP to ping.
Please ensure that you are connected to the internet.

Detailed:
java.lang.iiilegalStateException: No match found

Trecing route to zertop.com[154.127.61.124]
over a maximum of 2 hops:

1 <1ms <1ms <1ms 10.0.0.2
2 <397ms 400 ms 318ms rkmp-ip-bb-2.norh.dsl.telkomsa.net[105.224.204.1]

Trace complete.
Click to expand...

Hi There,

There seems to be an anomaly in tour second hop, which is throwing out the error (the < shouldn't be there). Ill see if I can make a patch :)

Z
 
B

bstarkey

Well-Known Member
Joined
Dec 19, 2012
Messages
187
Zertop's "Is it my Line" Results
Date/Time: Wed Oct 28 07:32:41 SAST 2015

Basic Report:

Your packet loss was 0%.
Your average ping was 0ms.
Your maximum ping was 0ms.

Looking at your average ping, your line seems to be running perfectly.
It seems that your maximum ping is also good. If there are any issues, they most probably lie with your ISP

Detailed Report:
Code: 
PING 155.239.255.250 (155.239.255.250): 56 data bytes
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
Request timeout for icmp_seq 2
Request timeout for icmp_seq 3
Request timeout for icmp_seq 4
Request timeout for icmp_seq 5
Request timeout for icmp_seq 6
Request timeout for icmp_seq 7
Request timeout for icmp_seq 8
Request timeout for icmp_seq 9
Request timeout for icmp_seq 10
Request timeout for icmp_seq 11
Request timeout for icmp_seq 12
Request timeout for icmp_seq 13
Request timeout for icmp_seq 14
Request timeout for icmp_seq 15
Request timeout for icmp_seq 16
Request timeout for icmp_seq 17
Request timeout for icmp_seq 18
Request timeout for icmp_seq 19
Request timeout for icmp_seq 20
Request timeout for icmp_seq 21
Request timeout for icmp_seq 22
Request timeout for icmp_seq 23
Request timeout for icmp_seq 24
Request timeout for icmp_seq 25
Request timeout for icmp_seq 26
Request timeout for icmp_seq 27
Request timeout for icmp_seq 28

--- 155.239.255.250 ping statistics ---
30 packets transmitted, 0 packets received, 100.0% packet loss


Running on Mac, also tried in windows 7 VM, similar problem. Any solutions yet?
 
Zertop

Zertop

Expert Member
Joined
Mar 9, 2013
Messages
3,105
bstarkey said:
Zertop's "Is it my Line" Results
Date/Time: Wed Oct 28 07:32:41 SAST 2015

Basic Report:

Your packet loss was 0%.
Your average ping was 0ms.
Your maximum ping was 0ms.

Looking at your average ping, your line seems to be running perfectly.
It seems that your maximum ping is also good. If there are any issues, they most probably lie with your ISP

Detailed Report:
Code: 
PING 155.239.255.250 (155.239.255.250): 56 data bytes
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
Request timeout for icmp_seq 2
Request timeout for icmp_seq 3
Request timeout for icmp_seq 4
Request timeout for icmp_seq 5
Request timeout for icmp_seq 6
Request timeout for icmp_seq 7
Request timeout for icmp_seq 8
Request timeout for icmp_seq 9
Request timeout for icmp_seq 10
Request timeout for icmp_seq 11
Request timeout for icmp_seq 12
Request timeout for icmp_seq 13
Request timeout for icmp_seq 14
Request timeout for icmp_seq 15
Request timeout for icmp_seq 16
Request timeout for icmp_seq 17
Request timeout for icmp_seq 18
Request timeout for icmp_seq 19
Request timeout for icmp_seq 20
Request timeout for icmp_seq 21
Request timeout for icmp_seq 22
Request timeout for icmp_seq 23
Request timeout for icmp_seq 24
Request timeout for icmp_seq 25
Request timeout for icmp_seq 26
Request timeout for icmp_seq 27
Request timeout for icmp_seq 28

--- 155.239.255.250 ping statistics ---
30 packets transmitted, 0 packets received, 100.0% packet loss


Running on Mac, also tried in windows 7 VM, similar problem. Any solutions yet?
Click to expand...

That's odd....

Could you please do a traceroute for me, to zertop.com :)

Z
 
You must log in or register to reply here.
Top