1kbs speed on 4meg line

S

Shuyin

Active Member
Joined
Dec 5, 2010
Messages
55
Reaction score
0
My Internet connection has been basicly non exisitant for the past 3 weeks we have phoned mweb they claim everything is ok on there side.

We phone Telkom to send round a technition and they say they will send one out the next day and then we get a SMS! saying the Problem has been resolved ??? how the bloody hell do they know its resovled if they have not phoned back and asked for feedback. (and no its not resolved at all)

This has been going on for 3 weeks now frankly im tired of it.

See Screenshot for awsome proof!:D

HTML: 
http://i52.tinypic.com/2cqb0yg.jpg

On that site i average about 150kbs but now as u can see its 1kbs or 1000 bytes.
 
Last edited:
Have you tried another ISP or only an MWEB account?
 
Are you using a download manager or do you always download the default way (your screenshot)?
A download manager will help you get the maximum the line can do at any time (in the screenshot example perhaps 2-4 kB/s:D).
 
cpu. said:
Are you using a download manager or do you always download the default way (your screenshot)?
A download manager will help you get the maximum the line can do at any time (in the screenshot example perhaps 2-4 kB/s:D).
Click to expand...

Thats not even funny or the issue at hand :mad: p2p was like 450kbs now its 0kbs
 
medraught said:
I'm having similar (though not as extreme) issues. In the interesting of comparing apples with apples, please could you run the following for me and post the results:

Start -> Run -> cmd.exe

ping www.google.com
tracert www.google.com
pathping www.google.com

Thanks.
Click to expand...

Pinging www.l.google.com [209.85.143.104] with 32 bytes of data:

Reply from 209.85.143.104: bytes=32 time=318ms TTL=52
Reply from 209.85.143.104: bytes=32 time=313ms TTL=52
Reply from 209.85.143.104: bytes=32 time=344ms TTL=52
Reply from 209.85.143.104: bytes=32 time=337ms TTL=52

Ping statistics for 209.85.143.104:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 313ms, Maximum = 344ms, Average = 328ms
--------------------------------------------------------------------------

Tracing route to www.l.google.com [209.85.143.99]
over a maximum of 30 hops:

1 39 ms 38 ms 41 ms 41-132-20-1.dsl.mweb.co.za [41.132.20.1]
2 70 ms 76 ms 75 ms tengig-0-0-0-107.vic-ipc-1.mweb.co.za [196.29.158]
3 22 ms 23 ms 24 ms vl-92.vic-hscore-2.mweb.co.za [196.22.189.3]
4 64 ms 39 ms 39 ms tengig-0-0-0-0-12.vic-up-1.mweb.co.za [196.29.241]
5 41 ms 41 ms 53 ms tengig-0-0-0-0-41.vic-up-2.mweb.co.za [196.29.210]
6 289 ms 318 ms 318 ms pos-0-0-0-0.lon-1.mweb.co.za [196.22.163.230]
7 329 ms 334 ms 329 ms 195.66.226.125
8 303 ms 308 ms 311 ms 209.85.252.76
9 305 ms 319 ms 314 ms 209.85.251.190
10 328 ms 316 ms 308 ms 209.85.253.125
11 328 ms 337 ms 283 ms 216.239.47.26
12 329 ms 319 ms 341 ms dy-in-f99.1e100.net [209.85.143.99]

Trace complete.

------------------------------------------------------------------------

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Ghostalker>pathping www.google.com

Tracing route to www.l.google.com [209.85.143.104]
over a maximum of 30 hops:
0 sacredshard [41.132.234.37]
1 41-132-20-1.dsl.mweb.co.za [41.132.20.1]
2 * tengig-0-0-0-110.vic-ipc-1.mweb.co.za [196.22.169.170]
3 vl-92.vic-hscore-1.mweb.co.za [196.22.189.2]
4 tengig-0-0-0-0-11.vic-up-1.mweb.co.za [196.22.169.225]
5 196.22.169.94
6 pos-0-0-0-0.lon-1.mweb.co.za [196.22.163.230]
7 195.66.224.125
8 64.233.175.25
9 209.85.251.190
10 209.85.253.125
11 216.239.47.38
12 dy-in-f104.1e100.net [209.85.143.104]

