Strange DSL issue Telkom doesn't know

funkmail

funkmail

Active Member
Joined
Aug 23, 2010
Messages
77
Reaction score
0
Location
Johannesburg
Hi All,

I really need some help with this, I am having the strangest issue with my dsl, I have a 384 dsl and Mweb's uncapped offering. I have a Billion 800VGT router and have configured it correctly, I have disabled all firewalls and any port blocking as well as given myself priority on the connection out. I have no downloads running in the background either. My issue is that I have high latency on my line when I ping a local server it pings at +/- 400 ms, I know I should be getting around 60-90 ms. The servers I am pinging are co.za & www.saix.net, when I do a trace on the second hop it jumps to 400ms. The line Attenuation is fine according to the Telkom technician 27dBi. When I do have downloads running it runs the correct download speed, if I ping with 32b or 384b it reply's at the same latency. I don't know what the problem could be and any help with this would be great.

Thank you,
 
I have a very similar set up to you, just with a Vox phone as my router. My ping times to saix.net are around 40ms (over 4 hops) - though if I let it run for a few minutes it does vary quite a bit, up to around 200ms at one point.

Try downloading the freeware version of PingPlotter to see where the bottleneck is. (Or a tracert from the command line will do a similar job).
 
funkmail said:
Hi All,

I really need some help with this, I am having the strangest issue with my dsl, I have a 384 dsl and Mweb's uncapped offering. I have a Billion 800VGT router and have configured it correctly, I have disabled all firewalls and any port blocking as well as given myself priority on the connection out. I have no downloads running in the background either. My issue is that I have high latency on my line when I ping a local server it pings at +/- 400 ms, I know I should be getting around 60-90 ms. The servers I am pinging are co.za & www.saix.net, when I do a trace on the second hop it jumps to 400ms. The line Attenuation is fine according to the Telkom technician 27dBi. When I do have downloads running it runs the correct download speed, if I ping with 32b or 384b it reply's at the same latency. I don't know what the problem could be and any help with this would be great.

Thank you,
Click to expand...

What DNS are u using ?
 
@brettwlewis:

When I tracert from command my first hop to the router is <1ms the second hop to the dslam/exchange is 400ms and all other hops beyond that are also above 400ms I will link it when I get home from work.

@Ice2Cool

My router is configured to auto assign the dns, but if I use the Mweb dns I can't browse anything. The dns's for Mweb that I tried are 196.28.80.140 prim & 196.28.80.139 Secondary

Thank you
 
20-08-2010 06:18 PM #38
ShadowRider

* View Profile
* View Forum Posts
* Private Message
* View Blog Entries
* Visit Homepage
* View Articles
* Add as Contact

ShadowRider is offline
Active Member

Join Date
Mar 2009
Posts
88

