dslreports logo
site
 
    All Forums Hot Topics Gallery
spc

spacer




how-to block ads


Search Topic:
uniqs
291
share rss forum feed

byebye_cable

join:2010-01-14
Scarborough, ON

1 edit

[Cable] Advise on poor cable connection

Looking for advise - I need a rock-solid internet connection preferably with a large cap.

I am sure others have had similar problems - what I don't know is if TekSavvy can resolve them. I logged a ticket some time ago & they did something, but it was not any kind of permanent solution.

I'm a geek - but not a network geek - last night I did the following remedial diagnostics;

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

C:\Documents and Settings\Paul>ping google.ca

Pinging google.ca [74.125.226.56] with 32 bytes of data:

Reply from 74.125.226.56: bytes=32 time=10ms TTL=56
Reply from 74.125.226.56: bytes=32 time=11ms TTL=56
Request timed out.
Reply from 74.125.226.56: bytes=32 time=10ms TTL=56

Ping statistics for 74.125.226.56:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 10ms, Maximum = 11ms, Average = 10ms

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

C:\Documents and Settings\Paul>tracert google.ca

Tracing route to google.ca [74.125.226.56]
over a maximum of 30 hops:

1 2 ms 1 ms 1 ms 192.168.1.1
2 10 ms 11 ms 15 ms 10.124.114.1
3 17 ms 11 ms 24 ms gw01.mtwh.phub.net.cable.rogers.com [66.185.89.1
]
4 12 ms * 16 ms comstock1.cable.teksavvy.com [24.52.255.58]
5 10 ms * 18 ms comstock2.cable.teksavvy.com [24.52.255.61]
6 9 ms 12 ms 10 ms 72.14.212.134
7 31 ms 13 ms * 216.239.47.114
8 * 17 ms 10 ms 64.233.175.132
9 12 ms 14 ms 11 ms yyz06s06-in-f24.1e100.net [74.125.226.56]

Trace complete.



creed3020
Premium
join:2006-04-26
Kitchener, ON
kudos:2

Could you do more than 4 pings, run these separately and post the results:

ping google.ca -n 100
ping teksavvy.com -n 100 -l 1024 (that last flag is a lower case L)


byebye_cable

join:2010-01-14
Scarborough, ON

Thanks for taking pity on me. There were done last night when I was NOT experiencing the issue, still, neither is 100%.

------------------------------------------------------------
C:\Documents and Settings\Paul>ping google.ca -n 100

Pinging google.ca [74.125.226.56] with 32 bytes of data:

