Join us now. It is free, and it takes less than 1 minute to register.
Register now
Subscribe to our daily newsletter. It is free, and it comes with many benefits.


+ Reply to Thread
Page 2 of 2 FirstFirst 12
Results 16 to 25 of 25

Thread: Understanding Adsl in SA and Troubleshooting Tools

  1. #16
    Super Grandmaster
    Join Date
    Jul 2011
    Location
    Durban
    Posts
    5,273

    Default

    [QUOTE=doublefrangelico;8025888]
    "Now that I know a critical factor is the length of the cabling from my modem/router to the DSLAM or Exchange, I'd like to know how to figure out where my DSLAM is. Is it in one of those small blue and white boxes (approx 1.2mx30cmx60cm) on the street corners or is it a housed in a small building? (etc etc) I don't trust Telkom to provide this info."

    No this is not a DSLAM that is a street box ( cable from the exchange meets the local cabling that feeds the poles )
    Last edited by FNfal; 05-02-2014 at 06:49 PM.
    If it walks like a duck and kwaks like a duck ..its a duck
    Full consciousness will come to very few people in their life time .

  2. #17
    Super Grandmaster ichigo's Avatar
    Join Date
    Aug 2006
    Location
    Pietermaritzburg
    Posts
    9,048
    Blog Entries
    1

    Default

    Quote Originally Posted by doublefrangelico View Post
    Hi Guys and thanks for making things much clearer.

    In troubleshooting my current situation, I need a bit of specific info.

    Now that I know a critical factor is the length of the cabling from my modem/router to the DSLAM or Exchange, I'd like to know how to figure out where my DSLAM is. Is it in one of those small blue and white boxes (approx 1.2mx30cmx60cm) on the street corners or is it a housed in a small building? (etc etc) I don't trust Telkom to provide this info.

    This site shows the location my of my "exchange". (could this be the DSLAM and not the exchange?)
    http://www.broadbandstats.co.za/exchange/RNHL05


    The reason I'm asking is because Telkom told me that I was more than 5KM from the exchange and that this was the reason I was limited to 384Kbps and thus the reason my latency and speed are so bad (<120KBps). I do realise after reading this excellent guide that even though I am 4.4Km as the crow files from the abovementioned exchange, the cables might be more than 5km. This is why I'm hoping that there is a DSLAM inbetween, and thus the reason for trying to find a way to identify it so that I can ask to be connected via it, if I am not.

    I am desperate.... No Line of Sight for cellular/wireless providers, no more than 34KB/s download speed on cellular provider even with professionally-installed YAGI antenna directly connected to router, >5km from ADSL exchange .... FML ;-)
    What you need to find is a big white cabinet then you can work how far you actually are from it, its the mini exchange/dslam apparently. If you close to it your cable is either faulty or it goes wacko around the whole neigbourhood before it reaches it .

    Exchange on broadbandstats is in a brick building it isnt the mini-exchange/dslam

  3. #18

  4. #19
    Super Grandmaster ichigo's Avatar
    Join Date
    Aug 2006
    Location
    Pietermaritzburg
    Posts
    9,048
    Blog Entries
    1

    Default

    Updated with helpful DNS' settings when you faced with a faulty DNS causing you to download/upload slowly and to have high latency and with VDSL 1&2.
    Last edited by ichigo; 20-05-2013 at 01:47 PM.

  5. #20
    Super Grandmaster ichigo's Avatar
    Join Date
    Aug 2006
    Location
    Pietermaritzburg
    Posts
    9,048
    Blog Entries
    1

    Default

    If you like my thread vote for it here
    http://mybroadband.co.za/vb/showthre...on-Please-vote

  6. #21
    Grandmaster Mineer's Avatar
    Join Date
    Apr 2008
    Location
    /\/ŻŻŻŻŻ\/\
    Posts
    3,189

    Default

    Quote Originally Posted by ichigo View Post
    If you like my thread vote for it here
    http://mybroadband.co.za/vb/showthre...on-Please-vote
    its Sad that my thread was not selected for this
    Understanding SNR and Attenuation Rates
    Last edited by Mineer; 29-06-2013 at 11:55 AM.
    “We know too well that our freedom is incomplete without the freedom of the Palestinians.”― Nelson Mandela

  7. #22
    Super Grandmaster ichigo's Avatar
    Join Date
    Aug 2006
    Location
    Pietermaritzburg
    Posts
    9,048
    Blog Entries
    1

    Default

    Quote Originally Posted by Mineer View Post
    its Sad that my thread was not selected for this
    Understanding SNR and Attenuation Rates
    Did you enter it in the newest one since I never saw it there

  8. #23

    Default

    I would take issue with your statement :-
    DNS' in the router settings affects your adsl latency/speed so if you in Durban and you have Cape Town as your dns it will affect your adsl latency/speed since any data transfered(uploaded) or downloaded has to go through Cape Town first before going out Internationally or Locally

    DNS is a Domain Name Server, which is only used during the process to find and IP Address {eg 123.234.132.213} from a Domain Name {eg www.google.com} So whilst it is true that if a DNS is situated far away your DNS lookup may take slightly longer, it would not affect the actual traffic. Once your host has resolved the IP address of the destination host the traffic is routed via the shortest possible path to the destination. Thus the location of the DNS will only affect the latency of DNS lookups, not all traffic.

  9. #24

    Default

    Here are a couple of useful tools available on most systems.
    On windows there is a utility called "PathPing" it is like Traceroute on Steroids, Not only does it find each hop on the path it also tests the latency on each hop.
    So if you suspect you are getting less than optimal throughput, Pathping can tell you where the problem might be.
    It first identifies all the hops, and then spends several minutes testing the hop latencies, and then produces a report like this:-

    C:\Documents and Settings\user>pathping www.mybroadband.co.za

    Tracing route to www.mybroadband.co.za [197.242.89.170]
    over a maximum of 30 hops:
    0 triumph.abc.lan [192.168.42.148]
    1 myway.abc.lan [192.168.42.254]
    2 197-87-143-1.cpt.mweb.co.za [197.87.143.1]
    3 197-84-96-162.cpt.mweb.co.za [197.84.96.162]
    4 197-84-2-2.cpt.mweb.co.za [197.84.2.2]
    5 197-84-5-226.cpt.mweb.co.za [197.84.5.226]
    6 197-84-7-5.cpt.mweb.co.za [197.84.7.5]
    7 africainx.ct1.napafrica.net [196.46.25.7]
    8 CORE.GP-CN-HET-MEE-1.TO.GP-MR-VOD-MEE-1.DFA.P2P.10G.za.africainx.net [41.84.12.151]
    9 41-66-132-242-f2.HET001-CPE-1-to-GP-CN-HET-MEE-1.africainx.net [41.66.132.242]
    10 core-access-switch1.jnb1.host-h.net [197.189.193.1]
    11 row-access-switch1-row7-8.jnb1.host-h.net [197.189.193.39]
    12 41.203.24.42
    13 www.mybroadband.co.za [197.242.89.170]

    Computing statistics for 325 seconds...
    Source to Here This Node/Link
    Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
    0 triumph.jotrago.lan [192.168.42.148]
    0/ 100 = 0% |
    1 7ms 0/ 100 = 0% 0/ 100 = 0% milliways.jotrago.lan [192.168.42.254]
    0/ 100 = 0% |
    2 20ms 0/ 100 = 0% 0/ 100 = 0% 197-87-143-1.cpt.mweb.co.za [197.87.143.1]
    0/ 100 = 0% |
    3 36ms 0/ 100 = 0% 0/ 100 = 0% 197-84-96-162.cpt.mweb.co.za [197.84.96.162]
    0/ 100 = 0% |
    4 29ms 0/ 100 = 0% 0/ 100 = 0% 197-84-2-2.cpt.mweb.co.za [197.84.2.2]
    0/ 100 = 0% |
    5 33ms 0/ 100 = 0% 0/ 100 = 0% 197-84-5-226.cpt.mweb.co.za [197.84.5.226]
    0/ 100 = 0% |
    6 29ms 0/ 100 = 0% 0/ 100 = 0% 197-84-7-5.cpt.mweb.co.za [197.84.7.5]
    0/ 100 = 0% |
    7 37ms 0/ 100 = 0% 0/ 100 = 0% africainx.ct1.napafrica.net [196.46.25.7]
    0/ 100 = 0% |
    8 --- 100/ 100 =100% 100/ 100 =100% CORE.GP-CN-HET-MEE-1.TO.GP-MR-VOD-MEE-1.DFA.P2P.10G.za.africainx.net [41.8
    4.12.151]
    0/ 100 = 0% |
    9 55ms 0/ 100 = 0% 0/ 100 = 0% 41-66-132-242-f2.HET001-CPE-1-to-GP-CN-HET-MEE-1.africainx.net [41.66.132.
    242]
    0/ 100 = 0% |
    10 60ms 0/ 100 = 0% 0/ 100 = 0% core-access-switch1.jnb1.host-h.net [197.189.193.1]
    0/ 100 = 0% |
    11 56ms 0/ 100 = 0% 0/ 100 = 0% row-access-switch1-row7-8.jnb1.host-h.net [197.189.193.39]
    0/ 100 = 0% |
    12 54ms 0/ 100 = 0% 0/ 100 = 0% 41.203.24.42
    0/ 100 = 0% |
    13 58ms 0/ 100 = 0% 0/ 100 = 0% 197.242.89.170

    Trace complete.



    You can see the delay for each hop and determine whihc is the slowest link (core-access-switch1.jnb1.host-h.net [197.189.193.1])

    On many Linux flavours a similar utility is "TracePath"

    Happy pinging

  10. #25

+ Reply to Thread
Page 2 of 2 FirstFirst 12

Bookmarks

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •