 | reply to TSI Martin
Re: [Cable] DHCP Outage Last couple of days, I've been getting random disconnects. I disconnect for 30 seconds, then reconnect again. Seems that something is rebooting, hence the reconnect.
Everything is fine (speed, ping etc) but random disconnects.
Any chance this is related to the DHCP issues...?
Located in Whitby. |
|
|
|
 sbrookPremium,Mod join:2001-12-14 Ottawa kudos:4 | No, not the DHCP issue ... it could be signal quality related, especially considering they seem to correspond with the change in weather!
Look at your modem logs ... you should be able to find them at 192.168.100.1 |
|
 | has anybody had any success with filing a complain with the CRTC? i just got a response from them:
"This is in response to your correspondence of December 26, 2011. The CRTC doesn't regulate the rates or quality of service provided by Internet service providers to its customers at the retail level (in your case TekSavvy). It has generally supported an increasingly competitive environment and believes it is in the service provider's best interest to address the needs and concerns of its current and potential customers. For your additional information, here is a link to our info sheet on Internet services: »www.crtc.gc.ca/eng/info_sht/t1003.htm Furthermore, your service provider is in the best position to evaluate whether it believes its provider or a competitor is involved in inappropriate behaviour, and if so, it can provide the Commission with evidence of any alleged wrongdoing and file a competitive dispute with the Commission. The CRTC cannot deal with customer complaints made on behalf of their service provider."
so yeah... |
|
 sbrookPremium,Mod join:2001-12-14 Ottawa kudos:4 | They seem to forget that it's ultimately the consumer who's getting the raw deal! |
|
 | reply to s_horty_s88 said by s_horty_s88:has anybody had any success with filing a complain with the CRTC? i just got a response from them:
"This is in response to your correspondence of December 26, 2011. The CRTC doesn't regulate the rates or quality of service provided by Internet service providers to its customers at the retail level (in your case TekSavvy). It has generally supported an increasingly competitive environment and believes it is in the service provider's best interest to address the needs and concerns of its current and potential customers. For your additional information, here is a link to our info sheet on Internet services: »www.crtc.gc.ca/eng/info_sht/t1003.htm Furthermore, your service provider is in the best position to evaluate whether it believes its provider or a competitor is involved in inappropriate behaviour, and if so, it can provide the Commission with evidence of any alleged wrongdoing and file a competitive dispute with the Commission. The CRTC cannot deal with customer complaints made on behalf of their service provider."
so yeah... I got the same email |
|
 | reply to TSI Martin What about getting the home/business numbers/emails of Rogers executives and harassing them. 
Calling and asking when this will be fixed. |
|
 c2rothPremium join:2006-04-26 Kitchener, ON kudos:2 Reviews:
·TekSavvy Cable
| reply to TSI Martin Does this outage include McNicoll users? I have been away from home but since Dec 22nd I have been unable to remote into my home server or my router. I get a strong feeling that something is wrong with the internet. Closest major intersection is Warden & Steeles.
Can anyone please confirm. |
|
 | reply to TSI Martin Iam slighty luckier then others in that i do have the sync timing and dhcp issues but they resolve within 3 min so iam not down for long.
That and it only seems to happen once per day at most.
Annoying yes but hardly the worst i seen..remeber those days with rogers being effective run by that company in the states as far as tech support. |
|
 | reply to TSI Martin Hey guys, I don't live in the area, but have been following your plight. I find the CRTC's answer to you to be pretty disgusting. Looks like it's time for a visit to your local MP's since the CRTC is being funded by your tax dollars, and is meant to be serving your interests. I know I will at the first sign of trouble!
Best of luck! |
|
 | reply to TensionX Complaining to CRTC is not gonna work as they are not going to deal with end user. The better way is to have a class action sue agsinst both TSI and Rogers to pressure them. Just a matter of time I guess. |
|
 sbrookPremium,Mod join:2001-12-14 Ottawa kudos:4 Reviews:
·TekSavvy Cable
| reply to TSI Martin The CRTC is the agency that needs to deal with these issues. Suing TekSavvy and Rogers won't work. Any judge is going to say this is a matter in a regulated industry and throw it at the CRTC.
Yup, the CRTC will need direction but won't take it from us ... therefore we must go to the Industry Ministry ... and the Minister ... and put pressure on them to direct the CRTC to deal with the consumer level problems being caused by the interface of the incumbent and third party internet providers which they regulate. |
|
 c2rothPremium join:2006-04-26 Kitchener, ON kudos:2 Reviews:
·TekSavvy Cable
| reply to c2roth said by c2roth:Does this outage include McNicoll users? I have been away from home but since Dec 22nd I have been unable to remote into my home server or my router. I get a strong feeling that something is wrong with the internet. Closest major intersection is Warden & Steeles.
Can anyone please confirm. Turns out my issue was pretty simple. My cable modem died over the Christmas holidays while I was gone. So no internet at home until I get the replacement from TekSavvy. |
|
 | reply to Pharaoh11 said by Pharaoh11:Iam slighty luckier then others in that i do have the sync timing and dhcp issues but they resolve within 3 min so iam not down for long.
That and it only seems to happen once per day at most.
Annoying yes but hardly the worst i seen..remeber those days with rogers being effective run by that company in the states as far as tech support. Would seem no sooner do i say that then the i get knocked off line for over 24 hours do to dhcp issues.
Fortunately it seems to be fixed now. |
|