Reply from 74.125.226.56: bytes=32 time=11ms TTL=56
Reply from 74.125.226.56: bytes=32 time=14ms TTL=56
Reply from 74.125.226.56: bytes=32 time=14ms TTL=56
Reply from 74.125.226.56: bytes=32 time=13ms TTL=56
Reply from 74.125.226.56: bytes=32 time=20ms TTL=56
Reply from 74.125.226.56: bytes=32 time=17ms TTL=56
Reply from 74.125.226.56: bytes=32 time=13ms TTL=56
Reply from 74.125.226.56: bytes=32 time=56ms TTL=56
Reply from 74.125.226.56: bytes=32 time=14ms TTL=56
Request timed out.
Reply from 74.125.226.56: bytes=32 time=12ms TTL=56
Reply from 74.125.226.56: bytes=32 time=80ms TTL=56
Reply from 74.125.226.56: bytes=32 time=20ms TTL=56
Reply from 74.125.226.56: bytes=32 time=13ms TTL=56
Reply from 74.125.226.56: bytes=32 time=85ms TTL=56
Reply from 74.125.226.56: bytes=32 time=11ms TTL=56
Reply from 74.125.226.56: bytes=32 time=17ms TTL=56
Reply from 74.125.226.56: bytes=32 time=12ms TTL=56
Reply from 74.125.226.56: bytes=32 time=11ms TTL=56
Reply from 74.125.226.56: bytes=32 time=15ms TTL=56
Reply from 74.125.226.56: bytes=32 time=162ms TTL=56
Reply from 74.125.226.56: bytes=32 time=17ms TTL=56
Reply from 74.125.226.56: bytes=32 time=21ms TTL=56
Reply from 74.125.226.56: bytes=32 time=16ms TTL=56
Reply from 74.125.226.56: bytes=32 time=15ms TTL=56
Reply from 74.125.226.56: bytes=32 time=13ms TTL=56
Reply from 74.125.226.56: bytes=32 time=13ms TTL=56
Reply from 74.125.226.56: bytes=32 time=15ms TTL=56
Reply from 74.125.226.56: bytes=32 time=14ms TTL=56
Reply from 74.125.226.56: bytes=32 time=10ms TTL=56
Reply from 74.125.226.56: bytes=32 time=13ms TTL=56
Reply from 74.125.226.56: bytes=32 time=14ms TTL=56
Reply from 74.125.226.56: bytes=32 time=16ms TTL=56
Reply from 74.125.226.56: bytes=32 time=17ms TTL=56
Reply from 74.125.226.56: bytes=32 time=13ms TTL=56
Reply from 74.125.226.56: bytes=32 time=11ms TTL=56
Reply from 74.125.226.56: bytes=32 time=26ms TTL=56
Reply from 74.125.226.56: bytes=32 time=20ms TTL=56
Reply from 74.125.226.56: bytes=32 time=10ms TTL=56
Reply from 74.125.226.56: bytes=32 time=12ms TTL=56
Reply from 74.125.226.56: bytes=32 time=9ms TTL=56
Reply from 74.125.226.56: bytes=32 time=23ms TTL=56
Reply from 74.125.226.56: bytes=32 time=12ms TTL=56
Reply from 74.125.226.56: bytes=32 time=10ms TTL=56
Reply from 74.125.226.56: bytes=32 time=16ms TTL=56
Reply from 74.125.226.56: bytes=32 time=12ms TTL=56
Reply from 74.125.226.56: bytes=32 time=17ms TTL=56
Reply from 74.125.226.56: bytes=32 time=15ms TTL=56
Reply from 74.125.226.56: bytes=32 time=12ms TTL=56
Reply from 74.125.226.56: bytes=32 time=13ms TTL=56
Reply from 74.125.226.56: bytes=32 time=12ms TTL=56
Reply from 74.125.226.56: bytes=32 time=12ms TTL=56
Reply from 74.125.226.56: bytes=32 time=14ms TTL=56
Reply from 74.125.226.56: bytes=32 time=12ms TTL=56
Reply from 74.125.226.56: bytes=32 time=10ms TTL=56
Reply from 74.125.226.56: bytes=32 time=15ms TTL=56
Reply from 74.125.226.56: bytes=32 time=12ms TTL=56
Reply from 74.125.226.56: bytes=32 time=15ms TTL=56
Reply from 74.125.226.56: bytes=32 time=11ms TTL=56
Reply from 74.125.226.56: bytes=32 time=17ms TTL=56
Reply from 74.125.226.56: bytes=32 time=11ms TTL=56
Reply from 74.125.226.56: bytes=32 time=13ms TTL=56
Reply from 74.125.226.56: bytes=32 time=12ms TTL=56
Reply from 74.125.226.56: bytes=32 time=17ms TTL=56
Reply from 74.125.226.56: bytes=32 time=16ms TTL=56
Reply from 74.125.226.56: bytes=32 time=17ms TTL=56
Reply from 74.125.226.56: bytes=32 time=54ms TTL=56
Reply from 74.125.226.56: bytes=32 time=12ms TTL=56
Reply from 74.125.226.56: bytes=32 time=11ms TTL=56
Reply from 74.125.226.56: bytes=32 time=13ms TTL=56
Reply from 74.125.226.56: bytes=32 time=11ms TTL=56
Reply from 74.125.226.56: bytes=32 time=19ms TTL=56
Reply from 74.125.226.56: bytes=32 time=15ms TTL=56
Reply from 74.125.226.56: bytes=32 time=16ms TTL=56
Reply from 74.125.226.56: bytes=32 time=12ms TTL=56
Reply from 74.125.226.56: bytes=32 time=12ms TTL=56
Reply from 74.125.226.56: bytes=32 time=29ms TTL=56
Reply from 74.125.226.56: bytes=32 time=13ms TTL=56
Reply from 74.125.226.56: bytes=32 time=103ms TTL=56
Reply from 74.125.226.56: bytes=32 time=10ms TTL=56
Reply from 74.125.226.56: bytes=32 time=25ms TTL=56
Reply from 74.125.226.56: bytes=32 time=17ms TTL=56
Reply from 74.125.226.56: bytes=32 time=117ms TTL=56
Reply from 74.125.226.56: bytes=32 time=19ms TTL=56
Reply from 74.125.226.56: bytes=32 time=16ms TTL=56
Reply from 74.125.226.56: bytes=32 time=12ms TTL=56
Reply from 74.125.226.56: bytes=32 time=13ms TTL=56
Reply from 74.125.226.56: bytes=32 time=16ms TTL=56
Reply from 74.125.226.56: bytes=32 time=12ms TTL=56
Reply from 74.125.226.56: bytes=32 time=11ms TTL=56
Reply from 74.125.226.56: bytes=32 time=12ms TTL=56
Reply from 74.125.226.56: bytes=32 time=19ms TTL=56
Reply from 74.125.226.56: bytes=32 time=11ms TTL=56
Reply from 74.125.226.56: bytes=32 time=19ms TTL=56
Reply from 74.125.226.56: bytes=32 time=14ms TTL=56
Reply from 74.125.226.56: bytes=32 time=13ms TTL=56
Reply from 74.125.226.56: bytes=32 time=14ms TTL=56
Reply from 74.125.226.56: bytes=32 time=22ms TTL=56
Reply from 74.125.226.56: bytes=32 time=14ms TTL=56
Reply from 74.125.226.56: bytes=32 time=13ms TTL=56

