PIERRE VAN RYNEVELD ADSL Users please assist

M

Mr.Jax

Expert Member
Joined
Sep 22, 2009
Messages
1,461
Again thanks to all.

My contact explicitly stated that traceroutes are very important here, so when latency is bad again, please tracert www.is.co.za, games.saix.net and www.mweb.co.za.
Also specify which ISP you're using. << this is important.
What would help even more is if you can repeat the tests using the guest telkom login (I think it is guest@telkom.co.za pwd:guest) and tracert to www.telkom.co.za

Thanks.

EDIT: Telkom guest details (unverified)
guest1@telkomadsl
guest1

or

guest@telkomadsl
guest
 
Last edited:
J

jellievis

Senior Member
Joined
May 2, 2007
Messages
504
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved

C:\Windows\system32>tracert www.is.co.za

Tracing route to www.is.co.za [196.37.113.28]
over a maximum of 30 hops:

1 166 ms 1 ms 1 ms home.gateway [192.168.1.254]
2 * * * Request timed out.
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

MR Jax, is this it?
 
M

Mr.Jax

Expert Member
Joined
Sep 22, 2009
Messages
1,461
Eish, that traceroute does not look too good :(

You might have latencies > 2 seconds hence the timeouts all the way. So try this:
tracert -w 5000 www.is.co.za

If it still shows timeouts, increase the 5000 to e.g. 10000

If its still timing out, there might be something else wrong. Maybe no "PPP connection to your ISP"
 
Last edited:
J

jellievis

Senior Member
Joined
May 2, 2007
Messages
504
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\>tracert -w 5000 www.is.co.za

Tracing route to www.is.co.za [196.37.113.28]
over a maximum of 30 hops:

1 2 ms 1 ms 1 ms home.gateway [192.168.1.254]
2 * * * Request timed out.
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

C:\>tracert -w 10000 www.is.co.za

Tracing route to www.is.co.za [196.37.113.28]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms home.gateway [192.168.1.254]
2 * * * Request timed out.
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

?????
 
A

andrerobbertse

New Member
Joined
Oct 13, 2010
Messages
8
Status on this ?

Hi,

Im also living in this area and have endless problems with my Adsl 4mb line, it keeps disconnecting.
So is this problem still ongoing or what?

Thanks
 
M

Mr.Jax

Expert Member
Joined
Sep 22, 2009
Messages
1,461
Yes, this problem is still going on, but i don't think its why your DSL is disconnecting.

The contact cant help me unless I'm a customer of his ISP and that itself cant guarantee anything.
So, I'm fed up now. Telkom won't see any more of my money (or the company I work for), they've had their chance to fix this....*** them. I'm done.
 
EricBusy

EricBusy

New Member
Joined
Oct 23, 2010
Messages
5
I'm in PvR, 012 662 1xxx. My ISP is WA, have a DSL Data Shaped account.

My router SnR etc is:
Signal to Noise ratio: Ds: 10.0 Us: 8.0
Line Attenuation: Ds: 59.0 Us: 31.5
Data Rate: Ds: 4096 Us: 640


Tracing route to www.is.co.za [196.37.113.28]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.254
2 * * * Request timed out.
3 * * * Request timed out.
4 * 52 ms 68 ms vl34.er.gw.cpt.za.wa.co.za [41.185.0.34]
5 * 43 ms 44 ms upstream.vl101.gw.cpt.za.wa.co.za [196.220.59.226]
6 46 ms 59 ms 61 ms 196.43.11.218
7 44 ms 44 ms 44 ms 196.43.25.206
8 45 ms 45 ms 45 ms 196.25.247.26
9 46 ms 45 ms 45 ms core1a-ctn-gi0-1.ip.isnet.net [168.209.2.5]
10 68 ms 68 ms 67 ms core1a-pkl-gi0-0-3-1-305.ip.isnet.net [168.209.100.73]
11 68 ms * * core1a-bry-gi1-0-3.ip.isnet.net [168.209.100.194]
12 68 ms 68 ms 68 ms csw4-bry-vl2.ip.isnet.net [168.209.217.251]
13 68 ms 73 ms 70 ms csw3-bry-vl2.ip.isnet.net [168.209.217.250]
14 70 ms 69 ms 69 ms sw-osfw-shared-2-bry-gi1-0-24.ip.isnet.net [196.38.255.145]
15 68 ms 68 ms 67 ms 196.37.113.28
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * 2042 ms * vl105.cr.gw.cpt.za.wa.co.za [196.220.59.250]
26 * 46 ms * vl35.er.gw.cpt.za.wa.co.za [41.185.0.38]
27 * * * Request timed out.
28 * * * Request timed out.
29 46 ms * * 196.43.39.62
30 * * * Request timed out.

Trace complete.


Tracing route to www.mweb.co.za [196.2.63.110]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.254
2 * * * Request timed out.
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 46 ms 45 ms 46 ms tiscali-gw.telkom-ipnet.co.za [196.25.55.178]
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.
 
M

Mr.Jax

Expert Member
Joined
Sep 22, 2009
Messages
1,461
Still going strong even this morning.


TELKOM INTERNET SHAPED:
Tracing route to www.mybroadband.co.za [41.203.21.137]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 254 ms 254 ms 230 ms 196.43.11.202
4 127 ms 125 ms 122 ms 196.43.25.138
5 152 ms * 98 ms ge0-2.br1.jnb6.za.mtnbusiness.net [196.30.16.181]
6 160 ms 176 ms 170 ms 196.30.1.21
7 36 ms 37 ms 36 ms vlan9.hr3.jnb6.za.mtnbusiness.net [196.30.156.136]
8 117 ms 126 ms 146 ms 196.30.213.108
9 147 ms 154 ms 167 ms firewall1.jnb2.host-h.net [196.7.216.173]
10 242 ms 212 ms 153 ms mybroadband.co.za [41.203.21.137]

Trace complete.

OpenWeb(IS) Unshaped
Tracing route to www.mybroadband.co.za [41.203.21.137]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 91 ms 124 ms 120 ms cdsl2-rba-vl2663.ip.isnet.net [196.38.73.25]
4 119 ms 112 ms 128 ms cdsl2-rba-vl150.ip.isnet.net [196.38.73.9]
5 124 ms 129 ms 141 ms 168.209.1.140
6 230 ms 305 ms 262 ms 168.209.1.179
7 238 ms 239 ms 262 ms ge0-1.br1.jnb7.za.mtnbusiness.net [196.30.228.241]
8 100 ms 90 ms 74 ms ge0-1.cr1.jnb7.za.mtnbusiness.net [196.30.228.122]
9 41 ms 42 ms 34 ms ge11-0-0.gw2.jnb6.za.mtnbusiness.net [196.30.1.22]
10 161 ms 172 ms 174 ms vlan9.hr3.jnb6.za.mtnbusiness.net [196.30.156.136]
11 234 ms 211 ms 211 ms 196.30.213.108
12 183 ms 203 ms 179 ms firewall1.jnb2.host-h.net [196.7.216.173]
13 231 ms 225 ms 238 ms mybroadband.co.za [41.203.21.137]

Trace complete.
 
Last edited:
ichigo

ichigo

Executive Member
Joined
Aug 1, 2006
Messages
9,252
remind me to not move to your area, btw how long has your guys internet been broken now?
 
M

Mr.Jax

Expert Member
Joined
Sep 22, 2009
Messages
1,461
For me its been a year and a half of regular poor latency, but because its only one guy screaming about it (until now that is), nothing gets done about it.
 
J

jellievis

Senior Member
Joined
May 2, 2007
Messages
504
Mr Jax,

I really want to help, but the technical knowledge lacks seriously so you'll have to guide me. This has been my problem thus far and I cannot do a traceroute without the timeouts. Something else must be wrong?

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

C:\>tracert mybroadband.co.za

Tracing route to mybroadband.co.za [41.203.21.137]
over a maximum of 30 hops:

1 2 ms 1 ms 1 ms home.gateway [192.168.1.254]
2 * * * Request timed out.
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 65 ms 65 ms 66 ms mybroadband.co.za [41.203.21.137]

Trace complete.

You can see my speedtest in post #32 and that tells my story...
 
M

Mr.Jax

Expert Member
Joined
Sep 22, 2009
Messages
1,461
Those timeouts are probably because the ISP you're using is blocking specific ICMP packets, I'm also not specifically clued up to be sure.
Best way to assist would be to ping the home page of your isp continuously.
It will be better if you can ping your internet connection's default gateway (since its the first computer on "the other side"), that ip address will (should) be viewable inside your router, using it's web interface.

You can use Ping Plotter standard edition (expires after 30 days)
http://www.pingplotter.com/downloads/pngplt_std.exe

...to ping the site for a long period.

Once done, you can export the results to an image.
 
M

Mr.Jax

Expert Member
Joined
Sep 22, 2009
Messages
1,461
Eish...still going stroooooonngggg! The Telkom next generation network thats broken more than its working....eish!
C:\Users\......>ping -t 41.240.188.1

Pinging 41.240.188.1 with 32 bytes of data:
Reply from 41.240.188.1: bytes=32 time=148ms TTL=254
Reply from 41.240.188.1: bytes=32 time=126ms TTL=254
Reply from 41.240.188.1: bytes=32 time=80ms TTL=254
Reply from 41.240.188.1: bytes=32 time=101ms TTL=254
Reply from 41.240.188.1: bytes=32 time=84ms TTL=254
Reply from 41.240.188.1: bytes=32 time=105ms TTL=254
Reply from 41.240.188.1: bytes=32 time=90ms TTL=254
Request timed out.
Reply from 41.240.188.1: bytes=32 time=18ms TTL=254
Reply from 41.240.188.1: bytes=32 time=106ms TTL=254
Reply from 41.240.188.1: bytes=32 time=71ms TTL=254
Reply from 41.240.188.1: bytes=32 time=72ms TTL=254
Reply from 41.240.188.1: bytes=32 time=112ms TTL=254
Reply from 41.240.188.1: bytes=32 time=82ms TTL=254
Reply from 41.240.188.1: bytes=32 time=189ms TTL=254
Reply from 41.240.188.1: bytes=32 time=90ms TTL=254
Reply from 41.240.188.1: bytes=32 time=115ms TTL=254
Reply from 41.240.188.1: bytes=32 time=189ms TTL=254
Reply from 41.240.188.1: bytes=32 time=173ms TTL=254
Reply from 41.240.188.1: bytes=32 time=169ms TTL=254
Reply from 41.240.188.1: bytes=32 time=80ms TTL=254
Reply from 41.240.188.1: bytes=32 time=87ms TTL=254
Reply from 41.240.188.1: bytes=32 time=83ms TTL=254
Reply from 41.240.188.1: bytes=32 time=125ms TTL=254
Reply from 41.240.188.1: bytes=32 time=41ms TTL=254
Reply from 41.240.188.1: bytes=32 time=140ms TTL=254
Reply from 41.240.188.1: bytes=32 time=107ms TTL=254
Reply from 41.240.188.1: bytes=32 time=63ms TTL=254
Reply from 41.240.188.1: bytes=32 time=95ms TTL=254
Reply from 41.240.188.1: bytes=32 time=63ms TTL=254
Reply from 41.240.188.1: bytes=32 time=125ms TTL=254
Reply from 41.240.188.1: bytes=32 time=88ms TTL=254
Reply from 41.240.188.1: bytes=32 time=88ms TTL=254
Reply from 41.240.188.1: bytes=32 time=71ms TTL=254
Reply from 41.240.188.1: bytes=32 time=96ms TTL=254
Reply from 41.240.188.1: bytes=32 time=131ms TTL=254
Reply from 41.240.188.1: bytes=32 time=48ms TTL=254
Reply from 41.240.188.1: bytes=32 time=53ms TTL=254
Reply from 41.240.188.1: bytes=32 time=64ms TTL=254
Request timed out.
Reply from 41.240.188.1: bytes=32 time=82ms TTL=254
Reply from 41.240.188.1: bytes=32 time=103ms TTL=254
Reply from 41.240.188.1: bytes=32 time=26ms TTL=254
Reply from 41.240.188.1: bytes=32 time=114ms TTL=254
Reply from 41.240.188.1: bytes=32 time=72ms TTL=254
Reply from 41.240.188.1: bytes=32 time=119ms TTL=254
Reply from 41.240.188.1: bytes=32 time=74ms TTL=254
Reply from 41.240.188.1: bytes=32 time=124ms TTL=254
Reply from 41.240.188.1: bytes=32 time=53ms TTL=254
Request timed out.
Reply from 41.240.188.1: bytes=32 time=101ms TTL=254
Reply from 41.240.188.1: bytes=32 time=113ms TTL=254
Reply from 41.240.188.1: bytes=32 time=105ms TTL=254
Reply from 41.240.188.1: bytes=32 time=75ms TTL=254

Ping statistics for 41.240.188.1:
Packets: Sent = 54, Received = 51, Lost = 3 (5% loss),
Approximate round trip times in milli-seconds:
Minimum = 18ms, Maximum = 189ms, Average = 96ms
 
M

Mr.Jax

Expert Member
Joined
Sep 22, 2009
Messages
1,461
....
C:\Users\......>PING -t 41.240.188.1

Pinging 41.240.188.1 with 32 bytes of data:
Reply from 41.240.188.1: bytes=32 time=113ms TTL=254
Reply from 41.240.188.1: bytes=32 time=22ms TTL=254
Reply from 41.240.188.1: bytes=32 time=92ms TTL=254
Reply from 41.240.188.1: bytes=32 time=82ms TTL=254
Reply from 41.240.188.1: bytes=32 time=145ms TTL=254
Reply from 41.240.188.1: bytes=32 time=107ms TTL=254
Reply from 41.240.188.1: bytes=32 time=133ms TTL=254
Reply from 41.240.188.1: bytes=32 time=160ms TTL=254
Reply from 41.240.188.1: bytes=32 time=98ms TTL=254
Reply from 41.240.188.1: bytes=32 time=146ms TTL=254
Reply from 41.240.188.1: bytes=32 time=95ms TTL=254
Reply from 41.240.188.1: bytes=32 time=97ms TTL=254
Reply from 41.240.188.1: bytes=32 time=104ms TTL=254
Reply from 41.240.188.1: bytes=32 time=160ms TTL=254
Reply from 41.240.188.1: bytes=32 time=160ms TTL=254
Reply from 41.240.188.1: bytes=32 time=155ms TTL=254
Reply from 41.240.188.1: bytes=32 time=135ms TTL=254
Reply from 41.240.188.1: bytes=32 time=103ms TTL=254
Request timed out.
Reply from 41.240.188.1: bytes=32 time=62ms TTL=254
Reply from 41.240.188.1: bytes=32 time=48ms TTL=254
Reply from 41.240.188.1: bytes=32 time=143ms TTL=254
Reply from 41.240.188.1: bytes=32 time=138ms TTL=254
Reply from 41.240.188.1: bytes=32 time=95ms TTL=254
Reply from 41.240.188.1: bytes=32 time=149ms TTL=254
Reply from 41.240.188.1: bytes=32 time=181ms TTL=254
Reply from 41.240.188.1: bytes=32 time=109ms TTL=254
Reply from 41.240.188.1: bytes=32 time=123ms TTL=254
Reply from 41.240.188.1: bytes=32 time=103ms TTL=254
Reply from 41.240.188.1: bytes=32 time=145ms TTL=254
Reply from 41.240.188.1: bytes=32 time=174ms TTL=254
Reply from 41.240.188.1: bytes=32 time=171ms TTL=254
Reply from 41.240.188.1: bytes=32 time=177ms TTL=254
Reply from 41.240.188.1: bytes=32 time=107ms TTL=254
Reply from 41.240.188.1: bytes=32 time=138ms TTL=254
Reply from 41.240.188.1: bytes=32 time=198ms TTL=254
Reply from 41.240.188.1: bytes=32 time=200ms TTL=254
Reply from 41.240.188.1: bytes=32 time=117ms TTL=254
Reply from 41.240.188.1: bytes=32 time=58ms TTL=254
Reply from 41.240.188.1: bytes=32 time=203ms TTL=254
Reply from 41.240.188.1: bytes=32 time=205ms TTL=254
Reply from 41.240.188.1: bytes=32 time=103ms TTL=254
Reply from 41.240.188.1: bytes=32 time=165ms TTL=254
Reply from 41.240.188.1: bytes=32 time=183ms TTL=254
Reply from 41.240.188.1: bytes=32 time=114ms TTL=254
Reply from 41.240.188.1: bytes=32 time=165ms TTL=254
Reply from 41.240.188.1: bytes=32 time=209ms TTL=254
Reply from 41.240.188.1: bytes=32 time=161ms TTL=254
Reply from 41.240.188.1: bytes=32 time=117ms TTL=254
Reply from 41.240.188.1: bytes=32 time=217ms TTL=254
Reply from 41.240.188.1: bytes=32 time=233ms TTL=254

Ping statistics for 41.240.188.1:
Packets: Sent = 51, Received = 50, Lost = 1 (1% loss),
Approximate round trip times in milli-seconds:
Minimum = 22ms, Maximum = 233ms, Average = 136ms
 
You must log in or register to reply here.
Top