O Canada! > Canadian > TekSavvy > Reliable 2 yrs, TSI unreliable now; ten 2-16 hr outages-3mth

Reliable 2 yrs, TSI unreliable now; ten 2-16 hr outages-3mth

Re: Reliable 2 yrs, TSI sucks now; ten 2-16 hr outages 3 mnths

reply to hiremichael

reply to hiremichael
Anyone else notice about once a week now someone makes a post like this. Almost as if they are trying to keep attention on something that really doesn't require attention.
--
COME ON OVER TO THE NEW »TekSavvy FORUM

Actually, I believe him because I'm currently experiencing the same thing:

"the DSL handshakes fine. It's the PPPoE authentication requests that get no response."

This has been my story for the past week. I've been in communication with TSI tech support ever since, but the situations has not yet been resolved.

But I do believe it's Bell's fault tho, it's their lines after all.

reply to hiremichael
Even though I am not a TSI customer, I have been seeing a few threads here with downtime issues.

Must be something to do with the new equipment.

The new equipment is basically the exact same router we have been using all along.

hiremichael: Can you please PM me with your username so I can have a look into your issue?

reply to hiremichael
I have yet to see Teksavvy go down once for me. SO far this isp has been 10x better then my old one and never had any problems with IT support.

Maybe its a problem on your line possibly? Since you said sometimes switching to another isp account did not help?

Ciao
--
Computer: AMD AthlonXP 2800, 1GB, Seagate 500gb 7200rpm 16mb cache, ati All-In-Wonder X800 XT, 5mb DSL

»www.MaximumRepair.ca

reply to The Flash
i noticed no downtime tahts tsi's fault.. infact when they had pppoe downtime i was still up

i should also mention bell is much worse... they have downtown also monthly... and whats worse their buisness accounts are even worse! (should be little - to none).

i bet other ex bell guys here can tell you the horror of big bad bell :/

reply to hiremichael

reply to hiremichael
Thanks for all the replies.

I've been building/programming with computers for 30 years, professionally 23 years. Networking, 20 years. I've had high speed internet since late 1996 (Rogers Wave, $40/month for 240 KBits/sec). I've been a contractor building embedded Linux network devices for 10 years (SNMP, security, 1 DSLAM).

So yeah, I might not know ALL the intricacies of DSL or PPPoE today, but I think I more than qualify as a "Tech Savvy" Internet consumer who understands when PPPoE authentication is failing.

>What do you mean by this? When the PPPoE authentication rquests failed, did test@test work?

No, test@test did NOT work. PPPoE authentication requests were sent but no response came.

>Anyone else notice about once a week now someone makes a post like this. Almost as if they are trying to keep attention on something that really doesn't require attention.

I've made perhaps 2 such posts recently because I'm pulling my hair out here. I REALLY want my TSI DSL to work reliably again like it did the last 2 years. I don't want to lose my TSI email or junk my new $200 DSL modem and I don't want to trade TSI support for Videotron support.

>Actually, I believe him because I'm currently experiencing the same thing

Thank you.

>i should also mention bell is much worse... they have downtown also monthly

But my downtime is about twice per month so Sympatico would be an improvement. Many of these outages also affected Sympatico locally, but at least one did not.

A Bell tech called me this afternoon. (Yesterday Bell said my DSL modem was defective and someone would come to prove it.) He really didn't say much, since he was a hardware tech and this was a software problem. I expressed my extreme displeasure with these ongoing outages and with all the incorrect information I keep getting.

I DO believe that most or all of these outages are Bells "fault". In the end, it doesn't matter, except that DSL from other ISPs will probably have the same issues. I keep hoping that this is the last outage, because I don't want to change ISPs.

For now, I will probably try Videotrons most basic service for 3 month low price. This will be my backup if/when TSI DSL fails. If TSI DSL keeps dropping and Videotron looks good I will switch to Videotron. Perhaps I can get a cheap DSL account for backup.

The vast majority of the messages in Videotron forum here are in french and I'm virtually unilingual. Cest la vie...

I'm seeing that the modem actually syncs up at 672 on the upstream while it should actually be 800 as you already said. So this happens with 2 different modems right? Although it doesn't happen very often, it may be possible that the DSLAM line card is defective...or maybe even just the port. There is currently a ticket opened with bell...for a timeout problem..I'm fairly sure these are actually related to the fact that your modem is only syncing up at 672...basically the PADO PPP packets never make it to the BAS.

>So this happens with 2 different modems right?

I haven't tried the other modem since the last outage about 1-2 weeks ago. I'm no longer willing to jump through the hoops required for this, since I've done that during several of the previous outages and it never fixed the problem. Several times I tied the modem directly into the phone company termination and disconnected all other lines for the house; that changed nothing.

>Although it doesn't happen very often, it may be possible that the DSLAM line card is defective...or maybe even just the port. There is currently a ticket opened with bell...for a timeout problem..I'm fairly sure these are actually related to the fact that your modem is only syncing up at 672...basically the PADO PPP packets never make it to the BAS.

OK, perhaps. I hope Bell can fix this, if this is the case.

But Bell guy that called today said it was a software problem, and the outage 1-2 weeks ago was announced here and acknowledged as a widespread problem. Perhaps they are different problems. OTOH, different Bell guys say different things, so IMO, some of them are just guessing or are wrong.

My TSI DSL has been great until 3 months ago. I really hope someone can fix this or I'll be forced into becoming a Videotron customer. Thanks...

reply to hiremichael
Just for clarification the "test@test" login is a tool used to see if the customer is indeed getting to the Bas server to be provided an IP. If test@test works with password "test", it assigns a private IP, not an internet IP, then there is most likely an authentication problem with the customer's login ID. Just a point of clarification.
--
My Canada includes Quebec.

but if test@test does not work then it is a Bell issue.

reply to hiremichael
Hi hiremichael,

I've been away for the last couple days, so I'm late in this discussion. As Glen and JayMan are both pointing out, if the Test@test fails, it's for sure not TSI.

From a point of clarification, if we're down and it's our fault, I've made it vary clear that we wouldn't BS "anyone" and tell them when we were the cause.

We've had a few things over the last couple of months, due to some huge upgrades, which were all documented, and planned from months prior (so we let everyone know well ahead that we'd have a bumpy ride once the major changes came down).

These changes however affect, for the most part, only about 2,000 of our client-base as they were the only remaining clients on the old ATM Gig-E connections.

In any case, I hope your issues have either been dealt with or are being dealt with at this point. Should they not have been at this point, please feel free to PM me your details so that I can push things forward for you.

Regards,

Rocky
--
TSI Rocky - TekSavvy Solutions Inc.

Hi Rocky,

>it's for sure not TSI.

OK, wonderful, it not TSIs "fault". Doesn't really matter, since TSI is effectively attached at the hip to Bell.

If my DSL keeps going down, then TSI will likely lose me as a customer and advocate regardless of who's "fault" it is.

IMO, TSI should provide me with free DialUp access for when my DSL is down. IMO, TSI should make some compensation for all my outages. (Yeah, a few months free access is just a tiny fraction of what my time is worth; probably have spent 40+ hours troubleshooting this.)

I've had no problems since this past weekend, but I'm expecting some within the next few weeks, since it happens every 2 weeks or so. Perhaps their auth server needs to be rebooted that often... Gee is it running on Win95 ?

Thanks...

reply to hiremichael
A few free months access? LOL.