Reply
Visitor
Posts: 3
Registered: ‎04-09-2007

Re: Intermittent drops - Motorola sbg6580

I too had no issues with the 3.3 software code and a nice quite period with no errors or drops. I am now rolled back to the version 3.1 code and am getting the daily drops requiring a router reboot.  I have been plagued by this issue for at least six months and am tired of the Comcast run around in getting it resolved.

 

First one Comcast help desk person tried to tell me that Comcast does not do firmware upgrades.  NOT TRUE since upgrade are done for any modem connected to their network and it is required by the DOCSIS 3.0 Standards.

 

Next a smart Comcast help desk person attempted to get me to purchase a support contract and pay them to do the upgrade!  I don’t think I should have to pay for the service TWICE!

 

I do like the idea of a class action law suit. We are paying for service that we are not getting or at best are getting limited, poor service.

 

How about a little transparency in what the issue is and what Comcast is trying to do to correct the problem.  Could you maybe use a little disk space and create a web site listing known issues and the current status of the fix?  Doesn’t seem like too much to ask of a service provider.

Contributor
jchaoz
Posts: 5
Registered: ‎11-28-2011

Re: Intermittent drops - Motorola sbg6580

[ Edited ]

I had the same issue. I have SBG901. This is the second one sent by Moto. The same issues remained. I posted before and thought it was resovled after using a new modem. I was wrong. It started to flare up in less than 2 weeks. I am now thinking it is comcast's problem.

Contributor
Posts: 8
Registered: ‎01-26-2008

Re: Intermittent drops - Motorola sbg6580

Notice the nice quiet period between February 15th - February 29th.  That's with version 3.3 installed.  Back to the every other day reboot of the router. 

 

