dslreports logo
site
 
    All Forums Hot Topics Gallery
spc

spacer




how-to block ads


Search Topic:
uniqs
19
share rss forum feed


Glen1
These Are The Good Ol' Days.
Premium,MVM
join:2002-05-24
GTA Canada
kudos:8
reply to masif

Re: Bell Canada Fibe25/10 can ping but cannot browse frequently

My question is: if Bell knows about this problem, when are they going to address it?


urbang33k

join:2010-02-13
Canada
kudos:1

said by Glen1:

My question is: if Bell knows about this problem, when are they going to address it?

agreed. I would love to know what exactly is it about the profile / port settings that cause this.

ruggs

join:2012-03-26
Ontario
reply to Glen1

I believe not all profiles work for everyone, as techs we're SUPPOSED to do a 'final test' but a lot of times this doesn't happen... Also the limited time we're there, the problem may not rear its ugly head...


urbang33k

join:2010-02-13
Canada
kudos:1

said by ruggs:

Also the limited time we're there, the problem may not rear its ugly head...

Thats just it, we can't be expected to wait around all day incase it MIGHT go for a crap.

I love to know if it's tied to Alcatel or Lucent equipment. Or a specific revision of one of the slot cards.
--
Opinions and ideas expressed in my post are my own and in no way represent those of Bell Canada Enterprises, Bell Canada, Bell TV, Bell Internet, Bell Mobility, Bell Technical Solutions, Expertech, or any other partners under the BCE umbrella.

themisa

join:2012-05-22

This ping works but browsing doesn't issue is Sagemcom specific.
Issue was definitely 'fixed' for me by switching over to a spare Cellpipe modem.



deekay0

join:2001-12-23
Toronto, ON

1 edit

said by themisa:

This ping works but browsing doesn't issue is Sagemcom specific.
Issue was definitely 'fixed' for me by switching over to a spare Cellpipe modem.

I also find that the CellPipe is a bit more stable. However, it seems that the CellPipe loses sync instead of the "ping works but browsing doesn't" issue that the Sagemcom had. At least the CellPipe self recovers quickly within a minute or two.

EDIT: some more background info and my two cents. I have TekSavvy 25/7 (obviously through Bell) and had stable service for quite some time. After a while I started suffering from almost daily DSL sync losses. I was sent a new Sagemcom modem and then discovered this "can ping but can't browse" issue. Between the two issues, the CellPipe modem's symptoms are easier to deal with. I suspect some change on Bell's equipment which is manifesting as these two different issues for these two different modems.

kovy

join:2009-03-26
kudos:8

said by deekay0:

said by themisa:

This ping works but browsing doesn't issue is Sagemcom specific.
Issue was definitely 'fixed' for me by switching over to a spare Cellpipe modem.

I also find that the CellPipe is a bit more stable. However, it seems that the CellPipe loses sync instead of the "ping works but browsing doesn't" issue that the Sagemcom had. At least the CellPipe self recovers quickly within a minute or two.

EDIT: some more background info and my two cents. I have TekSavvy 25/7 (obviously through Bell) and had stable service for quite some time. After a while I started suffering from almost daily DSL sync losses. I was sent a new Sagemcom modem and then discovered this "can ping but can't browse" issue. Between the two issues, the CellPipe modem's symptoms are easier to deal with. I suspect some change on Bell's equipment which is manifesting as these two different issues for these two different modems.

Well that depends since the Cellpipe firmware for wholesales was garbage would restart on its own. Some people tested without even pluggin the DSL.

themisa

join:2012-05-22

I am also with Teksavvy. Bell updated the firmware on the Cellpipe and the restarts are now gone, but that's besides the point.

Sagemcom issue clearly exists. It's hard to demonstrate to tech support since it doesn't affect ping and in some cases disappears in the time it takes to reach support, i.e. 30min.

How do we get Bell to address this globally?


kovy

join:2009-03-26
kudos:8

said by themisa:

I am also with Teksavvy. Bell updated the firmware on the Cellpipe and the restarts are now gone, but that's besides the point.

Sagemcom issue clearly exists. It's hard to demonstrate to tech support since it doesn't affect ping and in some cases disappears in the time it takes to reach support, i.e. 30min.

How do we get Bell to address this globally?

Both the Cellpipe and Sagemcom had this problem for me. How to fix this globally, no idea.