Computing statistics for 300 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 sacredshard [41.132.234.37]
4/ 100 = 4% |
1 59ms 9/ 100 = 9% 5/ 100 = 5% 41-132-20-1.dsl.mweb.co.za [41.132.20.1]
0/ 100 = 0% |
2 58ms 9/ 100 = 9% 5/ 100 = 5% tengig-0-0-0-110.vic-ipc-1.mweb.co.za [196.22.169.170]
0/ 100 = 0% |
3 59ms 7/ 100 = 7% 3/ 100 = 3% vl-92.vic-hscore-1.mweb.co.za [196.22.189.2]
0/ 100 = 0% |
4 58ms 4/ 100 = 4% 0/ 100 = 0% tengig-0-0-0-0-11.vic-up-1.mweb.co.za [196.22.169.225]
1/ 100 = 1% |
5 60ms 5/ 100 = 5% 0/ 100 = 0% 196.22.169.94
1/ 100 = 1% |
6 314ms 9/ 100 = 9% 3/ 100 = 3% pos-0-0-0-0.lon-1.mweb.co.za [196.22.163.230]
0/ 100 = 0% |
7 316ms 6/ 100 = 6% 0/ 100 = 0% 195.66.224.125
0/ 100 = 0% |
8 288ms 13/ 100 = 13% 7/ 100 = 7% 64.233.175.25
0/ 100 = 0% |
9 302ms 8/ 100 = 8% 2/ 100 = 2% 209.85.251.190
0/ 100 = 0% |
10 313ms 6/ 100 = 6% 0/ 100 = 0% 209.85.253.125
1/ 100 = 1% |
11 309ms 7/ 100 = 7% 0/ 100 = 0% 216.239.47.38
2/ 100 = 2% |
12 329ms 9/ 100 = 9% 0/ 100 = 0% dy-in-f104.1e100.net [209.85.143.104]

Trace complete.

This looks normal to me well not 100% but normal how do i tell of my equipment is damage like router or adls filter i dont have spares :(
 
Everything up until the pathping looks well... ok-ish.

The pathping however, seems to indicate packet loss, so I think that is the first thing you need to sort out. What worries me is that the loss seems to happen from the first hop (ie. your PC, sacredshard), so what I would do is check your cabling if possible (or wireless signal strength if you are connecting to the router wirelessly). A bad connection from the start is just going to get worse further down the line.

To compare, here is mine as of 2 minutes ago:

pathping www.google.com

Tracing route to www.l.google.com [196.23.168.147] over a maximum of 30 hops:
0 Fenris.home.gateway [192.168.1.2]
1 192.168.1.254
2 dsl-242-144-01.telkomadsl.co.za [41.242.144.1]
3 196.38.73.113
4 cdsl2-rba-vl150.ip.isnet.net [196.38.73.9]
5 core6a-rba-gi0-0-0.ip.isnet.net [196.26.0.43]
6 csw4-pkl-gi1-1.ip.isnet.net [196.26.0.101]
7 za196-23-168-147.cache.googlevideo.com [196.23.168.147]

Computing statistics for 175 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Fenris.home.gateway [192.168.1.2] 0/ 100 = 0% |
1 3ms 0/ 100 = 0% 0/ 100 = 0% 192.168.1.254 0/ 100 = 0% |
2 --- 100/ 100 =100% 100/ 100 =100% dsl-242-144-01.telkomadsl.co.za [41.242.144.1] 0/ 100 = 0% |
3 24ms 0/ 100 = 0% 0/ 100 = 0% 196.38.73.113 0/ 100 = 0% |
4 20ms 1/ 100 = 1% 1/ 100 = 1% cdsl2-rba-vl150.ip.isnet.net [196.38.73.9] 0/ 100 = 0% |
5 18ms 0/ 100 = 0% 0/ 100 = 0% core6a-rba-gi0-0-0.ip.isnet.net [196.26.0.43] 0/ 100 = 0% |
6 16ms 0/ 100 = 0% 0/ 100 = 0% csw4-pkl-gi1-1.ip.isnet.net [196.26.0.101] 0/ 100 = 0% |
7 18ms 0/ 100 = 0% 0/ 100 = 0% za196-23-168-147.cache.googlevideo.com [196.23.168.147]

Trace complete.

Ideally you don't want any packet loss. The ones marked as 100% are probably due to firewalling or access list's not allowing ICMP so don't stress about those.
 
medraught said:
Everything up until the pathping looks well... ok-ish.
Click to expand...

So i understand that bad cables can be the cause ... the problem is the same on the other 3 Computers could a damaged Router/adls Filter cause packet loss ? and also make a 4meg line thats ment to download at about 450kbs now download at 1kbs ? .... At 3pm tomorow some techie from telkom dls is going to phone us... i doubt it will get sorted out.

it took like about 10 minutes to open Google image search lol .... Normal google works fine but when i click on image tab it hangs for 10 minutes :P:wtf:
 
To be honest, in a case like yours, I would try to borrow a friend's router and plug it on and do a comparison. If the issue clears up, it may have been the router. If not, get them to check the junction boxes in the house and leading onto the property. I can't explain your issues but I can suggest a course of action to try and eliminate possibilities.
 
medraught said:
To be honest, in a case like yours, I would try to borrow a friend's router and plug it on and do a comparison. If the issue clears up, it may have been the router. If not, get them to check the junction boxes in the house and leading onto the property. I can't explain your issues but I can suggest a course of action to try and eliminate possibilities.
Click to expand...


I have now tested a new router and its still the same I have also tested my line on Webafrica .... so it is 100% telkoms issue they need to come out and repair the line. but they just keep saying that the issue has been resolved and wont send one out.
 
Time to escalate to supervisors, etc? I can only hope that the few decent and friendly Telkom staff that I know lurk around the forums notice this post and can help.
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X