"Is it my Line" Report Tool

[Zertop]

Tried again, and it said Update skipped, make sure you are connected to the Internet.

Very weird!

I've just rebuilt my server so it should all be up and running again

Z

 

[Geurt]

Hi Z
Trying assess my very bad ADSL line, I downloaded the latest linetool.exe and run it. After a duration of indicating it was testing, it came back with answer of "Sorry, the tool was unable to ping your exhange address"

Why is that?

Cheers

 

[Zertop]

Hi Z
Trying assess my very bad ADSL line, I downloaded the latest linetool.exe and run it. After a duration of indicating it was testing, it came back with answer of "Sorry, the tool was unable to ping your exhange address"

Why is that?

Cheers

Aah it seems there is something up with your tracert then :/ Else your line is incredibly bad.

Please would you type the following into command prompt and post the results here:

tracert google.co.za

Thanks!
Z

 

[tdev]

Hi, I get the same message and here is my Tracert:

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

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

1 1 ms 1 ms 1 ms 192.168.1.1
2 52 ms 52 ms 44 ms 105-236-249-65-esr-lo.mtnbusiness.co.za [105.236
.249.65]
3 47 ms 92 ms 50 ms ipc-send-tb-3a.mtnbusiness.net [41.181.53.214]
4 46 ms 50 ms 46 ms tb-dca-2.za--qux-i.za.mtnbusiness.net [66.8.11.1
86]
5 49 ms 48 ms 48 ms compj-cpt-1.mtnns.net [196.44.18.2]
6 647 ms 598 ms 249 ms ls-cr-2--tb-cr-1.uk-b.mtnns.net [196.44.31.113]

7 226 ms 212 ms 192 ms ls-pr-2.uk--ls-cr-2.uk-a.mtn.net [209.212.111.18
7]
8 241 ms 255 ms 273 ms 209.212.99.13
9 199 ms 189 ms 190 ms 209.85.255.76
10 352 ms 350 ms 350 ms 66.249.95.9
11 351 ms 350 ms 352 ms 72.14.239.129
12 363 ms 352 ms 352 ms jnb01s08-in-f3.1e100.net [216.58.223.35]

Trace complete.

 

[lws]

Hi Zertop

I have the same problem as Geurt with the exchange address issue. My results:

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

1 69 ms 3 ms 2 ms 192.168.168.3
2 11 ms 11 ms 11 ms 196-210-136-1.dynamic.isadsl.co.za [196.210.136.1]
3 12 ms 12 ms 11 ms cdsl1-rba-vl2360.ip.isnet.net [196.38.73.133]
4 13 ms 34 ms 12 ms cdsl1-rba-vl150.ip.isnet.net [196.38.73.17]
5 13 ms * 14 ms core2b-pkl-te0-0-0-0.ip.isnet.net [196.26.0.63]
6 13 ms 12 ms 12 ms 196.26.0.130
7 13 ms 12 ms 16 ms 72.14.205.16
8 14 ms 13 ms 13 ms 72.14.239.129
9 41 ms 28 ms 69 ms jnb01s08-in-f3.1e100.net [216.58.223.35]

Trace complete.

Thanks

 

[Zertop]

Okay!

Let me check it out and see whats happening.

Z

 

[ebis]

Morning Zertop!

Any idea when you'll be able to have the updated tool available, without the previously mentioned error? Am getting the same error too.

Am getting some line disturbances and for the life of me, not able to gauge where the fault is. Your tool has previously assisted me in this regard!

 

[User4456]

Zertop's "Is it my Line" Results
Basic Report:

Your packet loss was 3 percent.
Your average ping was 18ms.
Your maximum ping was 484ms.

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 serious intermittent fault on the line. This could be a cause of an issue. Please post the results (at the end of the program) into the forum for advice.


Detailed Report

Ping results for last hop before account switches to ISP's hardware (Hop 2 on Tracert) 

Pinging 192.168.1.254 with 32 bytes of data:
Reply from 192.168.1.254: bytes=32 time=2ms TTL=253
Reply from 192.168.1.254: bytes=32 time=6ms TTL=253
Reply from 192.168.1.254: bytes=32 time=2ms TTL=253
Reply from 192.168.1.254: bytes=32 time=2ms TTL=253
Reply from 192.168.1.254: bytes=32 time=2ms TTL=253
Reply from 192.168.1.254: bytes=32 time=2ms TTL=253
Reply from 192.168.1.254: bytes=32 time=1ms TTL=253
Reply from 192.168.1.254: bytes=32 time=1ms TTL=253
Reply from 192.168.1.254: bytes=32 time=5ms TTL=253
Reply from 192.168.1.254: bytes=32 time=1ms TTL=253
Reply from 192.168.1.254: bytes=32 time=2ms TTL=253
Reply from 192.168.1.254: bytes=32 time=2ms TTL=253
Reply from 192.168.1.254: bytes=32 time=2ms TTL=253
Reply from 192.168.1.254: bytes=32 time=1ms TTL=253
Reply from 192.168.1.254: bytes=32 time=2ms TTL=253
Reply from 192.168.1.254: bytes=32 time=2ms TTL=253
Reply from 192.168.1.254: bytes=32 time=1ms TTL=253
Reply from 192.168.1.254: bytes=32 time=2ms TTL=253
Reply from 192.168.1.254: bytes=32 time=2ms TTL=253
Reply from 192.168.1.254: bytes=32 time=1ms TTL=253
Reply from 192.168.1.254: bytes=32 time=1ms TTL=253
Reply from 192.168.1.254: bytes=32 time=484ms TTL=253
Request timed out.
Reply from 192.168.1.254: bytes=32 time=1ms TTL=253
Reply from 192.168.1.254: bytes=32 time=2ms TTL=253
Reply from 192.168.1.254: bytes=32 time=3ms TTL=253
Reply from 192.168.1.254: bytes=32 time=2ms TTL=253
Reply from 192.168.1.254: bytes=32 time=2ms TTL=253
Reply from 192.168.1.254: bytes=32 time=1ms TTL=253
Reply from 192.168.1.254: bytes=32 time=2ms TTL=253

