Please help me troubleshoot an ADSL line problem... MWeb vs Telkom

B

BarnettE

Well-Known Member
Joined
Jul 27, 2008
Messages
192
Reaction score
13
Location
Table View, Cape Town
Lately I have been getting many web sites timing out or loading partially. I phoned MWeb and Telkom and both said that they see nothing wrong and insisted the problem must be with the other company. Telkom did however "reset the line" and after that I thought it was working fine. When I ping the nearest device on the other side of the ADSl line, the ping times were consistent and very close to 10ms:

Code: 
C:\>tracert www.mweb.co.za

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

  1     1 ms     1 ms    <1 ms  10.0.0.2
  [U]2     8 ms     9 ms     8 ms  41-133-130-1.dsl.mweb.co.za [41.133.130.1][/U]    <<<<<<<<<<<<<<<<<<<<<<<
  3    10 ms    10 ms    10 ms  te1-1-0.502.cpt-ipc-1.mweb.co.za [196.28.178.166]
  4    10 ms    10 ms    10 ms  197-84-2-2.cpt.mweb.co.za [197.84.2.2]
  5    10 ms     9 ms    10 ms  ^C

C:\>ping 41.133.130.1 -t

Pinging 41.133.130.1 with 32 bytes of data:
Reply from 41.133.130.1: bytes=32 time=10ms TTL=253
Reply from 41.133.130.1: bytes=32 time=10ms TTL=253
Reply from 41.133.130.1: bytes=32 time=10ms TTL=253
Reply from 41.133.130.1: bytes=32 time=10ms TTL=253
Reply from 41.133.130.1: bytes=32 time=9ms TTL=253
Reply from 41.133.130.1: bytes=32 time=10ms TTL=253
Reply from 41.133.130.1: bytes=32 time=10ms TTL=253
Reply from 41.133.130.1: bytes=32 time=10ms TTL=253
Reply from 41.133.130.1: bytes=32 time=11ms TTL=253
Reply from 41.133.130.1: bytes=32 time=10ms TTL=253
Reply from 41.133.130.1: bytes=32 time=10ms TTL=253
Reply from 41.133.130.1: bytes=32 time=10ms TTL=253
Reply from 41.133.130.1: bytes=32 time=11ms TTL=253
Reply from 41.133.130.1: bytes=32 time=10ms TTL=253
Reply from 41.133.130.1: bytes=32 time=10ms TTL=253
Reply from 41.133.130.1: bytes=32 time=10ms TTL=253
Reply from 41.133.130.1: bytes=32 time=10ms TTL=253
Reply from 41.133.130.1: bytes=32 time=11ms TTL=253
Reply from 41.133.130.1: bytes=32 time=10ms TTL=253
Reply from 41.133.130.1: bytes=32 time=10ms TTL=253
Reply from 41.133.130.1: bytes=32 time=11ms TTL=253
Reply from 41.133.130.1: bytes=32 time=10ms TTL=253

But that did not last very long. This is what I am getting for the last few days:

Code: 
C:\>ping 41.133.130.1 -t

Pinging 41.133.130.1 with 32 bytes of data:
Reply from 41.133.130.1: bytes=32 time=38ms TTL=253
Reply from 41.133.130.1: bytes=32 time=53ms TTL=253
Reply from 41.133.130.1: bytes=32 time=35ms TTL=253
Reply from 41.133.130.1: bytes=32 time=44ms TTL=253
Reply from 41.133.130.1: bytes=32 time=34ms TTL=253
Reply from 41.133.130.1: bytes=32 time=10ms TTL=253
Reply from 41.133.130.1: bytes=32 time=21ms TTL=253
Reply from 41.133.130.1: bytes=32 time=43ms TTL=253
Reply from 41.133.130.1: bytes=32 time=61ms TTL=253
Reply from 41.133.130.1: bytes=32 time=44ms TTL=253
Reply from 41.133.130.1: bytes=32 time=11ms TTL=253
Reply from 41.133.130.1: bytes=32 time=10ms TTL=253
Reply from 41.133.130.1: bytes=32 time=53ms TTL=253
Reply from 41.133.130.1: bytes=32 time=50ms TTL=253
Reply from 41.133.130.1: bytes=32 time=12ms TTL=253
Reply from 41.133.130.1: bytes=32 time=28ms TTL=253
Reply from 41.133.130.1: bytes=32 time=41ms TTL=253
Reply from 41.133.130.1: bytes=32 time=10ms TTL=253
Reply from 41.133.130.1: bytes=32 time=10ms TTL=253
Reply from 41.133.130.1: bytes=32 time=13ms TTL=253
Reply from 41.133.130.1: bytes=32 time=10ms TTL=253
Reply from 41.133.130.1: bytes=32 time=13ms TTL=253
Reply from 41.133.130.1: bytes=32 time=22ms TTL=253
Reply from 41.133.130.1: bytes=32 time=10ms TTL=253
Reply from 41.133.130.1: bytes=32 time=51ms TTL=253
Reply from 41.133.130.1: bytes=32 time=57ms TTL=253
Reply from 41.133.130.1: bytes=32 time=39ms TTL=253
Reply from 41.133.130.1: bytes=32 time=54ms TTL=253
Reply from 41.133.130.1: bytes=32 time=57ms TTL=253
Reply from 41.133.130.1: bytes=32 time=11ms TTL=253
Reply from 41.133.130.1: bytes=32 time=20ms TTL=253

