Unresponsible dsl

McT said:
New word of the day: "Unresponsible" :eek:
Click to expand...

http://www.urbandictionary.com/define.php?term=unresponsible

An entity which denies responsibility simply by the act of claiming they are not responsible, whereas from other logical reasonings they would take responsibility.

Similar to the term "undead," as in, not dead, but supposed to be.
Unresponsible is not responsible, but still should be.
A car company which states "we are not responsible for death caused by mechanical malfunction" renders itself unresponsible, as an automobile company should, from a moral standpoint, be held accountable for matters of safety.

However, a company that makes clothing irons and claims "we are not responsible for burns caused by using our product while still wearing clothes" would NOT be considered unresponsible from the reasoning that the corporation can not control individual behaviour of consumers.
Click to expand...
 
traceroute to microsoft.com
Tracing route to lb1.www.ms.akadns.net [64.4.11.42]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 10.0.0.2
2 34 ms 38 ms 39 ms dsl-146-56-01.telkomadsl.co.za [41.146.56.1]
3 33 ms 36 ms 37 ms tpr-ip-cat-1-vlan-913.telkom-ipnet.co.za [196.4
.33.238]
4 * * * Request timed out.
5 * * * Request timed out.
6 51 ms 37 ms 37 ms 196.43.10.130
7 36 ms 37 ms 36 ms rrba-ip-lir-1-gig-2-0-0-201.telkom-ipnet.co.za
196.43.33.5]
8 249 ms 232 ms 235 ms lon-ip-dir-telecity-pos-1-1-1.telkom-ipnet.co.z
[196.43.9.138]
9 353 ms 414 ms 414 ms vl1088.mpd01.lon01.atlas.cogentco.com [149.6.2.
93]
10 343 ms 340 ms 344 ms te0-2-0-3.ccr21.lon01.atlas.cogentco.com [130.1
7.3.226]
11 337 ms 338 ms 335 ms te0-2-0-4.ccr21.lon13.atlas.cogentco.com [154.5
.57.114]
12 327 ms 331 ms 326 ms te0-5-0-4.ccr21.jfk02.atlas.cogentco.com [154.5
.44.229]
13 330 ms 330 ms 327 ms te0-4-0-0.ccr21.jfk07.atlas.cogentco.com [154.5
.44.218]
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

ADSL Link Downstream Upstream
Connection Speed 384 kbps 128 kbps
Line Attenuation 36.5 db 22.5 db
Noise Margin 35.0 db 14 db
netgear telkom router

SNR and Attenuation looks ok.



C:\>ping www.microsoft.com

Pinging lb1.www.ms.akadns.net [64.4.11.42] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 64.4.11.42:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
 
Last edited:
Your trace routes look fine.

Try www.google.co.za next time as Microsoft no longer seems to allow their website to be pinged.

Have you got a different PC or device that you can test from?
 
C:\>ping www.google.com

Pinging www.google.com [196.23.168.147] with 32 bytes of data:
Reply from 196.23.168.147: bytes=32 time=34ms TTL=58
Reply from 196.23.168.147: bytes=32 time=343ms TTL=58
Reply from 196.23.168.147: bytes=32 time=34ms TTL=58
Reply from 196.23.168.147: bytes=32 time=36ms TTL=58

Ping statistics for 196.23.168.147:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 34ms, Maximum = 343ms, Average = 111ms

C:\>ping www.google.co.za

Pinging www.google.co.za [196.23.168.147] with 32 bytes of data:
Reply from 196.23.168.147: bytes=32 time=33ms TTL=58
Reply from 196.23.168.147: bytes=32 time=214ms TTL=58
Reply from 196.23.168.147: bytes=32 time=33ms TTL=58
Reply from 196.23.168.147: bytes=32 time=38ms TTL=58

Ping statistics for 196.23.168.147:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 33ms, Maximum = 214ms, Average = 79ms

local sites seems to load fine as google. trying the int sites and getting high latencies.....

C:\>ping www.bbc.co.uk

Pinging www.bbc.net.uk [212.58.246.95] with 32 bytes of data:
Reply from 212.58.246.95: bytes=32 time=230ms TTL=51
Reply from 212.58.246.95: bytes=32 time=237ms TTL=51
Reply from 212.58.246.95: bytes=32 time=238ms TTL=51
Reply from 212.58.246.95: bytes=32 time=296ms TTL=51

Ping statistics for 212.58.246.95:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 230ms, Maximum = 296ms, Average = 250ms
 
You can add a -t to check the stability over a longer period. C:\>ping www.google.com -t

What speed ADSL do you have ? Was is recently upgraded ? Is it possible to try another ISP ?
 
Mier said:
You can add a -t to check the stability over a longer period. C:\>ping www.google.com -t

What speed ADSL do you have ? Was is recently upgraded ? Is it possible to try another ISP ?
Click to expand...

same result as above with -t. ISP telkom. local seems fine but international sites result in high latencies close to 400ms during peak hours.
C:\>ping www.google.com

Pinging www.google.com [196.23.168.147] with 32 bytes of data:
Reply from 196.23.168.147: bytes=32 time=35ms TTL=58
Reply from 196.23.168.147: bytes=32 time=43ms TTL=58
Reply from 196.23.168.147: bytes=32 time=34ms TTL=58
Reply from 196.23.168.147: bytes=32 time=34ms TTL=58

Ping statistics for 196.23.168.147:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 34ms, Maximum = 43ms, Average = 36ms

this is taken before 8am. so it means that when telkom shapping kicks in latency **** :(
 
Last edited:
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X