"Is it my Line" Report Tool

blaaislaai

blaaislaai

Executive Member
Joined
Mar 6, 2007
Messages
5,740
Zertop said:
It does look congested - however it is fairly consistent. Have you asked Telkom to reset the port?

Z
Click to expand...

Hi Z

I'll ask them for a reset, would it make a difference on a newly installed line? I can understand if the line is active for a few months/years to reset the port.
 
E

EmileS

Expert Member
Joined
Feb 13, 2013
Messages
1,033
I tried the tool. When it does the "Pinging Telkom Equipment" test. It gives an error after that and says it's going to close. What could that be?

Used the V1 latest.
 
Zertop

Zertop

Expert Member
Joined
Mar 9, 2013
Messages
3,105
EmileS said:
I tried the tool. When it does the "Pinging Telkom Equipment" test. It gives an error after that and says it's going to close. What could that be?

Used the V1 latest.
Click to expand...

Hi There,

Sorry - haven't been very active... have been waay to busy. What error does it give you?

Z :)
 
S

shaddowdragon

Well-Known Member
Joined
Dec 8, 2006
Messages
265
Zertop's "Is it my Line" Results
Basic Report:
Your packet loss was 3 percent.
Your average ping was 13ms.
Your maximum ping was 33ms.

You seem to have some packet loss. This indicates an issue on the line.
Looking at your average ping, your line seems to be running perfectly,
Looking at your maximum ping, however, it seems as though there could be a slight intermittant issue on the line. If required, please post the results to a forum post.

Detailed Report
Ping results to local Telkom equipment (all on Telkom's equipment)

Pinging 155.239.255.250 with 32 bytes of data:
Request timed out.
Reply from 155.239.255.250: bytes=32 time=10ms TTL=63
Reply from 155.239.255.250: bytes=32 time=12ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=33ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=33ms TTL=63
Reply from 155.239.255.250: bytes=32 time=10ms TTL=63
Reply from 155.239.255.250: bytes=32 time=12ms TTL=63
Reply from 155.239.255.250: bytes=32 time=12ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=24ms TTL=63
Reply from 155.239.255.250: bytes=32 time=10ms TTL=63
Reply from 155.239.255.250: bytes=32 time=10ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=12ms TTL=63
Reply from 155.239.255.250: bytes=32 time=10ms TTL=63
Reply from 155.239.255.250: bytes=32 time=22ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=10ms TTL=63
Reply from 155.239.255.250: bytes=32 time=10ms TTL=63
Reply from 155.239.255.250: bytes=32 time=12ms TTL=63
Reply from 155.239.255.250: bytes=32 time=10ms TTL=63
Reply from 155.239.255.250: bytes=32 time=10ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=12ms TTL=63
Reply from 155.239.255.250: bytes=32 time=12ms TTL=63
Reply from 155.239.255.250: bytes=32 time=10ms 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 = 10ms, Maximum = 33ms, Average = 13ms

2015/06/01 22:30:24.64

Am on Mweb line. How is this possible, my connection is soooooooooooooooooooooooooooooooooooooo slow. I do not even get these ping response times on some lans I look after.

Just sharing for the sake of it, will give it another week before raising it with mweb
 
Zertop

Zertop

Expert Member
Joined
Mar 9, 2013
Messages
3,105
shaddowdragon said:
Zertop's "Is it my Line" Results
Basic Report:
Your packet loss was 3 percent.
Your average ping was 13ms.
Your maximum ping was 33ms.

You seem to have some packet loss. This indicates an issue on the line.
Looking at your average ping, your line seems to be running perfectly,
Looking at your maximum ping, however, it seems as though there could be a slight intermittant issue on the line. If required, please post the results to a forum post.

Detailed Report
Ping results to local Telkom equipment (all on Telkom's equipment)

Pinging 155.239.255.250 with 32 bytes of data:
Request timed out.
Reply from 155.239.255.250: bytes=32 time=10ms TTL=63
Reply from 155.239.255.250: bytes=32 time=12ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=33ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=33ms TTL=63
Reply from 155.239.255.250: bytes=32 time=10ms TTL=63
Reply from 155.239.255.250: bytes=32 time=12ms TTL=63
Reply from 155.239.255.250: bytes=32 time=12ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=24ms TTL=63
Reply from 155.239.255.250: bytes=32 time=10ms TTL=63
Reply from 155.239.255.250: bytes=32 time=10ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=12ms TTL=63
Reply from 155.239.255.250: bytes=32 time=10ms TTL=63
Reply from 155.239.255.250: bytes=32 time=22ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=10ms TTL=63
Reply from 155.239.255.250: bytes=32 time=10ms TTL=63
Reply from 155.239.255.250: bytes=32 time=12ms TTL=63
Reply from 155.239.255.250: bytes=32 time=10ms TTL=63
Reply from 155.239.255.250: bytes=32 time=10ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=12ms TTL=63
Reply from 155.239.255.250: bytes=32 time=12ms TTL=63
Reply from 155.239.255.250: bytes=32 time=10ms 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 = 10ms, Maximum = 33ms, Average = 13ms

2015/06/01 22:30:24.64

Am on Mweb line. How is this possible, my connection is soooooooooooooooooooooooooooooooooooooo slow. I do not even get these ping response times on some lans I look after.

Just sharing for the sake of it, will give it another week before raising it with mweb
Click to expand...

Errm...

Do a ping test to mybroadband.co.za for me.

Z
 
Zertop

Zertop

Expert Member
Joined
Mar 9, 2013
Messages
3,105
BigBear said:
Mine does the same (Hangs on Testing Telkom Equipment) then Eventually gives and Error..

Can't reach Telkom Equipment etc.
Click to expand...

Could you try the old tool for now?

I will release a new version shortly. I've unfortunately been too busy to even think about the tool :(

Z
 
B

BigBear

Expert Member
Joined
Apr 24, 2008
Messages
2,197
DOWNLOADS [V2.x]:

Zertop's "Is it my Line" Results
Date/Time: Wed Jun 17 14:32:32 CAT 2015

Basic Report:

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

You have serious packet loss. Please post these results to the forum for advice.

Detailed Report:


Pinging 155.239.255.250 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 155.239.255.250:
Packets: Sent = 30, Received = 0, Lost = 30 (100% loss),
Click to expand...

Zertop's "Is it my Line" Results
Date/Time: Wed Jun 17 14:32:33 CAT 2015

Basic Report:

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

You have serious packet loss. Please post these results to the forum for advice.

Detailed Report:
Code: 
Pinging 155.239.255.250 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 155.239.255.250:
    Packets: Sent = 30, Received = 0, Lost = 30 (100% loss),

DOWNLOADS [V1.x]:

2015/06/17 14:41:04

20150617_144104_004440_LINDY-PC - TeamViewer - Free license (non-commercial use only).jpg

2015/06/17 14:44:23

20150617_144423_004441_LINDY-PC - TeamViewer - Free license (non-commercial use only).jpg

2015/06/17 14:44:39

20150617_144439_004442_LINDY-PC - TeamViewer - Free license (non-commercial use only).jpg
 
B

BigBear

Expert Member
Joined
Apr 24, 2008
Messages
2,197
Zertop said:
Okay something is very wrong there.

Please would you PM me a tracert to google.co.za

Z
Click to expand...

PM Sent.

Code: 
Tracing route to www.google.co.za [197.80.128.50]
over a maximum of 30 hops:

  1     1 ms     2 ms     2 ms  MWEB FON ROUTER
  2    13 ms     9 ms    10 ms  41-133-92-1.dsl.mweb.co.za [41.133.92.1]
  3    12 ms     9 ms     9 ms  197-80-96-186.jhb.mweb.co.za [197.80.96.186]
  4    10 ms    11 ms    12 ms  vl92.vic-hscore-1.optinet.net [197.80.2.1]
  5    15 ms    18 ms    15 ms  11.te0-0-0-2.vic-p-2.optinet.net [197.80.5.226]

  6    13 ms    12 ms    16 ms  202.te0-0-0-0.vic-pe-12.optinet.net [197.80.7.10
8]
  7    11 ms    10 ms    10 ms  197-80-128-50.jhb.mweb.co.za [197.80.128.50]

Trace complete.
 
Zertop

Zertop

Expert Member
Joined
Mar 9, 2013
Messages
3,105
New Update Released

V2.1.2
- Redesigned Update Procedure
- Now downloads/installs updates automatically from the web
- Source code released
- Required Manual Update
- New Launcher GUI
- Sped up tool
- Updated Interface
- Added more client-size information (version etc)
- Updated File Paths
- Updated Method for IP Fetching
- Temporarily removed support for old IP types
Click to expand...
 
Zertop

Zertop

Expert Member
Joined
Mar 9, 2013
Messages
3,105
Yuu said:
Thank you Z, you are just too good :D.

Let me know when you want us to provide future feature requests, have one or two in mind :p.
Click to expand...

Haha please - send them my way :)

I'll make them happen!

Z
 
B

BigBear

Expert Member
Joined
Apr 24, 2008
Messages
2,197
Tx. !

No Luck for me... lol

Zertop's "Is it my Line" Results
Date/Time: Thu Jun 18 19:30:24 CAT 2015

Basic Report:

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

You have serious packet loss. Please post these results to the forum for advice.

Detailed Report:
Code: 
Pinging 155.239.255.250 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 155.239.255.250:
    Packets: Sent = 30, Received = 0, Lost = 30 (100% loss),
 
You must log in or register to reply here.
Top