Unhappy You think thats bad: Waterford Exchange :(

Same problem: On JHB Waterford Exchange 011 658.
(I am with webAfrica and I have a 4Mb line. I have tried 2 other accounts from IS to Mweb)

Tracert: to wa.co.za

Tracing route to wa.co.za [196.220.63.42]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 453 ms 419 ms 394 ms dsl-185-69-1.dynamic.wa.co.za [41.185.69.1]
3 463 ms 497 ms * vl108.cr.gw.cpt.za.wa.co.za [196.220.59.238]
4 399 ms 329 ms 362 ms vl36.er.gw.cpt.za.wa.co.za [41.185.0.66]
5 487 ms 478 ms 373 ms vl38.cr.gw.cpt.za.wa.co.za [41.185.0.73]
6 375 ms 445 ms 489 ms fe0.er1.gw.cpt.za.wadns.net [41.185.0.4]
7 220 ms 286 ms 290 ms wa-acc1.wadns.net [196.220.39.253]
8 460 ms 488 ms 436 ms 196.220.63.42

Trace complete.
Routers stats are: Which are good. (I am exactly 1.35KM from my exchange)
Line Attenuation 23.1 db 13.0 db
Noise Margin 26.0 db 18.0 db

I can upload about 50MB in the time it takes me to download about 3-5MB

I have had this problem for 4 weeks, since I got my 4Mb line.
And Telkom just does not get it, they have no-clue what ping, latency or contention-ratios are
I have also had 2 Techs at my house telling me what I already know.

Speed test: http://www.speedtest.net/result/921801841.png

Problem is I am sick of 3Gs ridiculous caps and I will never go back to NeoFail.
So what can I do, I can't pay +R400 p/m for a slow ISDN line

Last edited by ShadowRider; 20-08-2010 at 06:19 PM. Reason: You think thats bad: Waterford Exchange :(

I am here! | ..::Jesar|Arts::..
The rest of the universe is out there | Somewhere...

This looks like the same issue as I am on that same exchange.
 
@Merenwenrago

Telkom technicians were at my house yesterday afternoon trying to resolve the issue, they have put me on a whole new card & port on the exchange and the card they have put me on is not even close to full so I don't think it's a contention ratio issue (obviously assuming I wasn't lied to ). And I don't think it's that the exchange needs an upgrade as the technicians I have spoken to have said that the Waterford exchange has been upgraded recently to accommodate the 10Mb/s infrastructure. So I really dunno?
 
2 453 ms 419 ms 394 ms dsl-185-69-1.dynamic.wa.co.za [41.185.69.1] well this is where problem is and thats dslam/exchange

if they really changed it to another card and port
post another tracert to check if they not lying
 
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Scavenger>tracert www.saix.net

Tracing route to www.saix.net [196.25.1.200]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms home.gateway [192.168.8.3]
2 345 ms 399 ms 367 ms 41-132-10-1.dsl.mweb.co.za [41.132.10.1]
3 347 ms 340 ms 392 ms tengig-0-0-0-110.vic-ipc-1.mweb.co.za [196.22.16
9.170]
4 444 ms 447 ms 429 ms vl-92.vic-hscore-1.mweb.co.za [196.22.189.2]
5 467 ms 392 ms 394 ms tengig-0-0-0-0-11.vic-up-1.mweb.co.za [196.22.16
9.225]
6 407 ms 393 ms 366 ms rrba-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.8.
249]
7 452 ms 448 ms 500 ms wblv-ip-essr-1-atm-2-0-0-2.telkom-ipnet.co.za [1
96.43.11.30]
8 252 ms 259 ms 264 ms wblv-ip-www-1.saix.net [196.25.1.200]

Trace complete.

C:\Users\Scavenger>

This is my trace to www.saix.net

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

C:\Users\Scavenger>tracert www.saix.net

Tracing route to www.saix.net [196.25.1.200]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms home.gateway [192.168.8.3]
2 345 ms 399 ms 367 ms 41-132-10-1.dsl.mweb.co.za [41.132.10.1]
3 347 ms 340 ms 392 ms tengig-0-0-0-110.vic-ipc-1.mweb.co.za [196.22.16
9.170]
4 444 ms 447 ms 429 ms vl-92.vic-hscore-1.mweb.co.za [196.22.189.2]
5 467 ms 392 ms 394 ms tengig-0-0-0-0-11.vic-up-1.mweb.co.za [196.22.16
9.225]
6 407 ms 393 ms 366 ms rrba-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.8.
249]
7 452 ms 448 ms 500 ms wblv-ip-essr-1-atm-2-0-0-2.telkom-ipnet.co.za [1
96.43.11.30]
8 252 ms 259 ms 264 ms wblv-ip-www-1.saix.net [196.25.1.200]

Trace complete.

C:\Users\Scavenger>

Thats the latency I get.
 
@ Funkmail get your self a 1GB SAIX account to see if it's not some routing issue that the providers are having when they go via Telkom's IPC.
 
Merenwenrago said:
2 453 ms 419 ms 394 ms dsl-185-69-1.dynamic.wa.co.za [41.185.69.1] well this is where problem is and thats dslam/exchange

if they really changed it to another card and port
post another tracert to check if they not lying
Click to expand...

The exchange does not handle your PPP session, another server does....So changing DSLAM's PORTS won't make a difference to the IP address / default gateway assigned to you.


Funkmail:

Good luck sorting this out mate, I've been trying for 18 months now.
My take on this is that the problem lies within SAIX somewhere. I also thought my Exchange was overloaded but apparently its not even close to being overloaded.
I bet you its some stupid config setting somewhere the only one dude sitting on a corner picking his nose the whole day knows about etc....
Total BS and utterly disgusting that telkom cannot even fix this....they're **** clueless man.
 
OK, I have found out it is an issue on the Exchange and is currently being looked at. As soon as I have more info on this I'll let you know, this should resolve the issue for everyone in the area connecting to the Waterford exchange.
 
funkmail said:
OK, I have found out it is an issue on the Exchange and is currently being looked at. As soon as I have more info on this I'll let you know, this should resolve the issue for everyone in the area connecting to the Waterford exchange.
Click to expand...

ok good at least you found it was exchange and not dslam
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X