Ping statistics for 192.168.1.254:
    Packets: Sent = 30, Received = 29, Lost = 1 (3% loss),
Approximate round trip times in milli-seconds:
    Minimum = 1ms, Maximum = 484ms, Average = 18ms
 
2015/02/21 10:46:26.35

There's a manhole in my driveway where the telkom line comes in. There's some dampness, dripping water, a mess of cables down there with exposed dry joints, some of which I am not sure they are telephone cables or what...

I am going to assume this is the root source of my interference... would I be correct?

 

[Foxhound5366]

Okay!

Let me check it out and see whats happening.

Z

Any progress on solving this 'cannot ping' issue, Zertop? Just tried your tool for the first time, it's also bombing out like the other guys' (and I'm actually confident that my line has no issues).

 

[Zertop]

Any progress on solving this 'cannot ping' issue, Zertop? Just tried your tool for the first time, it's also bombing out like the other guys' (and I'm actually confident that my line has no issues).

Hi,

Sorry - completely forgot about this, been incredibly busy.

Could you please run a trace route (tracert google.co.za) for me. I have a suspicion that telkom is starting to firewall their second hop against ICMP (What ping uses) - as my second hop also seems to timeout.

Z

 

[ghostR]

Hi,

Sorry - completely forgot about this, been incredibly busy.

Could you please run a trace route (tracert google.co.za) for me. I have a suspicion that telkom is starting to firewall their second hop against ICMP (What ping uses) - as my second hop also seems to timeout.

Z

That would be correct, Majority of 2nd hops (Exchanges) ICMP has been turned off.

 

[Zertop]

That would be correct, Majority of 2nd hops (Exchanges) ICMP has been turned off.

In that case - there is no longer a reliable way to determine an issue between ISP/Line

Z

 

[ghostR]

In that case - there is no longer a reliable way to determine an issue between ISP/Line

Z

Indeed there is not, Without testing with multiple ISPs of course.

 

[Zertop]

Indeed there is not, Without testing with multiple ISPs of course.

Damn.

Alright - well then I guess I will need to find a workaround, or go for second best (pinging third hop).

I will investigate.

Z

 

[Crystal Web]

Damn.

Alright - well then I guess I will need to find a workaround, or go for second best (pinging third hop).

I will investigate.

Z

Ironically, this may end up with Telkom being blamed for ISP problems.

It's not really viable to test the third hop for Telkom issues unless you manually aquizz over the results and make a determination. Also, an ISP can do so watching their traffic charts to make determinations. And end user or your tool won't be able to, so it won't work all that well.

 

[Zertop]

Ironically, this may end up with Telkom being blamed for ISP problems.

It's not really viable to test the third hop for Telkom issues unless you manually aquizz over the results and make a determination. Also, an ISP can do so watching their traffic charts to make determinations. And end user or your tool won't be able to, so it won't work all that well.

Funny... isn't it Yep, that is what I am afraid of.

I have been contacted with an IP address which apparently is the direct route to the telkom gateway for that specific province - and does not pass through to the ISP. I have asked telkom for clarification

Z

 

[Zertop]

Hi All,

If you live in Johannesburg, Durban or Port Elizabeth and have a minute - please would you PM me. I need a few people to test something for me as a possible fix.

Thanks!
Z

 

[cortexenslaver]

Hi Zertop,

Thanks for all your hard work on the tools... been using them for a long time. Unfortunately, I noticed the same problem with the line tool not picking up the correct IP since last year. Strangely, the IP it picks up is an HP assigned IP (16.58.223.35).

 

[Zertop]

Hi Zertop,

Thanks for all your hard work on the tools... been using them for a long time. Unfortunately, I noticed the same problem with the line tool not picking up the correct IP since last year. Strangely, the IP it picks up is an HP assigned IP (16.58.223.35).

Hi There,

That might be due to a out-of-the-ordinary setup on your side. Could you possibly PM me a full trace route?

I will be launching a new update to the tool soon - which will hopefully solve all these issues.

Z

 

[Zertop]

New Update! Should fix all the issues that you have been experiencing.

13. 19-03-2015
- Telkom are in the process of upgrading all the dslams + exchange with Alcatel BNG equipment.
- Alcatel BNG blocks ICMP (Ping) requests, and therefore blocks this tool.
- Replaced the local exchange IP address with the Telkom Gateway
- Tool still allows for determining whether a fault lies with Telkom/ISP.
- Still pings Telkom's network without letting ISP issues get in the way.
- Now includes local area issues with Telkom, not just last mile.

Sorry for the delay.
Z