| Will TSI issues follow me to Start? With TSI cable, I experience evening slowness (drops my citrix connection to work).
With TSI DSL (from a few years ago) I had a noisy line that slowed speeds down especially after a rain. Bell came a couple times and fixed nothing whatsoever (went with TSI cable after that).
Need a reliable connection, can anyone recommend cable or DSL with Start & might these problems "follow" me to Start...as in I would have a new provider but the same problems? |
|
 corsterPremium
join:2002-02-23
Gatineau, QC
 ·TekSavvy Cable
| said by byebye_cable:With TSI cable, I experience evening slowness (drops my citrix connection to work).
With TSI DSL (from a few years ago) I had a noisy line that slowed speeds down especially after a rain. Bell came a couple times and fixed nothing whatsoever (went with TSI cable after that).
Need a reliable connection, can anyone recommend cable or DSL with Start & might these problems "follow" me to Start...as in I would have a new provider but the same problems?
In regards to cable: Depends where the congestion is. If it's occurring before the traffic is handed off to TSI (such as local node congestion), you'd still experience it. If it's on TSI's end, you wouldn't.
In regards to DSL: If your line was bad then, it's likely still bad now. Doesn't matter who your provider is, i'd stick with cable. |
|
| Thanks. How can I determine where the cable congestion is?
If there's some ping/tracert or something, I can run it...let me know! |
|
| You can always check with your neighbors if they use Rogers cable. If it's slow for them at peak times, then its likely local congestion. If they don't have those issues, then you should be okay with other providers. |
|
mlord
join:2006-11-05
Nepean, ON
kudos:9 | reply to byebye_cable
Before switching ISPs, first get a DOCSIS 3.0 capable cable modem (assuming you don't already have one). It will access more data channels in parallel, reducing the effects of node congestion on your transfers. |
|
| Thanks.
If my google-fu is good, my Motorola Surfboard SB5101N is not DOCSIS 3.0 capable.
Canada Computers has Thomson DCM476 - DOCSIS 3.0 Certified Cable Modem for $99. If fact, the salesperson I spoke with said he himself had problems with TSI & moving to this modem fixed it - don't know if they're on commission @ Canada Computers.
Is the Thomson DCM476 a reasonable choice? |
|
 TSI MartinPremium
join:2006-02-23
Chatham, ON
kudos:23 | said by byebye_cable:Is the Thomson DCM476 a reasonable choice?
It's the one we sell  |
|
|
|
Reviews:
 ·Start Communicat..
·ikTel Networks
| reply to byebye_cable
You could also download a program like ping plotter, and have it run a continuous trace to a site you are experiencing issues with. Set the interval to 5 seconds, and keep 1000 records. Let it run for a few hours while you are having problems.
You can then look at the results. If you see your ping time shooting up on the first 1-3 hops, before you start seeing the server names looking like Teksavvy, then the issue is probably local node congestion.
If the ping increases at Teksavvy IP's, the issue is them.
If it occurs later, then it might be a 3rd party issue that you may or may not still have if you switch ISP's,
You could also save the data from pingplotter and PM it to someone on the forums who knows what to look for. I wouldn't post it publicly on the forum since it has your IP in it. |
|
1 edit | This is not from ping plotter nor is it "to" the site I'm having problems with - but - on the off chance it is helpful? It was done when I have having big trouble.
For clarity, my problem isn't really speed, it's that my citrix connection disconnects repeatedly.
Those nasty asterix are delays & they appear mainly beside the teksavvy servers...does TSI Martin have some "splaining" to do?
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. |
|
| We'd need to see many more of those over time to confirm, but it does look like some packet loss occurring at Teksavvy.
Not sure it's congestion as ping times are excellent when they do get through. |
|
| reply to corster
said by corster:In regards to DSL: If your line was bad then, it's likely still bad now. Doesn't matter who your provider is, i'd stick with cable. Depending on how long ago that was, there always is the possibility of new remotes close enough to bypass the problematic copper or at least substantially improve SNRMs. |
|
pabloMVM
join:2003-06-23
kudos:1
1 edit | reply to GreenEnvy22
Hi,
The packet loss can be seen by the `*' in the `tracert' command.
When things look sketchy, run a continuous ping in a terminal window. On windows, you'll need to use the `-t' switch: `ping -t www.google.ca'
If all is well, you should see no packet loss. You may see one packet lost when you CTRL-C to terminate it.
Cheers,
-pablo
--
openSUSE 12.2/KDE 4.x
ISP: TekSavvy Bonded DSL; backhauled via a 6KM wireless link
Assorted goodies: »pablo.blog.blueoakdb.com |
|
Reviews:
·TekSavvy DSL
| reply to byebye_cable
Yes the problem will most likely follow you, and the prices are about to increase. Sounds like your cable numbers aren't the best. (have you looked at them?). Make sure it is a direct line to the modem from the box.
My suggestion is move next door to someone who works at CRTC and steal their internet. They are the only ones who will have it soon. |
|
| reply to GreenEnvy22
said by GreenEnvy22:We'd need to see many more of those over time to confirm, but it does look like some packet loss occurring at Teksavvy.
Not sure it's congestion as ping times are excellent when they do get through.
Thank you.
I'll do some more tracert's when things get sketchy.
Assuming it is a TekSavvy issue, might the DOCSIS 3.0 modem overcome it?
Other then TSI fixing the issue - the new modem is the next least painful solution. |
|
mlord
join:2006-11-05
Nepean, ON
kudos:9 Reviews:
·Start Communicat..
·TekSavvy Cable
·TekSavvy DSL
| said by byebye_cable:Assuming it is a TekSavvy issue, might the DOCSIS 3.0 modem overcome it?
Other then TSI fixing the issue - the new modem is the next least painful solution. Updating the modem to current technology is the first step regardless of what you do. Start.ca won't activate you on that old clunker you have today, and a DOCSIS3 modem will very likely improve things even with your current provider. |
|
TypeS
join:2012-12-17
London, ON
kudos:1 Reviews:
·TekSavvy Cable
| reply to byebye_cable
said by byebye_cable:Thanks.
If my google-fu is good, my Motorola Surfboard SB5101N is not DOCSIS 3.0 capable.
Canada Computers has Thomson DCM476 - DOCSIS 3.0 Certified Cable Modem for $99. If fact, the salesperson I spoke with said he himself had problems with TSI & moving to this modem fixed it - don't know if they're on commission @ Canada Computers.
Is the Thomson DCM476 a reasonable choice?
I can tell you for certainty they are no on commission and their wages coupled with how the company is managed don't really inspire that much loyalty. If they push any sales its services, hardware margins are so abysmal that they just barely only pay for the staff selling them.
But you definitely should pick up a DOCSIS 3.0 Modem & the DCM476 is a great choice right now. |
|
| reply to mlord
The Thomson DOCSIS3 modem is sitting beside my old surfboard, waiting to be provisioned (I will post an update). Here's a new tracert from earlier tonight when the problem was severe;
C:\Documents and Settings\Paul>tracert vtapps.viterra.ca
Tracing route to vtapps.viterra.ca [198.169.205.151]
over a maximum of 30 hops:
1 1 ms 5 ms 1 ms 192.168.1.1
2 18 ms 9 ms 10 ms 10.124.114.1
3 * 22 ms * gw01.mtwh.phub.net.cable.rogers.com [66.185.89.1]
4 * 10 ms 10 ms comstock1.cable.teksavvy.com [24.52.255.58]
5 10 ms 11 ms 13 ms comstock1.cable.teksavvy.com [24.52.255.57]
6 * 10 ms 10 ms 10gigabitethernet4-1.core1.tor1.he.net [209.51.161.193]
7 9 ms 11 ms * gw-allstream.torontointernetxchange.net [206.108.34.4]
8 82 ms 83 ms 81 ms 10ge4-11.hcap3-cal.bb.allstream.net [199.212.164.170]
9 93 ms * * 0029026.lodgenet.net [216.13.201.46]
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
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.
Trace complete. |
|
corsterPremium
join:2002-02-23
Gatineau, QC Reviews:
·TekSavvy Cable
| reply to InvalidError
said by InvalidError:said by corster:In regards to DSL: If your line was bad then, it's likely still bad now. Doesn't matter who your provider is, i'd stick with cable. Depending on how long ago that was, there always is the possibility of new remotes close enough to bypass the problematic copper or at least substantially improve SNRMs. Possible, but something like that could just as easily be a problem with the lines to the house - and if Bell didn't replace them then... they certainly haven't since. |
|
| said by corster:Possible, but something like that could just as easily be a problem with the lines to the house - and if Bell didn't replace them then... they certainly haven't since. If the remote bypasses 1-2km of outside plant, stats would likely still improve significantly even if no repairs were done to wiring.
The apartment I currently live in has 50+ years old phone wiring that has been hacked and spliced into multiple times with a messy wiring panel in the basement boiler room that has been through a few floodings and I still get 25dB SNRM.
DSL signals can take a fair bit of abuse as long as metallic continuity is good and the remote is close enough. |
|
1 edit | reply to mlord
TSI routing problem? Same problems remain at the same time. This is *after*;
- The Thomson DOCSIS3 modem provisioned & working.
- Next, TSI ticket opened, they requested a sequence of tracert's, was given same, and "changed something" 
Still hoping for an opinion if this problem would follow me if I went to Start cable.
Here are the tracert's TSI requested, these are with the new modem and after TSI "changed something;
C:\Documents and Settings\Paul>tracert 8.8.8.8
Tracing route to google-public-dns-a.google.com [8.8.8.8]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 192.168.1.1
2 19 ms * 19 ms 10.124.114.1
3 17 ms 15 ms 12 ms gw01.mtwh.phub.net.cable.rogers.com [66.185.89.1]
4 * 114 ms 7 ms comstock1.cable.teksavvy.com [24.52.255.58]
5 * 20 ms 9 ms comstock1.cable.teksavvy.com [24.52.255.57]
6 * 10 ms 22 ms 72.14.212.134
7 10 ms 10 ms 9 ms 209.85.255.232
8 30 ms 28 ms 69 ms 72.14.236.226
9 * 40 ms 34 ms 209.85.249.11
10 56 ms 35 ms 33 ms 72.14.238.16
11 43 ms 35 ms 53 ms 216.239.49.145
12 36 ms 34 ms 35 ms google-public-dns-a.google.com [8.8.8.8]
Trace complete.
C:\Documents and Settings\Paul>tracert google.ca
Tracing route to google.ca [74.125.226.55]
over a maximum of 30 hops:
1 1 ms 1 ms tracert 74.125.226.56
Tracing route to yyz06s06-in-f24.1e100.net [74.125.226.56]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 192.168.1.1
2 101 ms 9 ms 7 ms 10.124.114.1
3 * 23 ms 10 ms gw01.mtwh.phub.net.cable.rogers.com [66.185.89.1]
4 * 10 ms 13 ms comstock2.cable.teksavvy.com [24.52.255.62]
5 * 10 ms 9 ms comstock2.cable.teksavvy.com [24.52.255.61]
6 10 ms 10 ms 8 ms 72.14.212.134
7 9 ms * 14 ms 216.239.47.114
8 12 ms 22 ms 15 ms 64.233.175.132
9 10 ms * 11 ms yyz06s06-in-f24.1e100.net [74.125.226.56]
Trace complete.
C:\Documents and Settings\Paul>tracert 74.209.160.12
Tracing route to static-74-209-160-12.lynnwood.netriver.net [74.209.160.12]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 192.168.1.1
2 21 ms 7 ms 10 ms 10.124.114.1
3 13 ms 11 ms 11 ms gw01.mtwh.phub.net.cable.rogers.com [66.185.89.1]
4 9 ms 8 ms 20 ms comstock1.cable.teksavvy.com [24.52.255.58]
5 * * 11 ms comstock1.cable.teksavvy.com [24.52.255.57]
6 * 24 ms 12 ms 10gigabitethernet4-1.core1.tor1.he.net [209.51.1
61.193]
7 27 ms 44 ms 23 ms 10gigabitethernet7-3.core1.chi1.he.net [184.105.
213.150]
8 60 ms 49 ms 49 ms 10gigabitethernet3-2.core1.den1.he.net [184.105.
213.86]
9 77 ms 74 ms 74 ms 10gigabitethernet3-4.core1.sea1.he.net [184.105.
213.41]
10 76 ms * 74 ms six.netriver.net [206.81.80.160]
11 78 ms 76 ms 78 ms static-74-209-160-12.lynnwood.netriver.net [74.2
09.160.12]
Trace complete.
C:\Documents and Settings\Paul>tracert 24.212.236.1
Tracing route to 24-212-236-1.cable.teksavvy.com [24.212.236.1]
over a maximum of 30 hops:
1 2 ms 1 ms 1 ms 192.168.1.1
2 41 ms 10 ms * 24-212-236-1.cable.teksavvy.com [24.212.236.1]
3 18 ms 12 ms * 24-212-236-1.cable.teksavvy.com [24.212.236.1]
4 10 ms * 43 ms 24-212-236-1.cable.teksavvy.com [24.212.236.1]
Trace complete. |
|