Sun Mar 04 03:14:52 2012 Notice (6)TLV-11 - unrecognized OID;CM-MAC=1c:14:48:b1:d6:74;CMTS-MAC=00:01:5c:22:75:4f;CM-QOS=1.1;CM-VER=3.0;
Sat Mar 03 21:21:09 2012 Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=1c:14:48:b1:d6:74;CMTS-MAC=00:01:5c:22:75:4f;CM-QOS=1.1;CM-VER=3.0;
Time Not EstablishedCritical (3)No Ranging Response received - T3 time-out 
Sat Mar 03 11:14:47 2012 Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=1c:14:48:b1:d6:74;CMTS-MAC=00:01:5c:22:75:4f;CM-QOS=1.1;CM-VER=3.0;
Wed Feb 29 13:24:32 2012 Critical (3)SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=1c:14:48:b1:d6:74;CMTS-MAC=00:01:5c:22:75:4f;CM-QOS=1.1;CM-VER=3.0;
Wed Feb 29 13:24:29 2012 Critical (3)SYNC Timing Synchronization failure - Failed to receive MAC SYNC frame within time-out period;CM-MAC=1c:14:48:b1:d6:74;CMTS-MAC=00:01:5c:22:75:4f;CM-QOS=1.1;CM-VER=3.0;
Time Not EstablishedCritical (3)No Ranging Response received - T3 time-out 
Wed Feb 15 22:54:08 2012 Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=1c:14:48:b1:d6:74;CMTS-MAC=00:01:5c:22:75:4f;CM-QOS=1.1;CM-VER=3.0;
Time Not EstablishedCritical (3)No Ranging Response received - T3 time-out 
Tue Feb 14 02:50:05 2012 Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=1c:14:48:b1:d6:74;CMTS-MAC=00:01:5c:22:75:4f;CM-QOS=1.1;CM-VER=3.0;
Time Not EstablishedCritical (3)No Ranging Response received - T3 time-out 
Sat Feb 11 08:03:02 2012 Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=1c:14:48:b1:d6:74;CMTS-MAC=00:01:5c:22:75:4f;CM-QOS=1.1;CM-VER=3.0;
Time Not EstablishedCritical (3)No Ranging Response received - T3 time-out 
Fri Feb 10 02:12:27 2012 Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=1c:14:48:b1:d6:74;CMTS-MAC=00:01:5c:22:75:4f;CM-QOS=1.1;CM-VER=3.0;
Time Not EstablishedCritical (3)No Ranging Response received - T3 time-out 
Thu Feb 09 01:06:36 2012 Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=1c:14:48:b1:d6:74;CMTS-MAC=00:01:5c:22:75:4f;CM-QOS=1.1;CM-VER=3.0;
Time Not EstablishedCritical (3)No Ranging Response received - T3 time-out 
Sun Feb 05 08:57:40 2012 Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=1c:14:48:b1:d6:74;CMTS-MAC=00:01:5c:22:75:4f;CM-QOS=1.1;CM-VER=3.0;
Time Not EstablishedCritical (3)No Ranging Response received - T3 time-out 
Time Not EstablishedCritical (3)No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=1c:14:48:b1:d6:74;CMTS-MAC=00:01:5c:22:75:4f;CM-QOS=1.0;CM-VER=3.0;
Time Not EstablishedCritical (3)No Ranging Response received - T3 time-out 
Time Not EstablishedCritical (3)No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=1c:14:48:b1:d6:74;CMTS-MAC=00:01:5c:22:75:4f;CM-QOS=1.0;CM-VER=3.0;
Time Not EstablishedCritical (3)No Ranging Response received - T3 time-out 
Sat Feb 04 02:34:30 2012 Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=1c:14:48:b1:d6:74;CMTS-MAC=00:01:5c:22:75:4f;CM-QOS=1.1;CM-VER=3.0;
Sat Feb 04 02:33:57 2012 Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=1c:14:48:b1:d6:74;CMTS-MAC=00:01:5c:22:75:4f;CM-QOS=1.1;CM-VER=3.0;
Time Not EstablishedCritical (3)No Ranging Response received - T3 time-out 
Fri Feb 03 20:11:43 2012 Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=1c:14:48:b1:d6:74;CMTS-MAC=00:01:5c:22:75:4f;CM-QOS=1.1;CM-VER=3.0;
Fri Feb 03 02:38:44 2012 Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=1c:14:48:b1:d6:74;CMTS-MAC=00:01:5c:22:75:4f;CM-QOS=1.1;CM-VER=3.0;
Time Not EstablishedCritical (3)No Ranging Response received - T3 time-out 
Tue Jan 31 12:10:48 2012 Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=1c:14:48:b1:d6:74;CMTS-MAC=00:01:5c:22:75:4f;CM-QOS=1.1;CM-VER=3.0;
Tue Jan 31 03:33:04 2012 Critical (3)Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=1c:14:48:b1:d6:74;CMTS-MAC=00:01:5c:22:75:4f;CM-QOS=1.1;CM-VER=3.0;
Mon Jan 30 08:09:01 2012 Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=1c:14:48:b1:d6:74;CMTS-MAC=00:01:5c:22:75:4f;CM-QOS=1.1;CM-VER=3.0;
Sun Jan 29 18:21:28 2012 Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=1c:14:48:b1:d6:74;CMTS-MAC=00:01:5c:22:75:4f;CM-QOS=1.1;CM-VER=3.0;
Sun Jan 29 02:17:12 2012 Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=1c:14:48:b1:d6:74;CMTS-MAC=00:01:5c:22:75:4f;CM-QOS=1.1;CM-VER=3.0;
Fri Jan 27 19:35:19 2012 Critical (3)Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=1c:14:48:b1:d6:74;CMTS-MAC=00:01:5c:22:75:4f;CM-QOS=1.1;CM-VER=3.0;
Time Not EstablishedCritical (3)No Ranging Response received - T3 time-out 
Fri Jan 27 14:02:12 2012 Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=1c:14:48:b1:d6:74;CMTS-MAC=00:01:5c:22:75:4f;CM-QOS=1.1;CM-VER=3.0;
Wed Jan 25 11:36:44 2012 Critical (3)Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=1c:14:48:b1:d6:74;CMTS-MAC=00:01:5c:22:75:4f;CM-QOS=1.1;CM-VER=3.0;
Tue Jan 24 04:41:10 2012 Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=1c:14:48:b1:d6:74;CMTS-MAC=00:01:5c:22:75:4f;CM-QOS=1.1;CM-VER=3.0;
Mon Jan 23 16:22:42 2012 Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=1c:14:48:b1:d6:74;CMTS-MAC=00:01:5c:22:75:4f;CM-QOS=1.1;CM-VER=3.0;
Mon Jan 23 13:28:36 2012 Critical (3)SYNC Timing Synchronization failure - Failed to receive MAC SYNC frame within time-out period;CM-MAC=1c:14:48:b1:d6:74;CMTS-MAC=00:01:5c:22:75:4f;CM-QOS=1.1;CM-VER=3.0;
Sun Jan 22 09:07:26 2012 Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=1c:14:48:b1:d6:74;CMTS-MAC=00:01:5c:22:75:4f;CM-QOS=1.1;CM-VER=3.0;
Sat Jan 21 17:58:17 2012 Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=1c:14:48:b1:d6:74;CMTS-MAC=00:01:5c:22:75:4f;CM-QOS=1.1;CM-VER=3.0;
Thu Jan 19 11:05:49 2012 Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=1c:14:48:b1:d6:74;CMTS-MAC=00:01:5c:22:75:4f;CM-QOS=1.1;CM-VER=3.0;
Wed Jan 18 22:56:20 2012 Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=1c:14:48:b1:d6:74;CMTS-MAC=00:01:5c:22:75:4f;CM-QOS=1.1;CM-VER=3.0;
Fri Jan 13 05:19:08 2012 Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=1c:14:48:b1:d6:74;CMTS-MAC=00:01:5c:22:75:4f;CM-QOS=1.1;CM-VER=3.0;
Thu Jan 12 00:48:35 2012 Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=1c:14:48:b1:d6:74;CMTS-MAC=00:01:5c:22:75:4f;CM-QOS=1.1;CM-VER=3.0;
Wed Jan 11 06:57:48 2012 Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=1c:14:48:b1:d6:74;CMTS-MAC=00:01:5c:22:75:4f;CM-QOS=1.1;CM-VER=3.0;
Sat Jan 07 12:12:14 2012 Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=1c:14:48:b1:d6:74;CMTS-MAC=00:01:5c:22:75:4f;CM-QOS=1.1;CM-VER=3.0;
Time Not EstablishedCritical (3)No Ranging Response received - T3 time-out 
Thu Jan 05 02:59:23 2012 Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=1c:14:48:b1:d6:74;CMTS-MAC=00:01:5c:22:75:4f;CM-QOS=1.1;CM-VER=3.0;
Tue Jan 03 22:38:03 2012 Critical (3)Resetting the cable modem due to docsDevResetNow
Tue Jan 03 22:17:26 2012 Critical (3)Resetting the cable modem due to docsDevResetNow
Mon Jan 02 21:23:47 2012 Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=1c:14:48:b1:d6:74;CMTS-MAC=00:01:5c:22:75:4f;CM-QOS=1.1;CM-VER=3.0;
Sat Dec 31 02:23:39 2011 Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=1c:14:48:b1:d6:74;CMTS-MAC=00:01:5c:22:75:4f;CM-QOS=1.1;CM-VER=3.0;
Fri Dec 30 17:42:17 2011 Critical (3)Resetting the cable modem due to docsDevResetNow
Fri Dec 30 17:41:07 2011 Critical (3)Resetting the cable modem due to docsDevResetNow
Time Not EstablishedCritical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=1c:14:48:b1:d6:74;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Time Not EstablishedCritical (3)SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=1c:14:48:b1:d6:74;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Contributor
hax0rmort
Posts: 12
Registered: ‎02-07-2012

Re: Intermittent drops - Motorola sbg6580

Before I was upgraded to 3.3.1 and then back down, my disconnects were about once a day. Now I can't make it past 10 hours without a reset. COMCAST WAKE UP AND HELP US
New Visitor
FedUpWitC0mcast
Posts: 1
Registered: ‎03-04-2012

Re: Intermittent drops - Motorola sbg6580

Where are all of you guys located?  I've NEVER received a single update from Comcast and experience a drop every single day.

 

These guys are theives.  If I had FiOS available in my area I would leave you guys in a heartbeat.

 

I want my modem updated now!

Visitor
Deirelig60
Posts: 2
Registered: ‎02-06-2012