Any ideas what the problem can be? What other tests can I do?
 
Traceroutes would be a lot more helpful in pin pointing the problem.
 
Qwikslver said:
Traceroutes would be a lot more helpful in pin pointing the problem.
Click to expand...

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

  1    <1 ms     1 ms     1 ms  10.0.0.2
  2     8 ms    38 ms     8 ms  41-133-130-1.dsl.mweb.co.za [41.133.130.1]
  3    10 ms    56 ms    38 ms  te1-1-0.502.cpt-ipc-1.mweb.co.za [196.28.178.166]
  4    45 ms    41 ms    53 ms  197-84-2-2.cpt.mweb.co.za [197.84.2.2]
  5    21 ms    10 ms    13 ms  196.28.178.66
  6    61 ms    75 ms    34 ms  cte-core-sw2.vwol.net [196.41.144.35]
  7    28 ms    24 ms    33 ms  www.mweb.co.za [196.2.63.110]

Trace complete.

EDIT - A few more.
As you can see, one moment it is fine, the next it is not:
Code: 
Tracing route to www.mweb.co.za [196.2.63.110]
over a maximum of 30 hops:

  1     1 ms     1 ms    <1 ms  10.0.0.2
  2    11 ms    11 ms    13 ms  41-133-130-1.dsl.mweb.co.za [41.133.130.1]
  3     9 ms     9 ms    10 ms  te1-1-0.502.cpt-ipc-1.mweb.co.za [196.28.178.166]
  4    24 ms    24 ms    23 ms  197-84-2-2.cpt.mweb.co.za [197.84.2.2]
  5    10 ms    10 ms    11 ms  196.28.178.66
  6    12 ms    10 ms    11 ms  cte-core-sw2.vwol.net [196.41.144.35]
  7   708 ms    53 ms    21 ms  www.mweb.co.za [196.2.63.110]

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  10.0.0.2
  2     8 ms     8 ms     8 ms  41-133-130-1.dsl.mweb.co.za [41.133.130.1]
  3    10 ms    10 ms    10 ms  te1-1-0.502.cpt-ipc-1.mweb.co.za [196.28.178.166]
  4    10 ms    10 ms    10 ms  197-84-2-2.cpt.mweb.co.za [197.84.2.2]
  5     9 ms    10 ms    10 ms  196.28.178.66
  6    11 ms     9 ms    10 ms  cte-core-sw2.vwol.net [196.41.144.35]
  7    12 ms    11 ms    10 ms  www.mweb.co.za [196.2.63.110]

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  10.0.0.2
  2    24 ms    26 ms    25 ms  41-133-130-1.dsl.mweb.co.za [41.133.130.1]
  3    71 ms    64 ms    56 ms  te1-1-0.502.cpt-ipc-1.mweb.co.za [196.28.178.166]
  4    74 ms    79 ms    80 ms  197-84-2-2.cpt.mweb.co.za [197.84.2.2]
  5    49 ms    42 ms    38 ms  196.28.178.66
  6    10 ms    10 ms     9 ms  cte-core-sw2.vwol.net [196.41.144.35]
  7    11 ms    10 ms    10 ms  www.mweb.co.za [196.2.63.110]

Trace complete.

PS: I made sure that the line was idle during these tests. I closed all programs and was watching the modem lights.
 
Last edited:
AcidRaZor said:
websites timing out with a ping of 40ms?

PEBCAC
Click to expand...

Are you saying that what I am getting is normal? Is it normal for to see consistent 9-11ms pings one moment, and 10-100ms the next?

The ping results I posted above is how it is right now. Some times it is gets worse with perhaps 10% packet loss. Web sites timing out is not always, it only happens at times. I noticed that it gets exponentially worse when more than one person tries to use the internet at the same time. Some times it becomes almost impossible to access the web, with even DNS lookups failing, and I have to click refresh several times to get a page to load.
 
Maybe take a look at your Line Attenuation and SNR stats?

For a time I had an issue where I was getting time outs a lot, and then eventually it got worse and I'd lose sync every few hours. My stats were getting worse by the day. It turned out some flooding during a rainy period messed with one of the lines between my suburb and town(the exchange), and they dug it up, repaired it, and my line stats went right back to being excellent.
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X