Ping statistics for 74.125.226.56:
Packets: Sent = 100, Received = 99, Lost = 1 (1% loss),
Approximate round trip times in milli-seconds:
Minimum = 9ms, Maximum = 162ms, Average = 20ms

C:\Documents and Settings\Paul>
---------------------------------------------------------
C:\Documents and Settings\Paul>ping teksavvy.com -n 100 -l 1024

Pinging teksavvy.com [206.248.155.70] with 1024 bytes of data:

Reply from 206.248.155.70: bytes=1024 time=36ms TTL=121
Reply from 206.248.155.70: bytes=1024 time=25ms TTL=121
Reply from 206.248.155.70: bytes=1024 time=24ms TTL=121
Reply from 206.248.155.70: bytes=1024 time=32ms TTL=121
Reply from 206.248.155.70: bytes=1024 time=22ms TTL=121
Reply from 206.248.155.70: bytes=1024 time=54ms TTL=121
Reply from 206.248.155.70: bytes=1024 time=21ms TTL=121
Reply from 206.248.155.70: bytes=1024 time=19ms TTL=121
Reply from 206.248.155.70: bytes=1024 time=32ms TTL=121
Reply from 206.248.155.70: bytes=1024 time=24ms TTL=121
Reply from 206.248.155.70: bytes=1024 time=21ms TTL=121
Reply from 206.248.155.70: bytes=1024 time=21ms TTL=121
Reply from 206.248.155.70: bytes=1024 time=20ms TTL=121
Reply from 206.248.155.70: bytes=1024 time=43ms TTL=121
Reply from 206.248.155.70: bytes=1024 time=20ms TTL=121
Reply from 206.248.155.70: bytes=1024 time=76ms TTL=121
Reply from 206.248.155.70: bytes=1024 time=21ms TTL=121
Reply from 206.248.155.70: bytes=1024 time=33ms TTL=121
Reply from 206.248.155.70: bytes=1024 time=22ms TTL=121
Reply from 206.248.155.70: bytes=1024 time=18ms TTL=121
Reply from 206.248.155.70: bytes=1024 time=28ms TTL=121
Reply from 206.248.155.70: bytes=1024 time=23ms TTL=121
Reply from 206.248.155.70: bytes=1024 time=21ms TTL=121
Reply from 206.248.155.70: bytes=1024 time=32ms TTL=121
Reply from 206.248.155.70: bytes=1024 time=23ms TTL=121
Reply from 206.248.155.70: bytes=1024 time=19ms TTL=121
Reply from 206.248.155.70: bytes=1024 time=24ms TTL=121
Reply from 206.248.155.70: bytes=1024 time=31ms TTL=121
Reply from 206.248.155.70: bytes=1024 time=22ms TTL=121
Reply from 206.248.155.70: bytes=1024 time=41ms TTL=121
Reply from 206.248.155.70: bytes=1024 time=22ms TTL=121
Reply from 206.248.155.70: bytes=1024 time=37ms TTL=121
Reply from 206.248.155.70: bytes=1024 time=20ms TTL=121
Reply from 206.248.155.70: bytes=1024 time=19ms TTL=121
Reply from 206.248.155.70: bytes=1024 time=71ms TTL=121
Reply from 206.248.155.70: bytes=1024 time=21ms TTL=121
Reply from 206.248.155.70: bytes=1024 time=21ms TTL=121
Reply from 206.248.155.70: bytes=1024 time=37ms TTL=121
Reply from 206.248.155.70: bytes=1024 time=18ms TTL=121
Reply from 206.248.155.70: bytes=1024 time=20ms TTL=121
Reply from 206.248.155.70: bytes=1024 time=23ms TTL=121
Reply from 206.248.155.70: bytes=1024 time=19ms TTL=121
Reply from 206.248.155.70: bytes=1024 time=25ms TTL=121
Reply from 206.248.155.70: bytes=1024 time=18ms TTL=121
Reply from 206.248.155.70: bytes=1024 time=23ms TTL=121
Reply from 206.248.155.70: bytes=1024 time=19ms TTL=121
Reply from 206.248.155.70: bytes=1024 time=29ms TTL=121
Reply from 206.248.155.70: bytes=1024 time=26ms TTL=121
Reply from 206.248.155.70: bytes=1024 time=23ms TTL=121
Reply from 206.248.155.70: bytes=1024 time=27ms TTL=121
Reply from 206.248.155.70: bytes=1024 time=32ms TTL=121
Reply from 206.248.155.70: bytes=1024 time=28ms TTL=121
Reply from 206.248.155.70: bytes=1024 time=26ms TTL=121
Reply from 206.248.155.70: bytes=1024 time=29ms TTL=121
Reply from 206.248.155.70: bytes=1024 time=19ms TTL=121
Reply from 206.248.155.70: bytes=1024 time=27ms TTL=121
Reply from 206.248.155.70: bytes=1024 time=26ms TTL=121
Reply from 206.248.155.70: bytes=1024 time=20ms TTL=121
Reply from 206.248.155.70: bytes=1024 time=20ms TTL=121
Reply from 206.248.155.70: bytes=1024 time=19ms TTL=121
Reply from 206.248.155.70: bytes=1024 time=30ms TTL=121
Reply from 206.248.155.70: bytes=1024 time=30ms TTL=121
Reply from 206.248.155.70: bytes=1024 time=21ms TTL=121
Reply from 206.248.155.70: bytes=1024 time=26ms TTL=121
Reply from 206.248.155.70: bytes=1024 time=24ms TTL=121
Reply from 206.248.155.70: bytes=1024 time=28ms TTL=121
Reply from 206.248.155.70: bytes=1024 time=21ms TTL=121
Reply from 206.248.155.70: bytes=1024 time=21ms TTL=121
Reply from 206.248.155.70: bytes=1024 time=21ms TTL=121
Reply from 206.248.155.70: bytes=1024 time=28ms TTL=121
Reply from 206.248.155.70: bytes=1024 time=27ms TTL=121
Reply from 206.248.155.70: bytes=1024 time=27ms TTL=121
Reply from 206.248.155.70: bytes=1024 time=23ms TTL=121
Reply from 206.248.155.70: bytes=1024 time=20ms TTL=121
Reply from 206.248.155.70: bytes=1024 time=23ms TTL=121
Reply from 206.248.155.70: bytes=1024 time=39ms TTL=121
Reply from 206.248.155.70: bytes=1024 time=22ms TTL=121
Reply from 206.248.155.70: bytes=1024 time=20ms TTL=121
Reply from 206.248.155.70: bytes=1024 time=21ms TTL=121
Request timed out.
Reply from 206.248.155.70: bytes=1024 time=35ms TTL=121
Reply from 206.248.155.70: bytes=1024 time=29ms TTL=121
Reply from 206.248.155.70: bytes=1024 time=21ms TTL=121
Reply from 206.248.155.70: bytes=1024 time=19ms TTL=121
Reply from 206.248.155.70: bytes=1024 time=22ms TTL=121
Reply from 206.248.155.70: bytes=1024 time=23ms TTL=121
Reply from 206.248.155.70: bytes=1024 time=21ms TTL=121
Reply from 206.248.155.70: bytes=1024 time=28ms TTL=121
Reply from 206.248.155.70: bytes=1024 time=20ms TTL=121
Reply from 206.248.155.70: bytes=1024 time=20ms TTL=121
Reply from 206.248.155.70: bytes=1024 time=21ms TTL=121
Reply from 206.248.155.70: bytes=1024 time=21ms TTL=121
Reply from 206.248.155.70: bytes=1024 time=19ms TTL=121
Reply from 206.248.155.70: bytes=1024 time=21ms TTL=121
Reply from 206.248.155.70: bytes=1024 time=23ms TTL=121
Reply from 206.248.155.70: bytes=1024 time=20ms TTL=121
Reply from 206.248.155.70: bytes=1024 time=20ms TTL=121
Reply from 206.248.155.70: bytes=1024 time=43ms TTL=121
Reply from 206.248.155.70: bytes=1024 time=19ms TTL=121
Reply from 206.248.155.70: bytes=1024 time=19ms TTL=121

Ping statistics for 206.248.155.70:
Packets: Sent = 100, Received = 99, Lost = 1 (1% loss),
Approximate round trip times in milli-seconds:
Minimum = 18ms, Maximum = 76ms, Average = 25ms



sbrook
Premium,Mod
join:2001-12-14
Ottawa
kudos:12
Reviews:
·WIND Mobile
·TekSavvy Cable
reply to byebye_cable

pinging google is not a good test of anything.

Google, like many host servers assigns ICMP pings a very low priority, therefore any load on the host server will take priority over the ping response delaying it.

A more meaningful test are a series of tracerts to your preferred destinations, although even that is not ideal. What it will reveal is where ping response variations begin. Remember that when you ping a distant site, the route TO the site may be different from the route back, so you cannot tell whether the delay is actually with the hop with anomalous results, or on its return path to you. But at least it provides some clues.

Some years back, I was analyzing a series of tracerts to a remote location, and there was a problem at a given hop. It took a reverse trace to discover the problem was not on the outbound path but in fact because a different route was used on the return route, via a teleglobe router in scarborough. It took a lot of tracing to discover that it was actually the teleglobe router ... finding routes that would go via that server eventually made it clear.