Re: Intermittent drops - Motorola sbg6580

Yep, same ole, same ole.... ever since the rollback the THEIVES at Comcast are still rebooting/dropping signal on a daily basis.  I concur with all on the thread... when they left the firmware upgrade alone... things ran smoothly... so Comcast Steve....any developments on the Comcast front regards the bugs with firmware version 3.3?  Keep us apprised... Ho hum....:smileycry:

 

Contributor
nhbragg
Posts: 7
Registered: ‎01-28-2012

Re: Intermittent drops - Motorola sbg6580

I also got rolled back to 3.1

 

I am also back to having the modem in bridging mode to a Linksys WRT610N.  Modem would become unstable with 4 wireless devices and 2 lan devices connected.  Bridging mode is at least stable as long as I have a reboot every 24 hours of the router/modem.

 

I was able to run the modem by itself during the whole 3.3 firmware timeframe with no reboots and no downtime.

 

Hopefully we see an upgrade sooner than later.

Contributor
hax0rmort
Posts: 12
Registered: ‎02-07-2012

Re: Intermittent drops - Motorola sbg6580

I'm in new castle, Delaware, a suburb of Greater Philadelphia area. It's a shame this thread has basically become a one sided assault against Comcast and/or Motorola. It isn't my intent to simply complain, I'd like to be HEARD or at least acknowledged. ( Lord knows simply posting troubleshooting codes isn't doing anything, no one is listening) Simply pointing the finger back and forth to the (other) guys isn't cutting it. Who do we have to service to get some decent support around here? Someone step up and take responsibility for this cluster. - one angry vet
Contributor
dbottoms
Posts: 18
Registered: ‎02-12-2012

Re: Intermittent drops - Motorola sbg6580

For what its worth I'm still at 3.3.1 and not a single disconnect or any noticable problems at all so far.  I think I have been upgraded now for a full week and 3 days.  I have not power cycled the modem and am nervous if I do that I might get downgraded.

Contributor
briansez
Posts: 13
Registered: ‎12-19-2011

Re: Intermittent drops - Motorola sbg6580

Same here.... on 3.3 for nearly 2 weeks with no interruptions whatsoever.  Crossing my fingers that I never need to power-cycle until Comcast and Motorola come up with the next iteration.

Visitor
MDRL
Posts: 4
Registered: ‎01-13-2012

Re: Intermittent drops - Motorola sbg6580

 I have been searching for solutions to this same problem... Losing connection 4-5 times a day... SB6580 just stops on it's own and reboots itself... Tried solutions in this forum before contacting Comcast. OK.. 1st rep readily understood that my question about firmware was beyond him... He switched me to the next step... Next guy understood but still was not fully informed about this issue.. However he sent new info to my modem, here is what it recorded

 

 Wed Mar 07 15:51:27 2012    Notice (6)   TLV-11 - unrecognized OID;CM-MAC=2c:9e:5f:c9:6a:29;CMTS-MAC=00:01:5c:22:04:0f;CM-QOS=1.1;CM-VER=3.0;   Wed Mar 07 15:50:38 2012    Critical (3)   Resetting the cable modem due to docsDevResetNow   

 

 

 

He then referred and gave me the number to call Motorola... Ok I will play along... Actually got a guy who knew about this issue.. Same as everyone else's answer, You can only get firmware updates from your ISP. But he did tell me that Motorola has given Comcast the firmware updates to push out... Comcast did push them and had issues that effected more models of Motorola modems in a negative way, so Comcast retracted or "undid" the "push" ... 

 

Anyway... I haven't had a dropped connection in almost 12 hours and speed is much better! Still have firmware 3.1... 

Contributor
Posts: 10
Registered: ‎01-16-2007

Re: Intermittent drops - Motorola sbg6580

[ Edited ]

 

Motorola will need to fix their problems again....  Personally, I would return this device or make motorola buy it back since this issue affects multiple cable operators out there. 

New Visitor
Scardycat
Posts: 1
Registered: ‎03-08-2012

Re: Intermittent drops - Motorola sbg6580

I've had this issue as well.  I bought the modem ($170 at Best Buy) Nov-2011 and started having issues sometime in Feb-2012.  At first I thought it was me blowing past my 250 cap limit...but the issue persisted and I found this thread and had all the symptoms everyone mentioned.  I've gone through both the 3.1 and 3.3 update and neither worked for me.  Strangely, ethernet was the one that gave me disconnections, wireless was completely fine.  I called tech - no dice.  I can't return the modem as it was months past.

 

I got so fed up with this that I've actually switched to another ISP.  It gave me faster speed and cheaper per-month cost with no activation fees.  Total difference.  Problem solved.  I suggest if you're out of options, you should do the same.

Contributor
SSubZero
Posts: 18
Registered: ‎12-16-2011

Re: Intermittent drops - Motorola sbg6580

Welp, I've been downgraded again, and the modem is very unhappy.  

 

This is beyond unreasonable.  Why are they bulk-downgrading everyone over some issue that is not even being explained?  My connection was 100%, absolutely **perfect** with 3.3.1 and now back to 3.1 and back to the disconnects.

 

I have a midterm coming up that is online.  Am I going to have to find somewhere else to take it? 

 

Thu Mar 08 19:12:25 2012   Notice (6) 

 TLV-11 - unrecognized OID;CM-MAC=70:7e:43:4f:5a:bb;CMTS-MAC=00:01:5c:33:d0:ce;CM-QOS=1.1;CM-VER=3.0;

New Visitor
Nickb_7
Posts: 2
Registered: ‎03-08-2012

Re: Intermittent drops - Motorola sbg6580

So...I just bought this modem yesterday (spent hundreds of dollars already renting from Comcast), the Geek at Best Buy gave me no warning about this. I also took it with me when I returned my rented modem to make sure it would work. My local Comcast employees gave me no warning about this. Of course, 1 quick Google search and I would've learned easily, so shame on me. My question is, should I keep it or return it and get something that works for now? I don't know how long you guys have been fighting this problem, but it seems to have been for a while now... RETURN IT or KEEP IT?.... That is the question.

Contributor
SSubZero
Posts: 18
Registered: ‎12-16-2011

Re: Intermittent drops - Motorola sbg6580

I'm not sure what I would recommend.  When the newer firmware was on, it worked perfectly.  With the current "on again/off again" version it's unstable and unreliable.  Apparently Comcast prefers we be unstable.

 

The sad thing is after a rant post I did a while back Comcast called me themselves and assigned me a "case manager" who I talked to exactly twice.  I don't have the guy's number anymore (I didn't think I would need it) and now here I am back to square one.  

 

What bothers me the most is I now know Comcast can and will arbitrarily change firmwares on a whim and there's no way to stop it.  They also apparently can't upgrade from A to B to C, and instead have to go from A to B, then B to A to go from A to C.  This modem is from 2009 why are we having this sort of shenanigans?  Of course now we have to just wait for someone to say something, then wait a couple more weeks for something to actually happen.

Regular Contributor
MidnightCat
Posts: 37
Registered: ‎01-15-2010

Re: Intermittent drops - Motorola sbg6580

@Nick If it's still within the time frame of returning the gateway, you probably should, unless you like to wait. :smileyhappy:

Cable Expert
i-am-nerdburg
Posts: 10,052
Registered: ‎06-27-2009

Re: Intermittent drops - Motorola sbg6580


Nickb_7 wrote:

My question is, should I keep it or return it and get something that works for now? I don't know how long you guys have been fighting this problem, but it seems to have been for a while now... RETURN IT or KEEP IT?.... That is the question.


Us cable nerds hate gateway devices - so RETURN IT. Get a modem like the Moto 6120 and any dual band gigabit N router.

Cable Expert
i-am-nerdburg
Posts: 10,052
Registered: ‎06-27-2009

Re: Intermittent drops - Motorola sbg6580


hax0rmort wrote:
I'm in new castle, Delaware, a suburb of Greater Philadelphia area. It's a shame this thread has basically become a one sided assault against Comcast and/or Motorola. It isn't my intent to simply complain, I'd like to be HEARD or at least acknowledged. ( Lord knows simply posting troubleshooting codes isn't doing anything, no one is listening) Simply pointing the finger back and forth to the (other) guys isn't cutting it. Who do we have to service to get some decent support around here? Someone step up and take responsibility for this cluster. - one angry vet

Have you read the whole thread? There has been official acknowledgment from Comcast that there is a problem and they are working on getting it resolved. They need to get everything tested before they roll it out to everyone, otherwise it could very well make things worse or create different problems. I can understand everyone's frustration, it would be nice if Comcast could compensate you somehow.

New Visitor
Starts
Posts: 1
Registered: ‎03-09-2012

Re: Intermittent drops - Motorola sbg6580

I've been reading through these posts and came accross yours.  I am having the same issues as most of the others with trying to get my firmware updated on my SBG6580.  If you do not mind could you tell me how you gained root access to the Motorola SBG6580?  When I configured mine, I changed my WAN IP to 192.168.115.1.  Not sure of I need to reset it back to default.  I would like to check out the extra info on my gateway.

 

Thanks

Contributor
dbottoms
Posts: 18
Registered: ‎02-12-2012

Re: Intermittent drops - Motorola sbg6580

For what its worth, I just got downgraded back to SBG6580-3.1.0.0-GA-07-180-NOSH just now at 5:17pm EST.  I had 2 weeks and 6 hours of uninterrupted service with the 3.3 firmware. I know Comcast claims there are "issues" with the 3.3 also and is working on this but with my not seeing any problems as far as I know with my 3.3x I can't help but feel let down Comcast choose to downgrade me back to a known problem version.  Or at least give me the option to choose. 

 

I found this in my log after my modem self-booted, most likely a push from Comcast...

 

Time      Priority      Description
 Fri Mar 09 17:07:43 2012       Notice (6)      TLV-11 - unrecognized OID;CM-MAC=00:23:ed:fa:2e:b9;CMTS-MAC=00:01:5c:31:bc:49;CM-QOS=1.1;CM-VER=3.0;
 Fri Mar 09 00:55:41 2012       Critical (3)      Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:23:ed:fa:2e:b9;CMTS-MAC=00:01:5c:31:bc:49;CM-QOS=1.1;CM-VER=3.0;
 Time Not Established      Critical (3)      No Ranging Response received - T3 time-out 

 

This is identical to the disconnectivity being reported as far as I can tell.

 

I now anxiously await the new solution with most of you.  Come on ComcastSteve don't let us down !  :smileyhappy:

Contributor
dbottoms
Posts: 18
Registered: ‎02-12-2012

Re: Intermittent drops - Motorola sbg6580

[ Edited ]

@starts -- to gain access to your modem go to this address:  http://http://192.168.100.1/ and enter your username and password which should be located in your user manual and possibly on a sticker on your modem.  The default username was  admin  and the default password was   motorola    as I recall.  Strongly recommend changing those default values of course in case any hackers are lurking.  If these instructions don't work you'll have to call Motorola.  Good luck.

 

@Nickb_7 -- I'd return it and get what Nerdburg said.  Comcast been chaising this red herrin for many months.  Trust me the disconnectivity sucks so badly as you can probably tell from the many posts. 

Contributor
wzeallor
Posts: 14
Registered: ‎01-07-2012

Re: Intermittent drops - Motorola sbg6580

I share live shows over bittorrent and, though I had no drops, with 3.3 installed and with the bittorrent client open and sharing I could do nothing on the internet and could not connect to the other devices on my network. 3.1 does not have this problem.

New Visitor
Posts: 2
Registered: ‎03-06-2007

Re: Intermittent drops - Motorola sbg6580

You can add my name to the list of suckers who bought this modem with the hopes of increased speed, consolidated equipment, and of course reliable service without giving more money to the cable company.  The reason Motorola will not upgrade the firmware is the cable companies are who runs the standards organization and the manufactures are required to agree to allow only the service providers to patch the firmware.  Can't wait for 5G wireless to be release then I will just cut the cable.

Contributor
dbottoms
Posts: 18
Registered: ‎02-12-2012

Re: Intermittent drops - Motorola sbg6580

@wddowning -- 5G wireless theoretically can reach 1Gbps; but its real advantage will be greatly improved serices and abilities like new compression that can funnel more data down that pipe.  But in my very humble opinion cellular will be many years -- if not decades before it gives any serious competition to land option.  Future Docsys specifications far and away exceeds anything cellular could hope to offer.  And Docsys has not even reached its theoretical cap yet.  Sorry to see another brother affected by this gateway issue.

New Visitor
Nickb_7
Posts: 2
Registered: ‎03-08-2012

Re: Intermittent drops - Motorola sbg6580

Thanks for all of your advice. I will be returning mine on Monday and I will mostly likely do as Nerdburg suggested. Thanks again!
Contributor
Posts: 8
Registered: ‎01-26-2008

Re: Intermittent drops - Motorola sbg6580

I bought mine last year and tried to find a way to return it to motorola but have you ever tried to use their website?  It's impossible.  If anyone has any tips or links to customer service at motorola please share them.

New Visitor
peterllam
Posts: 1
Registered: ‎03-11-2012

Re: Intermittent drops - Motorola sbg6580

I randomly had drops about once a day and it was usually all around the same time (midnight), but after last night, the modem would drop the connection every 10 minutes and then reboots itself. Returning the modem to default seems to worsen the problem as it's now dropping the connection and rebooting every 5-6 minutes. 

I've had more problems with this modem over the last few months than I've had with AT&T over the last 6 years. Decided to give up on this modem and ordered a new modem along with a new router.

Contributor
Posts: 8
Registered: ‎10-07-2007

Re: Intermittent drops - Motorola sbg6580

I have been having random drops as well and I am using this exact modem as a router. My firmware version is 3.1.0.

 

Is there any way we can upgrade the firmware ourselves?

 

Why is Comcast inflicting pain on its customers?

Connection Expert
EG
Posts: 40,205
Registered: ‎12-24-2003

Re: Intermittent drops - Motorola sbg6580


devsk wrote:

 

Is there any way we can upgrade the firmware ourselves?

 


As has been posted in this thread before, the answer is no.

New Visitor
GeraldineA
Posts: 1
Registered: ‎03-13-2012

Re: Intermittent drops - Motorola sbg6580

Hi guys,

 

I had problems with the motorola SGB6580 with the SBG6580-3.1.0.0 since I bought it three weeks ago.

This modem was recommended by the tec guy who install the cable at the house!

But, like the others, I have those strange logs:

 

TLV-11 - unrecognized OID;CM-MAC=a4:7a:a4:35:42:35;CMTS-MAC=00:01:5c:23:c1:06;CM-QOS=1.1;CM-VER=3.0; or  No Ranging Response received - T3 time-out

or

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=a4:7a:a4:35:42:35;CMTS-MAC=00:01:5c:23:c1:06;CM-QOS=1.1;CM-VER=3.0;

or No UCDs Received - Timeout;;CM-MAC=a4:7a:a4:35:42:35;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;

or

SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=a4:7a:a4:35:42:35;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;

 

I contacted Comcast and they said I have to contact Motorola! Great!

So, after spending hours on reading this thread +the multiple ones related to the same problem with the same modem, I'm decided to just return that product that doesn't work with Comcast.

I still think it is a bumer that the modem is listed and recommended by Comcast.

Good luck to you all.

Géraldine


Visitor
Posts: 1
Registered: ‎06-25-2006

Re: Intermittent drops - Motorola sbg6580

tldr - I have this problem too and Comcast's customer service seems intentionally designed to inspire rage.  They have had the new version of the software from Motorola for at least 2 weeks for testing.

 

Nov. 2011 - Bought modem, installed.  It worked ok, but from day 1 had the occasional drops/resets.

Early Feb. 2012 - Started researching problem, tried several solutions that faild.  Found these forums.

 

2/7/2012 - Emailed we_can_help@comcast.com.  Got a callback that same day, explained problem to someone who understood what I was talking about.  Got an appointment for a tech to visit my home.

 

2/8/2012 - Tech showed up, did all the standard replacement of cable ends, but of course didn't solve my problem because a tech can't.

 

2/9/2012 - They individually updated me with the 3.3 firmware!  I was thinking "Comcast service is fine, don't know why folks are complaining.  They did what I asked, quickly."

 

2/9 - 2/??/2012 - THINGS WORK FLAWLESSLY, 0 DROPS/RESETS.

 

2/27 - After experiencing a couple of drops, I happen to look at modem details and see that they have reset my firmware.

 

2/27 - Decided to try chat support.  First chat support person tried to tell me that I had to get firmware from Motorola.  While I tried to explain that this was not the case for this issue, support person INTENTIONALLY RESET MY MODEM to cut me off (I was completely polite throughout the chat).

 

Second chat person accepted that there was nothing they could do and asked me to call Comcast.

 

Called Comcast, who after ascertaining that my modem lights were on, sent me to paid support.  I hung up on them when they asked for money, but kept the obscenities to myself.

 

Emailed we_can_help again, explained the situation.  Got a reply from ComcastSteve himself, who said that we can't have the 3.3 firmware.  I asked what sort of timeline it would take to get the new firmware.  He said that Motorola HAD ALREADY DELIVERED A NEW VERSION TO THEM and that it was in beta testing and that it should be pushed to us "soon". 

 

I see that this will be news to folks here.  Who knows how long before they decide it is ok to push it again?  It was in testing for months last time.  How do the folks at Comcast sleep at night?

 

Regular Contributor
MidnightCat
Posts: 37
Registered: ‎01-15-2010

Re: Intermittent drops - Motorola sbg6580

Maybe they will wait to push the new firmware for everyone in December for "doomsday". Sorry, had to put a little humor here, cause this is just getting silly. :smileyhappy:

Contributor
chadsittner
Posts: 5
Registered: ‎02-13-2012

Re: Intermittent drops - Motorola sbg6580

D*@n it, after 2 weeks of perfect service with 3.3 tonight those clowns rolled me back to 3.1. And of course the drops start again. They want me to pay the bill, they fix their problem first. No fix, no payment.

New Visitor
Com_Shepard
Posts: 3
Registered: ‎03-16-2012

Re: Intermittent drops - Motorola sbg6580

I am having the same issue as everyone here. Daily drops. Modem resets itself and I'm connected back. I don't have to power cycle, it does it on it's own. I am soooo frustrated!!! I switched from DSL to get better speed, but this "approved" modem/router from Comcast is just behaving like a POS. I tried turning off Firewall and Flood IP Detection off, but it doesn't seem to be helping. I am so sick of dealing with this. I called Comcast, but they never called me back, even though the msg said they'd call me back in 1-3 mins. Here are my logs. I am not sure if I should just switch back to DSL or give up and buy a new modem/ router. What a complete waste of money...

 

Software Version SBG6580-3.1.0.0-GA-07-180-NOSH

 

Thu Mar 15 20:38:57 2012    Notice (6)   TLV-11 - unrecognized OID;CM-MAC=70:7e:43:4f:59:65;CMTS-MAC=00:01:5c:23:da:51;CM-QOS=1.1;CM-VER=3.0;   Time Not Established   Warning (5)   ToD request sent - No Response received;CM-MAC=70:7e:43:4f:59:65;CMTS-MAC=00:01:5c:23:da:51;CM-QOS=1.1;CM-VER=3.0;   Wed Mar 14 23:04:25 2012    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=70:7e:43:4f:59:65;CMTS-MAC=00:01:5c:23:da:51;CM-QOS=1.1;CM-VER=3.0;   Wed Mar 14 06:08:33 2012    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=70:7e:43:4f:59:65;CMTS-MAC=00:01:5c:23:da:51;CM-QOS=1.1;CM-VER=3.0;   Tue Mar 13 20:05:37 2012    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=70:7e:43:4f:59:65;CMTS-MAC=00:01:5c:23:da:51;CM-QOS=1.1;CM-VER=3.0;   Tue Mar 13 00:44:16 2012    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=70:7e:43:4f:59:65;CMTS-MAC=00:01:5c:23:da:51;CM-QOS=1.1;CM-VER=3.0;   Mon Mar 12 07:16:14 2012    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=70:7e:43:4f:59:65;CMTS-MAC=00:01:5c:23:da:51;CM-QOS=1.1;CM-VER=3.0;   Sun Mar 11 19:01:09 2012    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=70:7e:43:4f:59:65;CMTS-MAC=00:01:5c:23:da:51;CM-QOS=1.1;CM-VER=3.0;   Sat Mar 10 13:00:43 2012    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=70:7e:43:4f:59:65;CMTS-MAC=00:01:5c:23:da:51;CM-QOS=1.1;CM-VER=3.0;   Fri Mar 09 13:54:56 2012    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=70:7e:43:4f:59:65;CMTS-MAC=00:01:5c:23:da:51;CM-QOS=1.1;CM-VER=3.0;   Fri Mar 09 03:10:02 2012    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=70:7e:43:4f:59:65;CMTS-MAC=00:01:5c:23:da:51;CM-QOS=1.1;CM-VER=3.0;   Thu Mar 08 08:21:59 2012    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=70:7e:43:4f:59:65;CMTS-MAC=00:01:5c:23:da:51;CM-QOS=1.1;CM-VER=3.0;   Wed Mar 07 23:55:33 2012    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=70:7e:43:4f:59:65;CMTS-MAC=00:01:5c:23:da:51;CM-QOS=1.1;CM-VER=3.0;   Wed Mar 07 02:36:07 2012    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=70:7e:43:4f:59:65;CMTS-MAC=00:01:5c:23:da:51;CM-QOS=1.1;CM-VER=3.0;   Tue Mar 06 07:06:08 2012    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=70:7e:43:4f:59:65;CMTS-MAC=00:01:5c:23:da:51;CM-QOS=1.1;CM-VER=3.0;   Tue Mar 06 01:17:55 2012    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=70:7e:43:4f:59:65;CMTS-MAC=00:01:5c:23:da:51;CM-QOS=1.1;CM-VER=3.0;   Mon Mar 05 07:15:40 2012    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=70:7e:43:4f:59:65;CMTS-MAC=00:01:5c:23:da:51;CM-QOS=1.1;CM-VER=3.0;   Sun Mar 04 00:01:06 2012    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=70:7e:43:4f:59:65;CMTS-MAC=00:01:5c:23:da:51;CM-QOS=1.1;CM-VER=3.0;   Sat Mar 03 10:41:39 2012    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=70:7e:43:4f:59:65;CMTS-MAC=00:01:5c:23:da:51;CM-QOS=1.1;CM-VER=3.0;   Thu Mar 01 00:38:59 2012    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=70:7e:43:4f:59:65;CMTS-MAC=00:01:5c:23:da:51;CM-QOS=1.1;CM-VER=3.0;   Wed Feb 29 22:44:41 2012    Critical (3)   Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=70:7e:43:4f:59:65;CMTS-MAC=00:01:5c:23:da:51;CM-QOS=1.1;CM-VER=3.0;   Wed Feb 29 21:01:19 2012    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=70:7e:43:4f:59:65;CMTS-MAC=00:01:5c:23:da:51;CM-QOS=1.1;CM-VER=3.0;   Sun Feb 26 16:45:03 2012    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=70:7e:43:4f:59:65;CMTS-MAC=00:01:5c:23:da:51;CM-QOS=1.1;CM-VER=3.0;   Sun Feb 26 13:58:48 2012    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=70:7e:43:4f:59:65;CMTS-MAC=00:01:5c:23:da:51;CM-QOS=1.1;CM-VER=3.0;   Fri Feb 17 21:29:04 2012    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=70:7e:43:4f:59:65;CMTS-MAC=00:01:5c:23:da:51;CM-QOS=1.1;CM-VER=3.0;   Fri Feb 17 09:04:16 2012    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=70:7e:43:4f:59:65;CMTS-MAC=00:01:5c:23:da:51;CM-QOS=1.1;CM-VER=3.0;   Wed Feb 15 23:40:48 2012    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=70:7e:43:4f:59:65;CMTS-MAC=00:01:5c:23:da:51;CM-QOS=1.1;CM-VER=3.0;   Tue Feb 14 20:13:47 2012    Critical (3)   Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=70:7e:43:4f:59:65;CMTS-MAC=00:01:5c:23:da:51;CM-QOS=1.1;CM-VER=3.0;   Tue Feb 14 01:06:49 2012    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=70:7e:43:4f:59:65;CMTS-MAC=00:01:5c:23:da:51;CM-QOS=1.1;CM-VER=3.0;   Sun Feb 12 23:44:45 2012    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=70:7e:43:4f:59:65;CMTS-MAC=00:01:5c:23:da:51;CM-QOS=1.1;CM-VER=3.0;   Sun Feb 12 13:51:58 2012    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=70:7e:43:4f:59:65;CMTS-MAC=00:01:5c:23:da:51;CM-QOS=1.1;CM-VER=3.0;   Sat Feb 11 21:55:34 2012    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=70:7e:43:4f:59:65;CMTS-MAC=00:01:5c:23:da:51;CM-QOS=1.1;CM-VER=3.0;   Fri Feb 10 20:19:04 2012    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=70:7e:43:4f:59:65;CMTS-MAC=00:01:5c:23:da:51;CM-QOS=1.1;CM-VER=3.0;   Fri Feb 10 07:01:52 2012    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=70:7e:43:4f:59:65;CMTS-MAC=00:01:5c:23:da:51;CM-QOS=1.1;CM-VER=3.0;   Thu Feb 09 04:05:22 2012    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=70:7e:43:4f:59:65;CMTS-MAC=00:01:5c:23:da:51;CM-QOS=1.1;CM-VER=3.0;   Tue Feb 07 23:11:32 2012    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=70:7e:43:4f:59:65;CMTS-MAC=00:01:5c:23:da:51;CM-QOS=1.1;CM-VER=3.0;   Tue Feb 07 08:13:55 2012    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=70:7e:43:4f:59:65;CMTS-MAC=00:01:5c:23:da:51;CM-QOS=1.1;CM-VER=3.0;   Mon Feb 06 18:47:38 2012    Critical (3)   Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=70:7e:43:4f:59:65;CMTS-MAC=00:01:5c:23:da:51;CM-QOS=1.1;CM-VER=3.0;   Mon Feb 06 17:34:53 2012    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=70:7e:43:4f:59:65;CMTS-MAC=00:01:5c:23:da:51;CM-QOS=1.1;CM-VER=3.0;   Sun Feb 05 23:59:28 2012    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=70:7e:43:4f:59:65;CMTS-MAC=00:01:5c:23:da:51;CM-QOS=1.1;CM-VER=3.0;   Mon Jan 30 17:15:23 2012    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=70:7e:43:4f:59:65;CMTS-MAC=00:01:5c:23:da:51;CM-QOS=1.1;CM-VER=3.0;   Sun Jan 29 18:54:00 2012    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=70:7e:43:4f:59:65;CMTS-MAC=00:01:5c:23:da:51;CM-QOS=1.1;CM-VER=3.0;   Sat Jan 28 18:41:28 2012    Critical (3)   Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=70:7e:43:4f:59:65;CMTS-MAC=00:01:5c:23:da:51;CM-QOS=1.1;CM-VER=3.0;   Sat Jan 28 02:29:03 2012    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=70:7e:43:4f:59:65;CMTS-MAC=00:01:5c:23:da:51;CM-QOS=1.1;CM-VER=3.0;   Thu Jan 26 20:25:48 2012    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=70:7e:43:4f:59:65;CMTS-MAC=00:01:5c:23:da:51;CM-QOS=1.1;CM-VER=3.0;   Thu Jan 26 03:10:46 2012    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=70:7e:43:4f:59:65;CMTS-MAC=00:01:5c:23:da:51;CM-QOS=1.1;CM-VER=3.0;   Wed Jan 25 05:48:31 2012    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=70:7e:43:4f:59:65;CMTS-MAC=00:01:5c:23:da:51;CM-QOS=1.1;CM-VER=3.0;   Time Not Established   Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=70:7e:43:4f:59:65;CMTS-MAC=00:01:5c:23:da:51;CM-QOS=1.0;CM-VER=3.0;   Mon Jan 23 09:51:55 2012    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=70:7e:43:4f:59:65;CMTS-MAC=00:01:5c:23:da:51;CM-QOS=1.1;CM-VER=3.0;   Sun Jan 22 18:45:05 2012    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=70:7e:43:4f:59:65;CMTS-MAC=00:01:5c:23:da:51;CM-QOS=1.1;CM-VER=3.0;   Sat Jan 21 22:09:56 2012    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=70:7e:43:4f:59:65;CMTS-MAC=00:01:5c:23:da:51;CM-QOS=1.1;CM-VER=3.0;   Sat Jan 21 11:27:54 2012    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=70:7e:43:4f:59:65;CMTS-MAC=00:01:5c:23:da:51;CM-QOS=1.1;CM-VER=3.0;   Fri Jan 20 15:11:28 2012    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=70:7e:43:4f:59:65;CMTS-MAC=00:01:5c:23:da:51;CM-QOS=1.1;CM-VER=3.0;   Thu Jan 19 10:33:18 2012    Critical (3)   Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=70:7e:43:4f:59:65;CMTS-MAC=00:01:5c:23:da:51;CM-QOS=1.1;CM-VER=3.0;   Wed Jan 18 18:47:10 2012    Critical (3)   Resetting the cable modem due to docsDevResetNow   Time Not Established   Critical (3)   No Ranging Response received - T3 time-out    Time Not Established   Critical (3)   SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=70:7e:43:4f:59:65;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;   Time Not Established   Critical (3)   SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=70:7e:43:4f:59:65;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;   Time Not Established   Critical (3)   SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=70:7e:43:4f:59:65;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;   Time Not Established   Critical (3)   SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=70:7e:43:4f:59:65;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;   Time Not Established   Critical (3)   No Ranging Response received - T3 time-out    Time Not Established   Critical (3)   SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=70:7e:43:4f:59:65;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;   Time Not Established   Critical (3)   SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=70:7e:43:4f:59:65;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;   Time Not Established   Critical (3)   SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=70:7e:43:4f:59:65;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;   Time Not Established   Critical (3)   SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=70:7e:43:4f:59:65;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;

Contributor
Posts: 9
Registered: ‎06-21-2007

Re: Intermittent drops - Motorola sbg6580

Like so many others, i had 3.1 firmware then went to 3.3.1 firmware for about 3 weeks then back to 3.1 firmware.  While at 3.3.1, I logged on as ROOT and downloaded the configfuration file (It's a clickable link to a clear text file).  I saved it, for grins....

 

Now while at 3.1, I wanted to compare and when I try to do the same, the modem resets when clicking the link.

 

Configuration FileOKd11_m_sbg6580_speedtierextreme2_c01.cm

 

 

Hmmm.

 

I have numerous spontaneous modem reboots and i'm going to to use PINGDOM.COM to try to keep track of them (even when I'm not using the computer).

 

 

The logons (someone asked a few posts back) are

 

root/motorola

 

and

 

admin/motorola

Contributor
Posts: 15
Registered: ‎05-09-2009

Re: Intermittent drops - Motorola sbg6580

I was on 3.3 for a little while too and was rolled back to 3.1 recently. I have had a massive amount of error messages in my modem's log like Com_Shepard has ever since they downgraded me back. I sometimes get disconnected out of the blue; sometimes I have to wait a little while before I get my connection back. It's all over the place.

 

I don't know what the issue was with 3.3 but it was working fine for me.  : /

Regular Contributor
Sean3040
Posts: 28
Registered: ‎01-05-2011

Re: Intermittent drops - Motorola sbg6580

What do you mean by 3.3?

Regular Contributor
MidnightCat
Posts: 37
Registered: ‎01-15-2010

Re: Intermittent drops - Motorola sbg6580

That's the latest version of the firmware Comcast rolled out to their customers that have the gateways before they rolled it back to 3.1.

Contributor
donf99
Posts: 17
Registered: ‎12-29-2011

Re: Intermittent drops - Motorola sbg6580

Well, here's a new one. My modem was rolled back from 3.3 to 3.1 several weeks ago. While on a business trip, my modem mysteriously reset itself back to factory defaults. I lost my IP addressing, port forwarding, wireless settings, and custom IP assignments. This completely took out my Voip phones and access to my servers, as well as Internet access for any computer not hard-wired to the router. Very bad!

After arriving home, I attempted to restore the modem with my backed up settings file. Since the backup was done when the modem was on firmware 3.3, the file caused the modem to reset to factory defaults. It took several hours to sort out the firewall and IP address settings from scratch.

Can Comcast force a factory reset? If so, why would they?
Contributor
Posts: 15
Registered: ‎05-09-2009

Re: Intermittent drops - Motorola sbg6580


donf99 wrote:
Well, here's a new one. My modem was rolled back from 3.3 to 3.1 several weeks ago. While on a business trip, my modem mysteriously reset itself back to factory defaults. I lost my IP addressing, port forwarding, wireless settings, and custom IP assignments. This completely took out my Voip phones and access to my servers, as well as Internet access for any computer not hard-wired to the router. Very bad!

After arriving home, I attempted to restore the modem with my backed up settings file. Since the backup was done when the modem was on firmware 3.3, the file caused the modem to reset to factory defaults. It took several hours to sort out the firewall and IP address settings from scratch.

Can Comcast force a factory reset? If so, why would they?

That is very odd. (Just for curiosity's sake, I checked the settings in my modem to make sure everything's set the way I left it; no problems to report there.)

 

Was your admin password settings and such reset too?

Contributor
donf99
Posts: 17
Registered: ‎12-29-2011

Re: Intermittent drops - Motorola sbg6580

Yes, it was a total factory reset. The admin password was reset. This happened many weeks after the downgrade to 3.1. Restoring with the backup made when at 3.3 forced a modem reset, but the settings were not restored.
Contributor
wzeallor
Posts: 14
Registered: ‎01-07-2012

Re: Intermittent drops - Motorola sbg6580

Mine randomly reset sometime last year. It's likely a random error caused by the 3.1 incompatabilities.

Regular Contributor
Sean3040
Posts: 28
Registered: ‎01-05-2011

Re: Intermittent drops - Motorola sbg6580

Call 1800-COMCAST and request they send you a wireless gateway (only can be done through mail), with free overnight shipping for the incovience. This make take a few phone calls. Make sure the amount is credited before you leave the call! You can check my asking for your account balance. If it is $29.95 less than before, then the shipping is free. You can also log into your comcast account online (can take upto 15 minutes to update though)

Regular Contributor
evil_hero
Posts: 57
Registered: ‎10-29-2011

Re: Intermittent drops - Motorola sbg6580

Looking to sale this thing off and get something else. What do you all recommend? moto 6120, moto 6121, or something else?

 

Thanks for the input

 

Regular Contributor
Sean3040
Posts: 28
Registered: ‎01-05-2011

Re: Intermittent drops - Motorola sbg6580

Get a modem from Comcast and ask for free (mark modem as customer owned)
Regular Contributor
Sean3040
Posts: 28
Registered: ‎01-05-2011

Re: Intermittent drops - Motorola sbg6580

Smcd3dnvg or arris tg852g
Cable Expert
i-am-nerdburg
Posts: 10,052
Registered: ‎06-27-2009

Re: Intermittent drops - Motorola sbg6580

[ Edited ]

evil_hero wrote:

Looking to sale this thing off and get something else. What do you all recommend? moto 6120, moto 6121, or something else?

 

Thanks for the input

 


I'd suggest you check out a Motorola 6121 or Zoom 5341-J either one is about $85. You'll also want a dual channel  gigabit router.

Visitor
MDRL
Posts: 4
Registered: ‎01-13-2012

Re: Intermittent drops - Motorola sbg6580

I gave up too... Happened to see the 6121 at a Target store. $89.00. Bought it just in case I couldn't get the 6580 working correctly. Waited a few weeks. Installed it (and a router) about a week ago... Works way better and no issues so far! The 6580 also lagged when waking my computers....  This 6121 is up immediatly.  

Connection Expert
EG
Posts: 40,205
Registered: ‎12-24-2003

Re: Intermittent drops - Motorola sbg6580


Sean3040 wrote:
Smcd3dnvg or arris tg852g

Why would anybody want their crippled gateway junk..