Weird ADSL Issue

Abe

Expert Member
Joined
Jul 30, 2005
Messages
4,610
Reaction score
1
Location
Up the creek without a GB
Our ADSL line has been unstable for a while now. We get continuous packet losses. I was busy checking things out the other night and noticed a pattern. I was doing a repeated ping to our ISP and every minute (to the second) we would see a huge degradation. Most times it would lose a packet of the ping but on the odd occasion it would respond with a time of 1500+ ms. Does anyone have any ideas as to what could cause this sort of problem? It's a lot worse during the day but the regularity of the loss during that test run makes me wonder what on earth is going on. Telkom have not been much help and they keep ignoring the problems.
 
Try dropping your MTU settings.

How on earth do I do this? I have a billion 7402 and tried 1454 and 1472 and neither work. It just ignores my setting and goes back to 1492.

Edit - Scratch that, you have to disconnect first. Got it working on 1454. Will see how it works now. Thanks.
 
Last edited:
i am no expert, but i have twice had a similr problem which was finally resolved by telkom finding the cable being waterlogged (but that was in the rainy season)

PS: it was no easy task to convince telkom to check / find the fault on the actual cable ... first time i threatened them (don't ask :twisted: ), the second time I KNEW what was wrong and told the rocket scientist / technician straight
 
i am no expert, but i have twice had a similr problem which was finally resolved by telkom finding the cable being waterlogged (but that was in the rainy season)

PS: it was no easy task to convince telkom to check / find the fault on the actual cable ... first time i threatened them (don't ask :twisted: ), the second time I KNEW what was wrong and told the rocket scientist / technician straight

Our problems started with some issue at the exchange that effected the whole area where we were completely down and it hasn't come right since then. Getting Telkom to do anything more than a cursory glance is an absolute nightmare.

What makes it really strange is that the problem on the line repeats every minute to the second.

e.g.

Reply from 196.220.58.66: bytes=32 time=44ms TTL=121
Request timed out.
Reply from 196.220.58.66: bytes=32 time=46ms TTL=121
...
Reply from 196.220.58.66: bytes=32 time=46ms TTL=121
Reply from 196.220.58.66: bytes=32 time=1264ms TTL=121
Reply from 196.220.58.66: bytes=32 time=43ms TTL=121
...
Reply from 196.220.58.66: bytes=32 time=47ms TTL=121
Reply from 196.220.58.66: bytes=32 time=905ms TTL=121
Reply from 196.220.58.66: bytes=32 time=44ms TTL=121
...
Reply from 196.220.58.66: bytes=32 time=43ms TTL=121
Reply from 196.220.58.66: bytes=32 time=1805ms TTL=121
Reply from 196.220.58.66: bytes=32 time=42ms TTL=121
...
Reply from 196.220.58.66: bytes=32 time=47ms TTL=121
Reply from 196.220.58.66: bytes=32 time=904ms TTL=121
Reply from 196.220.58.66: bytes=32 time=44ms TTL=121

The spikes in bold occur only once and exactly on the minute. This is at night. During the day it occurs far more often.

On the MTU note, changing the MTU from 1492 to 1454 made a huge difference. Thank you. We only lost 9 packets out of 2962. We are still getting the ping spikes it's just that they are no longer timing out. Previously the majority were timing out with only a few spiking in place. What sort of value can we use for the MTU? Should I keep dropping it down until we no longer lose packets?
 
Last edited:
Exactly on the minute you say ?
Are you connecting to the router via WiFi ?

(I had this exact same problem and it turned out to be my WiFi network card. Replaced it and the problem went away.)
 
download this

http://support.uo.com/latency.html

Double-click on UOTRACE.EXE to run the program.
Click on OPTIONS, then ADVANCED.
Choose the server you wish to trace to from the drop-down list. (This is where you can also just enter the name of any site you want to use as a test endpoint.)
Click the TRACE ROUTE button. A succession of host names will begin to appear in the main window. These are the computers your data passes through on its way to the desired server. Once the function is complete, a message that says “Traceroute successful” will appear in the lower left corner of the window. If you get a message saying “Maximum number of hops exceeded” click on OPTIONS then SETTINGS and change the max hops to a higher number and re-trace.
Click the POLL button.
This tells the program to send multiple packets of data through the route to the final host. As the data is being sent, look at the PKTS R/S column. Let it send about 100 packets then select STOP POLL.
If you want to copy the results to post on a forum, click Copy in the Edit menu, then paste it where you want it to go.

When you are experiencing latency issues, you’ll probably see that your first few hops are fine, with very low round trip times, but then at some point you’ll hit a router that is responding much slower than the previous ones. You’ll probably notice that all the hops after this point have high latency. That hop, or the one just before it, is the problem. You can get this data to someone at your ISP, and if they can filter it up to their network department, they should be able to take a look into the problem.

If you see packet loss to every hop past a particular hop, the first hop with loss is probably the problem. (All packets to hops past the first one with loss have to pass through the one that is dropping packets.)
If you see packet loss pretty much from start to finish, it’s probably an issue with your cable/DSL modem, or possibly your connection itself.
 
Top
Sign up to the MyBroadband newsletter
X