R0CKY
TSI Rocky
Premium,VIP
join:2005-05-19
Chatham, ON
| reply to HiVolt
Re: In Toronto & maintenance night
said by HiVolt  :Rocky are you along for the maintenance tonight as well? Any more videos planned? Marc and I headed back last night around supper time after a Juniper Seminar.... So we didn't use the window. Too many other things needed to be done so the one night wasn't going to cut it. Marc will post when the next window is at this point. |
|
DJMASACRE
join:2008-05-27
Nepean, ON
 ·TekSavvy Solutions..
·Bell Sympatico
| reply to joshb
said by joshb :For those more geeky people around here... Here's the link to force10 website...» www.force10networks.com yay you saved me a google !@ =) |
|
DJMASACRE
join:2008-05-27
Nepean, ON
·TekSavvy Solutions..
·Bell Sympatico
| reply to AkFubar
said by AkFubar :After watching all of this if anyone had doubts about paying the extra $4.00 those doubts should be gone.  Very impressive guys! your right about that
imagine.. customers.. actually wanting .. to pay an extra fee to a company and be happy about it. |
|
Ty
@rogers.com
| reply to TSI Steve
I lost internet connection on June 5th at 7:30PM. It's currently 8:20am on June 6th and it still won't connect (also tried test@test). I'm in Mississauga (Dixie/Lakeshore area). Is my connection down due to this maintenance and will it be up shortly or is the problem something else? |
|
LazMan
join:2003-03-26
Angus, ON
·TekSavvy Solutions..
| said by Ty :
I lost internet connection on June 5th at 7:30PM. It's currently 8:20am on June 6th and it still won't connect (also tried test@test). I'm in Mississauga (Dixie/Lakeshore area). Is my connection down due to this maintenance and will it be up shortly or is the problem something else?
IF the "test@test" login won't work, either - it's either a connection issue at a lower level, or a Bell problem...
Laz |
|
Angelo_
The Network Guy
Premium
join:2002-06-18 | call into tek |
|
jfmezei
Premium
join:2007-01-03
Beaconsfield, QC
·ELECTRONICBOX
| reply to LazMan
>IF the "test@test" login won't work, either - it's either a connection
>issue at a lower level, or a Bell problem...
This is no longer true. If you have X unsuccesful connection attempts within Y time, Bell will block all PPPOE traffic (discovery, authentication) for Z minutes, and that includes trying test@test.
Teksavvy supports this (supposedly reduces the load on their radius servers) and is not concerned about the fact that Bell refuses to divulge X Y and Z. But this is why they recommend you disconnect your modem for 10 minutes to prevent any PPPOE traffic from reaching Bell to reset this block.
During one of the installation shows a few months back, I was down for 3 hours because of this. The big red button was pressed to rebalance the ERXs and there was a problem reconnecting (I guess the BAS kept trying to get to the downed ERX instead of round robbining to the others) and I got blocked out. |
|
joshb
Don't sweat the small stuff.
Premium
join:2006-03-04
Calgary, AB
clubs:
·TELUS
·TekSavvy Solutions..
 ·Shaw
 ·Primus Talkbroadband
 ·GoDaddy Hosting
| said by jfmezei :>IF the "test@test" login won't work, either - it's either a connection >issue at a lower level, or a Bell problem... This is no longer true. If you have X unsuccesful connection attempts within Y time, Bell will block all PPPOE traffic (discovery, authentication) for Z minutes, and that includes trying test@test. Teksavvy supports this (supposedly reduces the load on their radius servers) and is not concerned about the fact that Bell refuses to divulge X Y and Z. But this is why they recommend you disconnect your modem for 10 minutes to prevent any PPPOE traffic from reaching Bell to reset this block. During one of the installation shows a few months back, I was down for 3 hours because of this. The big red button was pressed to rebalance the ERXs and there was a problem reconnecting (I guess the BAS kept trying to get to the downed ERX instead of round robbining to the others) and I got blocked out. said by jfmezei :>IF the "test@test" login won't work, either - it's either a connection >issue at a lower level, or a Bell problem... This is no longer true. If you have X unsuccesful connection attempts within Y time, Bell will block all PPPOE traffic (discovery, authentication) for Z minutes, and that includes trying test@test. Teksavvy supports this (supposedly reduces the load on their radius servers) and is not concerned about the fact that Bell refuses to divulge X Y and Z. But this is why they recommend you disconnect your modem for 10 minutes to prevent any PPPOE traffic from reaching Bell to reset this block. During one of the installation shows a few months back, I was down for 3 hours because of this. The big red button was pressed to rebalance the ERXs and there was a problem reconnecting (I guess the BAS kept trying to get to the downed ERX instead of round robbining to the others) and I got blocked out. I hate to break the news to you.. But it's not just Bell who has such a protection mechanism in there systems... It is possible to lock your self out of almost any ISP if you do enough pppoe or DHCP requests... I have on a couple occasion had to call Telus to get the port reset when tweaking a router....This is by no means exclusive to Bell. It is an industry standard practice.
--
R.I.P Mom. |
|
