Comcast / Motorola sb5100 cable modem dropping connection...

Comcast / Motorola sb5100 cable modem dropping connection...
NewsGroups | Search | Tools
User Password
Register Now! Lost Password?
 comp.dcom.modems.cable  Post an article  get this group's latest topics as an RSS feed add this group's latest topics to your My MSN content add this group's latest topics to your My Yahoo content  add this group's latest topics to your Google content  YahooMyWeb Yahoo!  Google Google  Windows Live Favorites Windows Live  del.icio.us del.icio.us  digg digg  Add to Netscape Netscape
Subject Author Date
Comcast / Motorola sb5100 cable modem dropping connection... b4serenity 05-10-2006
Posted by on May 11, 2006, 3:28 pm
If you were  Registered and logged in, you could reply and use other advanced thread options
Well, I've been offline again for the last few hours again. If those
numbers are good then I THINK I have basically eliminated the signal
/wiring problem... so it's probably my modem?


Pure Networks
Posted by Dave on May 11, 2006, 3:45 pm
If you were  Registered and logged in, you could reply and use other advanced thread options
I had a similar situation a couple years ago. Everything was fine and then
it'd go offline for 15 minutes to a few hours. Of course, when I reported
it they'd schedule a service call and all would be well by the time he
showed up 2 days later. Later another outage and the same problem. I
finally got so frustrated that I went to the local Comcast office, spoke to
the manager and described my frustration. She contacted the local
maintenance manager who called me to discuss it. They finally realized
they had an amp with an intermittent noise problem. They changed the amp
and it hasn't happened since.

If I were you, I'd be escalating the issue and talking to a higher level of
management. In that kind of situation the normal trouble reporting process
is unlikely to work and you'll have to become the squeaky wheel. I'd keep
escalating until you get someone's attention.

That's just my two cents worth.......


> Well, I've been offline again for the last few hours again. If those
> numbers are good then I THINK I have basically eliminated the signal
> /wiring problem... so it's probably my modem?
>



Posted by on May 11, 2006, 5:27 pm
If you were  Registered and logged in, you could reply and use other advanced thread options
I just talked with others on my street w/ comcast net service and
they've been fine. So, now that, with the fairly OK signal strength
shown, has me thinking more then ever that it's probably the modem.
I'll give it a shot and see if that does the trick. If it doesn't fix
it then s the ball will be back in comcast's court.


Posted by Ed Nielsen on May 11, 2006, 8:19 pm
If you were  Registered and logged in, you could reply and use other advanced thread options
I had a situation that started around the end of January that nobody
could figure out. Talked with my assistant state engineer a few times
about it and nothing made any sense. Levels were great and S/N was
great also. Download speeds suddenly dropped to about 1/3 of what they
were previously. Swapped the modem out with one I had previously with
no change. Upload was not affected, just download. Went on for a
couple of months. Eventually, a Chief Tech in Indiana mentioned
something. I bought a new cable modem and voila, back in business.


CIAO!

Ed N.

b4serenity@gmail.com wrote:
> I just talked with others on my street w/ comcast net service and
> they've been fine. So, now that, with the fairly OK signal strength
> shown, has me thinking more then ever that it's probably the modem.
> I'll give it a shot and see if that does the trick. If it doesn't fix
> it then s the ball will be back in comcast's court.
>

Posted by on May 12, 2006, 7:56 pm
If you were  Registered and logged in, you could reply and use other advanced thread options
No new modem yet but here's the latest error log; Does this indicate a
bad signal from Comcast or still possibly a Modem problem? Any help
appreciated!!

Time         Priority         Code         Message
2006-05-12 17:46:54         3-Critical         R002.0         No Ranging Response received -
T3 time-out
2006-05-12 17:46:44         3-Critical         T001.0         SYNC Timing Synchronization
failure - Failed to acquire QAM/QPSK symbol timing
2006-05-12 17:46:24         3-Critical         R002.0         No Ranging Response received -
T3 time-out
2006-05-12 17:46:04         3-Critical         R007.0         Unicast Ranging Received Abort
Response - Re- initializing MAC
2006-05-12 17:45:47         3-Critical         R002.0         No Ranging Response received -
T3 time-out
2006-05-12 17:45:42         3-Critical         T001.0         SYNC Timing Synchronization
failure - Failed to acquire QAM/QPSK symbol timing
2006-05-12 17:45:21         3-Critical         R002.0         No Ranging Response received -
T3 time-out
2006-05-12 17:45:07         3-Critical         R007.0         Unicast Ranging Received Abort
Response - Re- initializing MAC
2006-05-12 17:44:49         3-Critical         R002.0         No Ranging Response received -
T3 time-out
2006-05-12 17:44:43         3-Critical         R007.0         Unicast Ranging Received Abort
Response - Re- initializing MAC
2006-05-12 17:41:28         3-Critical         R005.0         Started Unicast Maintenance
Ranging - No Response received - T3 time-out
2006-05-12 13:25:23         3-Critical         T001.0         SYNC Timing Synchronization
failure - Failed to acquire QAM/QPSK symbol timing
2006-05-12 13:25:19         3-Critical         T002.0         SYNC Timing Synchronization
failure - Failed to acquire FEC framing
2006-05-12 13:25:19         3-Critical         T001.0         SYNC Timing Synchronization
failure - Failed to acquire QAM/QPSK symbol timing
2006-05-12 13:25:14         3-Critical         T002.0         SYNC Timing Synchronization
failure - Failed to acquire FEC framing
2006-05-12 13:25:12         3-Critical         T001.0         SYNC Timing Synchronization
failure - Failed to acquire QAM/QPSK symbol timing
2006-05-12 13:25:12         3-Critical         T002.0         SYNC Timing Synchronization
failure - Failed to acquire FEC framing
2006-05-12 13:25:11         3-Critical         T001.0         SYNC Timing Synchronizatio


Similar ThreadsPosted
Motorola SB5100 cable modem - is it really dead? September 30, 2008, 12:43 pm
Motorola SB5100 March 14, 2005, 9:25 am
Motorola SB5100 Transformer Specs? October 28, 2007, 12:15 pm
Networking Comcast Motorola SB5101 Surfboard Cable Modem.... December 19, 2005, 11:13 pm
Modem Keeps Dropping Signal December 15, 2005, 1:02 am
Comcast Firmware upgrade on SB5100 June 1, 2005, 11:20 am
Using the Motorola DCT6200 receiver w/ comcast.net October 26, 2006, 11:54 pm
FA: nice Motorola Surfboard SB5101 cable modem lightly used in box complete July 18, 2007, 8:28 pm
USB connection to cable modem with no NIC August 12, 2007, 10:39 pm
Howto on Cable Modem Connection February 10, 2006, 2:16 pm

other useful resources:
The Federal Communications Commission (FCC)
Telecommunications Industry Association
Electronic and Software Security Products and Services
International Telecommunication Union

Custom CGI Perl and PHP programming by 1-Script.com

Contact Us | Privacy Policy
The site map in XML format XML site map