<?xml version="1.0" encoding="UTF-8"?>

<rss version="2.0" xmlns:blogChannel="http://backend.userland.com/blogChannelModule">

<channel>
<title>Topic &#x27;SB6141 Firmware Update?&#x27; in forum &#x27;Motorola&#x27; - dslreports.com</title>
<link>http://www.dslreports.com/forum/SB6141-Firmware-Update-27821731</link>
<description></description>
<language>en</language>
<pubDate>Wed, 19 Jun 2013 06:29:46 EDT</pubDate>
<lastBuildDate>Wed, 19 Jun 2013 06:29:46 EDT</lastBuildDate>

<item>
<title>Re: SB6141 Firmware Update?</title>
<link>http://www.dslreports.com/forum/Re-SB6141-Firmware-Update-28383849</link>
<description><![CDATA[swintec posted : How arte you approaching the problem with TW?  T4 errors shouldnt happen under ideal circumstances so maybe it would be better to pursue that route?  Obviously a modem shouldnt restart because of it but they do not seem willing to address that with a simple firmware update.  FWIW, I have the same firmware but do not see the problem at all.<br><br>Maybe start a topic in the direct forum here and get the ball rolling for a widespread rollout of the newest firmware, which HAS been issued in some divisions according to some topics here.  Or maybe they can at least get the T4 problems fixed.<br><small>--<br><A HREF="http://blocknews.net">Usenet Block Accounts</a> | <A HREF="http://usenetnow.net">Unlimited Accounts</a></small>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-SB6141-Firmware-Update-28383849</guid>
<pubDate>Sat, 15 Jun 2013 16:55:55 EDT</pubDate>
</item>

<item>
<title>Re: SB6141 Firmware Update?</title>
<link>http://www.dslreports.com/forum/Re-SB6141-Firmware-Update-28383840</link>
<description><![CDATA[Andrew LB posted : Well I've been having this T4 timeout problem since last summer and have spent at least 20 hours arguing with TWC to get things fixed. It's hilarious that when I purchased my SB6141, I specifically asked TWC if I will receive full support for the modem since it is on their approved list, which they said they would. <br><br>Now they're telling me that they cannot even give me level 3 tech support because they don't support customer modems and that the problem is not on their end, but they'd like to send a tech out.... again.<br><br>They also told me that any firmware updates must be obtained from Motorola since this is a customer owned device.... so much for support.<br><br>Has anyone been able to get firmware from Motorola?<br><br>here is my current software:<br><br>Model Name: SB6141<br>Vendor Name: Motorola<br>Firmware Name: SB_KOMODO-1.0.6.3-SCM03-NOSH<br>Boot Version: PSPU-Boot(25CLK) 1.0.12.<br>Hardware Version: 7.0<br>Firmware Build Time: Aug 18 2011 10:27:53]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-SB6141-Firmware-Update-28383840</guid>
<pubDate>Sat, 15 Jun 2013 16:49:41 EDT</pubDate>
</item>

<item>
<title>Re: SB6141 Firmware Update?</title>
<link>http://www.dslreports.com/forum/Re-SB6141-Firmware-Update-28379147</link>
<description><![CDATA[Meatball posted : Just want to say, I've been using the SB6121 (Firmware SB612X-1.0.5.1-SCM00-NOSH from Dec 2010) for months without a single issue.  I know they fixed something in my neighborhood, but I also wonder if the 6141 just has issues with TWC's network.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-SB6141-Firmware-Update-28379147</guid>
<pubDate>Thu, 13 Jun 2013 21:14:41 EDT</pubDate>
</item>

<item>
<title>Re: SB6141 Firmware Update?</title>
<link>http://www.dslreports.com/forum/Re-SB6141-Firmware-Update-28376802</link>
<description><![CDATA[Le Roy posted : Still having issues with T4 timeouts, but either I'm not using my Internet as much as I was before or it just doesn't happen as frequently.<br><br>Last night between 930PM and 1130PM, my modem rebooted due to T4 errors 4 times.<br><small>--<br>www.tdnclan.com<br></small>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-SB6141-Firmware-Update-28376802</guid>
<pubDate>Thu, 13 Jun 2013 08:33:14 EDT</pubDate>
</item>

<item>
<title>Re: SB6141 Firmware Update?</title>
<link>http://www.dslreports.com/forum/Re-SB6141-Firmware-Update-28347503</link>
<description><![CDATA[boe_d posted : I've spent 2 hours working with TW.  My old modem gets 26mbit down the best they can do for me is 15mbit.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-SB6141-Firmware-Update-28347503</guid>
<pubDate>Tue, 04 Jun 2013 00:36:04 EDT</pubDate>
</item>

<item>
<title>Re: SB6141 Firmware Update?</title>
<link>http://www.dslreports.com/forum/Re-SB6141-Firmware-Update-28347297</link>
<description><![CDATA[boe_d posted : I just switched out my TW rental unit for the Sb16141.   I went from 26mbit down x 2mbit up to 3mbit down x2mbit up.  I certainly am hoping this is fixed quickly.  <br><br>Model Name: SB6141<br> Vendor Name: Motorola<br> Firmware Name: SB_KOMODO-1.0.6.3-SCM03-NOSH<br> Boot Version: PSPU-Boot(25CLK) 1.0.12.<br> Hardware Version: 7.0<br> Firmware Build Time: Aug 18 2011 10:27:53]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-SB6141-Firmware-Update-28347297</guid>
<pubDate>Mon, 03 Jun 2013 23:13:30 EDT</pubDate>
</item>

<item>
<title>Re: SB6141 Firmware Update?</title>
<link>http://www.dslreports.com/forum/Re-SB6141-Firmware-Update-28324175</link>
<description><![CDATA[ShudderUser posted : "Meatball", and friends,<br>I Shudder here in Charlotte, NC. Switching to TWC from ATT Uverse to gain control of my home network (silly me for wanting to manage VoIP & NOT pay $35/mo to ATT).  <br><br>ANYWAY, looking to you as I prepare to buy my own modem and router.  After reading about Meatball's experience with Motorola's still-approved, purchased router since December, I wanted to cry (for us both, I promise!)<br><br>My eagerly-awaited departure (think "Argo" hostage) from AT&T ("I can transfer you to the Fee-based customer service area that can assist you with your issue"... ON A RENTED ROUTER? UGH!) Dear, dear Meatball: do you have any newer experiences?  I see that one respondant suggested s/he had switched to a router not specifically "supported" by TWC.  I find that move terrifying ... which is probably silly on my part.  <br><br>I initially switched to ATT 2 years ago since it was easier to get them to initiate a simple reboot by calling an automated attendant: Can TWC do that now?  I even chose their $6/mo (ironically, Motorola!) modem (they provide one already capable of wifi to addict the user and those pesky Phone ports mean they control your access to VoIP).  They've taking the "User's Manual" off the FCC's website, but hey?  It's not like I'm paying them rent to ... oh, wait, I am.  Although you can access the router's [2Wire] web interface and change settings on the Ethernet ports, you can't really.  I esp loved being taunted with the bright green "Contratulations! Successfully changed!" page they forgot to disable.  Yes, even the interface lies to me.<br><br>Because TWC allows me to go month to month, I still prefer them.  Would you suggest that I [suck it up and] rent the modem to get the access into my home with their alleged support and just purchase a router for wifi, VoIP and ethernet?  <br><br>Peace and condolences as I Shudder in Charlotte.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-SB6141-Firmware-Update-28324175</guid>
<pubDate>Sun, 26 May 2013 13:11:50 EDT</pubDate>
</item>

<item>
<title>Re: SB6141 Firmware Update?</title>
<link>http://www.dslreports.com/forum/Re-SB6141-Firmware-Update-28263191</link>
<description><![CDATA[Le Roy posted : Spoke too soon. Seems as long as I don't upload anything heavily and/or download constantly I am fine. Once I start using the connection I pay for, I get those errors and the modem reboots itself.<br><br>Maybe this will be of some help.<br><br>Model Name: SB6141<br>Vendor Name: Motorola<br>Firmware Name: SB_KOMODO-1.0.6.10-SCM00-NOSH<br>Boot Version: PSPU-Boot(25CLK) 1.0.12.18m3<br>Hardware Version: 7.0<br>Serial Number: xxxxxxxxxxx<br>Firmware Build Time: Oct 29 2012 18:07:13]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-SB6141-Firmware-Update-28263191</guid>
<pubDate>Sun, 05 May 2013 05:31:27 EDT</pubDate>
</item>

<item>
<title>Re: SB6141 Reset and bore on ......</title>
<link>http://www.dslreports.com/forum/Re-SB6141-Reset-and-bore-on-28254717</link>
<description><![CDATA[Le Roy posted : Well so far I haven't had any connection issues with the modem. <br><small>--<br>www.tdnclan.com<br></small>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-SB6141-Reset-and-bore-on-28254717</guid>
<pubDate>Wed, 01 May 2013 23:23:00 EDT</pubDate>
</item>

<item>
<title>Re: SB6141 Reset and bore on ......</title>
<link>http://www.dslreports.com/forum/Re-SB6141-Reset-and-bore-on-28233171</link>
<description><![CDATA[swintec posted : <div class="bquote"><said>said by <a href="/profile/625624" onClick="this.blur(); return popup(event,'/uidpop?ajh=1&uid=625624');">Le Roy</a>:</said><p>That's good to know, so the 6180 uses the same firmware as well? If not, then I am afraid they are still going to tell me it's my modems problem when the 6180 they left here wont be getting dropped.<br> </p></div>No, the 6180 does not share the same firmware image.  Just the 6141, 6121 and 6120.<br><br>Key part from the manual linked to below:<br>"Easily add the SB6141 to a deployed family of SB6120s and SB6121s, all three models utilize the same firmware image. This reduces qualification time for an Operator and eliminates configuration management headaches."<br><br>&raquo;<A HREF="http://moto.arrisi.com/staticfiles/Video-Solutions/Products/Voice-and-Data-CPE/DOCSIS-Modems-Gateways-and-eMTAs/Cable-Modems/SB6141/_Documents/_Static_files/SB6141-US-EN.pdf" >moto.arrisi.com/staticfiles/Vide&middot;&middot;&middot;S-EN.pdf</A><br><small>--<br><A HREF="http://blocknews.net">Usenet Block Accounts</a> | <A HREF="http://usenetnow.net">Unlimited Accounts</a></small>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-SB6141-Reset-and-bore-on-28233171</guid>
<pubDate>Wed, 24 Apr 2013 18:33:41 EDT</pubDate>
</item>

<item>
<title>Re: SB6141 Reset and bore on ......</title>
<link>http://www.dslreports.com/forum/Re-SB6141-Reset-and-bore-on-28233091</link>
<description><![CDATA[Le Roy posted : Oh wow, I just looked up the latest support list and the 6141 has been added!! When I bought the modem back in January, it wasn't listed. <br><br>&raquo;<A HREF="http://support.cableone.net/app/answers/detail/a_id/765/~/cable-modem-models" >support.cableone.net/app/answers&middot;&middot;&middot;m-models</A><br><br>That's good to know, so the 6180 uses the same firmware as well? If not, then I am afraid they are still going to tell me it's my modems problem when the 6180 they left here wont be getting dropped.<br><br>On the other hand, if it does have the same firmware and it does get dropped, that should make it a lot easier to tell them they need to update their firmware to solve the problem.<br><br>Do you happen to have some more documentation/links that I can read more into this so I can be better educated on the issue for when the tech comes back out tomorrow?<br><small>--<br>www.tdnclan.com<br></small>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-SB6141-Reset-and-bore-on-28233091</guid>
<pubDate>Wed, 24 Apr 2013 18:11:39 EDT</pubDate>
</item>

<item>
<title>Re: SB6141 Reset and bore on ......</title>
<link>http://www.dslreports.com/forum/Re-SB6141-Reset-and-bore-on-28233076</link>
<description><![CDATA[swintec posted : <div class="bquote"><said>said by <a href="/profile/625624" onClick="this.blur(); return popup(event,'/uidpop?ajh=1&uid=625624');">Le Roy</a>:</said><p>The problem is, the 6141 is not "officially" supported by my Cable Company (Cable One) so they will most likely just tell me to get a new cable modem.<br> </p></div>What modems are supported by your cable company?  The 6141 uses the same firmware as the 6121 and I believe the 6120.  This was by design by Motorola in order to make things a bit easier on ISPs.  If they utilize either of those modems as supported they should have no problem supporting the 6141, or at least upgrading you to a newer firmware (although i realize this would be an uphill battle for you on that front).<br><br>There is a white 6141 available now through regular retail channels (Newegg, etc) that ships with a newer firmware.  This should take care of your issue.  My experience on this front simply comes from discussions in the Time Warner forum and users posting about it.  YMMV on a different cable company but your symptoms are all the same.<br><small>--<br><A HREF="http://blocknews.net">Usenet Block Accounts</a> | <A HREF="http://usenetnow.net">Unlimited Accounts</a></small>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-SB6141-Reset-and-bore-on-28233076</guid>
<pubDate>Wed, 24 Apr 2013 18:07:13 EDT</pubDate>
</item>

<item>
<title>Re: SB6141 Reset and bore on ......</title>
<link>http://www.dslreports.com/forum/Re-SB6141-Reset-and-bore-on-28233038</link>
<description><![CDATA[Le Roy posted : So what you are saying is what I am fearing. They are going to come back and say it's a problem with my Cable Modem since the 6180 wont be getting dropped when the 6141 will? If I tell the line tech who is coming back to my house tomorrow that the reason why the 6141 is dropping it's connection is because of T4 errors. The problem is, the 6141 is not "officially" supported by my Cable Company (Cable One) so they will most likely just tell me to get a new cable modem.<br><br>Worst case scenario, I do have to get a new one. Which one would be recommended?<br><small>--<br>www.tdnclan.com<br></small>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-SB6141-Reset-and-bore-on-28233038</guid>
<pubDate>Wed, 24 Apr 2013 17:59:32 EDT</pubDate>
</item>

<item>
<title>Re: SB6141 Reset and bore on ......</title>
<link>http://www.dslreports.com/forum/Re-SB6141-Reset-and-bore-on-28232995</link>
<description><![CDATA[swintec posted : <div class="bquote"><said>said by <a href="/profile/625624" onClick="this.blur(); return popup(event,'/uidpop?ajh=1&uid=625624');">Le Roy</a>:</said><p>Well now I will find out if it's the cable modem or something on their end. They left an SB6180 here on the same line as my SB6141, both are connected to the same 3 way splitter and online. So in theory, if it's a problem on their end, both modems should go down; but if it's the SB6141 modem, then only it will go down.<br> </p></div>The problem is the T4 timeouts you are having.  Granted, you arent supposed to get them but if they do happen the firmware that your (and many others) 6141's run on will cause the modem to drop like you see.<br><br>My 6141 runs great with the same firmware that yours has...but I do not have cable plant issues so i do not get T4 errors.<br><br>I think in this case, it is hard to pin blame.  One side would say the modem should handle the T4 errors more gracefully.  The opposite side would say the cable plant should be addressed so T4 errors should not happen to begin with.<br><br>At any rate, firmware revisions put out by Motorola address this.  Maybe your cable company is small enough where you can get them to apply a more recent version for you and others on the network.  I see it as a bandaid fix though for the bigger issue but I guess it is the easiest thing to do rather than have them track down why the T4 issue is happening to begin with.<br><small>--<br><A HREF="http://blocknews.net">Usenet Block Accounts</a> | <A HREF="http://usenetnow.net">Unlimited Accounts</a></small>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-SB6141-Reset-and-bore-on-28232995</guid>
<pubDate>Wed, 24 Apr 2013 17:49:23 EDT</pubDate>
</item>

<item>
<title>Re: SB6141 Reset and bore on ......</title>
<link>http://www.dslreports.com/forum/Re-SB6141-Reset-and-bore-on-28232966</link>
<description><![CDATA[Le Roy posted : Well now I will find out if it's the cable modem or something on their end. They left an SB6180 here on the same line as my SB6141, both are connected to the same 3 way splitter and online. So in theory, if it's a problem on their end, both modems should go down; but if it's the SB6141 modem, then only it will go down.<br><small>--<br>www.tdnclan.com<br></small>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-SB6141-Reset-and-bore-on-28232966</guid>
<pubDate>Wed, 24 Apr 2013 17:39:15 EDT</pubDate>
</item>

<item>
<title>Re: SB6141 Reset and bore on ......</title>
<link>http://www.dslreports.com/forum/Re-SB6141-Reset-and-bore-on-28228520</link>
<description><![CDATA[Le Roy posted : <pre class="brush: text">Apr 23 2013 11:11:11 6-Notice I401.0 TLV-11 - unrecognized OID;CM-MAC=38:6b:bb:7f:7c:bf;CMTS-MAC=00:26:99:8a:99:9e;CM-QOS=1.1;CM-VER=3.0;&#012;Apr 23 2013 11:11:11 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=38:6b:bb:7f:7c:bf;CMTS-MAC=00:26:99:8a:99:9e;CM-QOS=1.1;CM-VER=3.0;&#012;Jan 01 1970 00:08:49 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=38:6b:bb:7f:7c:bf;CMTS-MAC=00:26:99:8a:99:9e;CM-QOS=1.1;CM-VER=3.0;&#012;Jan 01 1970 00:08:47 5-Warning R09.0 B-INIT-RNG Failure - Retries exceeded;CM-MAC=38:6b:bb:7f:7c:bf;CMTS-MAC=00:26:99:8a:99:9e;CM-QOS=1.1;CM-VER=3.0;&#012;Jan 01 1970 00:08:43 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=38:6b:bb:7f:7c:bf;CMTS-MAC=00:26:99:8a:99:9e;CM-QOS=1.1;CM-VER=3.0;&#012;Jan 01 1970 00:08:01 3-Critical D01.0 DHCP FAILED - Discover sent, no offer received;CM-MAC=38:6b:bb:7f:7c:bf;CMTS-MAC=00:26:99:8a:99:9e;CM-QOS=1.1;CM-VER=3.0;&#012;Jan 01 1970 00:07:27 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=38:6b:bb:7f:7c:bf;CMTS-MAC=00:26:99:8a:99:9e;CM-QOS=1.1;CM-VER=3.0;&#012;Jan 01 1970 00:00:14 6-Notice N/A Cable Modem Reboot due to power reset ;CM-MAC=38:6b:bb:7f:7c:bf;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;&#012;Jan 01 1970 00:00:54 3-Critical T05.0 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=38:6b:bb:7f:7c:bf;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;&#012;Jan 01 1970 00:00:42 5-Warning T203.0 MDD message timeout;CM-MAC=38:6b:bb:7f:7c:bf;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;&#012;Jan 01 1970 00:00:14 6-Notice N/A Cable Modem Reboot due to T4 timeout ;CM-MAC=38:6b:bb:7f:7c:bf;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;&#012;Apr 23 2013 11:00:01 3-Critical R04.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=38:6b:bb:7f:7c:bf;CMTS-MAC=00:26:99:8a:99:9e;CM-QOS=1.1;CM-VER=3.0;&#012;Apr 23 2013 03:05:35 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=38:6b:bb:7f:7c:bf;CMTS-MAC=00:26:99:8a:99:9e;CM-QOS=1.1;CM-VER=3.0;&#012;Apr 23 2013 02:54:25 6-Notice I401.0 TLV-11 - unrecognized OID;CM-MAC=38:6b:bb:7f:7c:bf;CMTS-MAC=00:26:99:8a:99:9e;CM-QOS=1.1;CM-VER=3.0;&#012;Apr 23 2013 02:54:25 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=38:6b:bb:7f:7c:bf;CMTS-MAC=00:26:99:8a:99:9e;CM-QOS=1.1;CM-VER=3.0;&#012;Jan 01 1970 00:00:14 6-Notice N/A Cable Modem Reboot due to T4 timeout ;CM-MAC=38:6b:bb:7f:7c:bf;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;&#012;Apr 23 2013 02:53:41 3-Critical R04.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=38:6b:bb:7f:7c:bf;CMTS-MAC=00:26:99:8a:99:9e;CM-QOS=1.1;CM-VER=3.0;&#012;Apr 23 2013 02:52:56 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=38:6b:bb:7f:7c:bf;CMTS-MAC=00:26:99:8a:99:9e;CM-QOS=1.1;CM-VER=3.0;&#012;Apr 23 2013 02:41:40 6-Notice I401.0 TLV-11 - unrecognized OID;CM-MAC=38:6b:bb:7f:7c:bf;CMTS-MAC=00:26:99:8a:99:9e;CM-QOS=1.1;CM-VER=3.0;&#012;Apr 23 2013 02:41:40 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=38:6b:bb:7f:7c:bf;CMTS-MAC=00:26:99:8a:99:9e;CM-QOS=1.1;CM-VER=3.0;&#012; &#012;</pre><!--end code block--><br>This time the connection went down for a while. Like 15 - 20 minutes before the modem would connect again, power cycling seemed to have no effect. I was on the phone with the CO when it was down and when it came back online, he told me over the phone that he didn't see the modem online, despite it being online on my end. Weird. They are sending another tech out, right now he's talking to one of the techs in the call center apparently.<br><br>edit<br>He said they had an outage on their end, which is the reason why he wasn't able to see the modem come back online and the reason why it was off for so long. He said he still seen prior connection drops on my line and he's going to send a tech out anyway, so one will be here tomorrow between 3 - 5P.<br>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-SB6141-Reset-and-bore-on-28228520</guid>
<pubDate>Tue, 23 Apr 2013 13:17:39 EDT</pubDate>
</item>

<item>
<title>Re: SB6141 Reset and bore on ......</title>
<link>http://www.dslreports.com/forum/Re-SB6141-Reset-and-bore-on-28226834</link>
<description><![CDATA[Le Roy posted : <pre class="brush: text">Apr 22 2013 19:21:18 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=38:6b:bb:7f:7c:bf;CMTS-MAC=00:26:99:8a:99:9e;CM-QOS=1.1;CM-VER=3.0;&#012;Apr 22 2013 18:52:57 6-Notice I401.0 TLV-11 - unrecognized OID;CM-MAC=38:6b:bb:7f:7c:bf;CMTS-MAC=00:26:99:8a:99:9e;CM-QOS=1.1;CM-VER=3.0;&#012;Apr 22 2013 18:52:57 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=38:6b:bb:7f:7c:bf;CMTS-MAC=00:26:99:8a:99:9e;CM-QOS=1.1;CM-VER=3.0;&#012;Jan 01 1970 00:00:14 6-Notice N/A Cable Modem Reboot due to T4 timeout ;CM-MAC=38:6b:bb:7f:7c:bf;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;&#012;Apr 22 2013 18:52:13 3-Critical R04.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=38:6b:bb:7f:7c:bf;CMTS-MAC=00:26:99:8a:99:9e;CM-QOS=1.1;CM-VER=3.0;&#012;Apr 22 2013 18:51:43 3-Critical T05.0 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=38:6b:bb:7f:7c:bf;CMTS-MAC=00:26:99:8a:99:9e;CM-QOS=1.1;CM-VER=3.0;&#012;Apr 22 2013 18:51:17 5-Warning T202.0 Lost MDD Timeout;CM-MAC=38:6b:bb:7f:7c:bf;CMTS-MAC=00:26:99:8a:99:9e;CM-QOS=1.1;CM-VER=3.0;&#012;Apr 22 2013 18:51:12 3-Critical T05.0 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=38:6b:bb:7f:7c:bf;CMTS-MAC=00:26:99:8a:99:9e;CM-QOS=1.1;CM-VER=3.0;&#012;Apr 22 2013 18:50:58 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=38:6b:bb:7f:7c:bf;CMTS-MAC=00:26:99:8a:99:9e;CM-QOS=1.1;CM-VER=3.0;&#012;Apr 22 2013 17:57:18 3-Critical T05.0 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=38:6b:bb:7f:7c:bf;CMTS-MAC=00:26:99:8a:99:9e;CM-QOS=1.1;CM-VER=3.0;&#012;Apr 22 2013 17:57:05 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=38:6b:bb:7f:7c:bf;CMTS-MAC=00:26:99:8a:99:9e;CM-QOS=1.1;CM-VER=3.0;&#012;Apr 22 2013 17:57:02 3-Critical T05.0 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=38:6b:bb:7f:7c:bf;CMTS-MAC=00:26:99:8a:99:9e;CM-QOS=1.1;CM-VER=3.0;&#012;Apr 22 2013 17:56:52 6-Notice I401.0 TLV-11 - unrecognized OID;CM-MAC=38:6b:bb:7f:7c:bf;CMTS-MAC=00:26:99:8a:99:9e;CM-QOS=1.1;CM-VER=3.0;&#012;Apr 22 2013 17:56:52 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=38:6b:bb:7f:7c:bf;CMTS-MAC=00:26:99:8a:99:9e;CM-QOS=1.1;CM-VER=3.0;&#012;Jan 01 1970 00:00:14 6-Notice N/A Cable Modem Reboot due to T4 timeout ;CM-MAC=38:6b:bb:7f:7c:bf;CMTS-MAC=00:26:99:8a:99:9e;CM-QOS=1.1;CM-VER=3.0;&#012;Apr 22 2013 17:54:23 3-Critical R04.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=38:6b:bb:7f:7c:bf;CMTS-MAC=00:26:99:8a:99:9e;CM-QOS=1.1;CM-VER=3.0;&#012;Apr 22 2013 17:53:44 3-Critical T05.0 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=38:6b:bb:7f:7c:bf;CMTS-MAC=00:26:99:8a:99:9e;CM-QOS=1.1;CM-VER=3.0;&#012;Apr 22 2013 17:53:20 5-Warning T202.0 Lost MDD Timeout;CM-MAC=38:6b:bb:7f:7c:bf;CMTS-MAC=00:26:99:8a:99:9e;CM-QOS=1.1;CM-VER=3.0;&#012;Apr 22 2013 17:53:00 3-Critical T05.0 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=38:6b:bb:7f:7c:bf;CMTS-MAC=00:26:99:8a:99:9e;CM-QOS=1.1;CM-VER=3.0;&#012;Apr 22 2013 17:51:36 5-Warning T202.0 Lost MDD Timeout;CM-MAC=38:6b:bb:7f:7c:bf;CMTS-MAC=00:26:99:8a:99:9e;CM-QOS=1.1;CM-VER=3.0;&#012; &#012;</pre><!--end code block--><br><small>--<br><A HREF="http://redlined.org">Redlined.org</a><br><br>Mississippi Gulf Coast Car Enthusiasts Forums<br></small>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-SB6141-Reset-and-bore-on-28226834</guid>
<pubDate>Mon, 22 Apr 2013 22:27:29 EDT</pubDate>
</item>

<item>
<title>Re: SB6141 Reset and bore on ......</title>
<link>http://www.dslreports.com/forum/Re-SB6141-Reset-and-bore-on-28224087</link>
<description><![CDATA[Le Roy posted : Ill check when i get home,  but if i remember correctly it is t4 or t3 errors.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-SB6141-Reset-and-bore-on-28224087</guid>
<pubDate>Mon, 22 Apr 2013 02:42:09 EDT</pubDate>
</item>

<item>
<title>Re: SB6141 Reset and bore on ......</title>
<link>http://www.dslreports.com/forum/Re-SB6141-Reset-and-bore-on-28222289</link>
<description><![CDATA[swintec posted : <div class="bquote"><said>said by <a href="/profile/625624" onClick="this.blur(); return popup(event,'/uidpop?ajh=1&uid=625624');">Le Roy</a>:</said><p>My connection has gone from dropping 2 - 3 times per hour to only once every few hours now.<br> </p></div>What is the errors in your modem log?  t4 timeouts and such?<br><small>--<br><A HREF="http://blocknews.net">Usenet Block Accounts</a> | <A HREF="http://usenetnow.net">Unlimited Accounts</a></small>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-SB6141-Reset-and-bore-on-28222289</guid>
<pubDate>Sun, 21 Apr 2013 11:27:29 EDT</pubDate>
</item>

<item>
<title>Re: SB6141 Reset and bore on ......</title>
<link>http://www.dslreports.com/forum/Re-SB6141-Reset-and-bore-on-28221826</link>
<description><![CDATA[Le Roy posted : I too am having issues with my SB6141 on my Cable Company, but I'm not sure if it really is the Cable Modem or the Cable Company... My cable company is Cable One. I've had a tech come out twice already to look over everything. So far they've replaced the line directly from my outside box to my modem, all the splitters in between and redone all the ends. This last time they replaced the main line from their hub to my house under ground. (I don't think they've sent anyone out to bury it yet, it's been rainy/muddy the past couple of days still)<br><br>My connection has gone from dropping 2 - 3 times per hour to only once every few hours now.<br><br>Their has to be a way for consumers to do our own firmware update on these.<br><small>--<br><A HREF="http://redlined.org">Redlined.org</a><br><br>Mississippi Gulf Coast Car Enthusiasts Forums<br></small>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-SB6141-Reset-and-bore-on-28221826</guid>
<pubDate>Sun, 21 Apr 2013 04:25:32 EDT</pubDate>
</item>

<item>
<title>Re: SB6141 Reset and bore on ......</title>
<link>http://www.dslreports.com/forum/Re-SB6141-Reset-and-bore-on-28160480</link>
<description><![CDATA[halfcack posted : I don't know if it's an old post but the reset on the SB 6141 is under the plastic gummed to the front. Take it off and it's at the bottom. The plastic cover goes back on well. You could put a pin hole in the plastic but with all the problems I've had I wouldn't dare.<br><br>TWC/RR has provisioned my modem. They stated they have the proper code from Motorola. That from level three.<br><br>I have been told, in this area, we have 25 up, 50 down, doesn't exist. I was on EarthLink for a time. I wish I could get my rock solid 30 meg, 1 1/2 up back. Received a commercial modem sitting on my porch. Have complained every day I have not gotten 80 % of 50 down since I lost my g father plan.<br><br>A tech saw everything was as I described, the modem is capable of 320 down, the apple 2nd gen Airport Express was grabbing 79 meg down from the modem on a, b, g, and n.<br><br>Everything from the pole in was replaced, an old timer made the best connect I ever saw, from the pole to the modem no boxes. Past level 3 and past two appeals to get the speed to 50 have failed. I've already seen it. I am paying 64.99 for the Ultimate. I woke up to today to 6 down .1 up.<br><br>I have kept a record all day and night and early morning since 3-4-13, I am not getting the required advertised 50 meg down 80% of the time. Roughly, 20 to 30% or less. I believe that is federal law today, April first.<br><br>I am so tired of this but I will keep at it. I forgot the name of the department I was in and graduated from, ah, retention, there it is, it's when they try to keep a customer. I am at the last appeal. Lost them both. there is a third. A separate department listens to every phone call I've made to them and then decides. Since I believe in and tell the absolute truth, they will find no discrepencies but they will think I scripted it, no winners.<br><br>It's a losing battle. The line tech said today that he hates speed issues. He said worse than the last call, where an older lady was getting half a picture, he moved the other console TV for her in it's place. Really nice guy.<br><br>It's my reponsibility for messing with the original grandfathered plan. It was somehow programmed right and never deviated from 28.6 to 30 down and 1 and a half up. It probably happened when I got an Eathlink agent, (they use TWC here), got a promo, talked for a while, got along,  and he set it up with permanent turbo, who knows.<br><br>Sorry for the bore on, but I thought maybe if I wrote it, my obsession with speed would go away, just like the additional 35 bucks.<br><br>I forgot one thing. I had to edit this. Of all things, my modem has never restarted itself. Sorry, I really deserve that part too or I won't feel proper.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-SB6141-Reset-and-bore-on-28160480</guid>
<pubDate>Tue, 02 Apr 2013 04:43:48 EDT</pubDate>
</item>

<item>
<title>Re: SB6141 Firmware Update?</title>
<link>http://www.dslreports.com/forum/Re-SB6141-Firmware-Update-28105824</link>
<description><![CDATA[tonyram57 posted : I just read that someones SB6141 purchased modem was downgraded to 1.0.6.3.  So TWC won't update your firmware but they will downgrade to a buggy firmware on a purchased modem.<br><br>I have a white retail SB6141 that I exchanged because it comes with 1.0.6.8.  If TWC downgrades the firmware to 1.0.6.3 I am going to be really ticked off.  They won't update your firmware but they will downgrade it which is proof that they can push firmware to purchased modems.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-SB6141-Firmware-Update-28105824</guid>
<pubDate>Fri, 15 Mar 2013 13:35:22 EDT</pubDate>
</item>

<item>
<title>Re: SB6141 Firmware Update?</title>
<link>http://www.dslreports.com/forum/Re-SB6141-Firmware-Update-28068896</link>
<description><![CDATA[MURICA posted : <div class="bquote"><said>said by <a href="/profile/1343930" onClick="this.blur(); return popup(event,'/uidpop?ajh=1&uid=1343930');">Meatball</a>:</said><p>I think you guys changed my mind, this isn't Motorolla's fault.  They're just following the DOCSIS 3 standard.  The blame for all this lies squarely in the lap of Time Warner Cable.<br> </p></div>It is Motorola's fault for having this bug in their firmware in the first place. Motorola should be replacing their faulty modems with replacements that have the latest firmware if the ISP won't do it. They sold a product which does not function as advertised. It should be their responsibility to fix it.<br><br>As a prominent member of CableLabs, the developer of the DOCSIS standards, Motorola also deserves some blame for not trying to use their leverage to block this moronic restriction on what the customer can do with their own hardware when the DOCSIS 3.0 standards were being developed.<br><br>Time Warner also deserves a share of the blame for not being willing to flash customer owned modems.<br><br>There's plenty of blame to go around here, but unfortunately playing the blame game won't fix this problem. Purchasing a modem which does not have this bug in its firmware is your only option.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-SB6141-Firmware-Update-28068896</guid>
<pubDate>Tue, 05 Mar 2013 02:23:07 EDT</pubDate>
</item>

<item>
<title>Re: SB6141 Firmware Update?</title>
<link>http://www.dslreports.com/forum/Re-SB6141-Firmware-Update-28068600</link>
<description><![CDATA[permutations posted : <div class="bquote"><said>said by <a href="/profile/1030204" onClick="this.blur(); return popup(event,'/uidpop?ajh=1&uid=1030204');">NetFixer</a>:</said><p>Not all ISPs punish their customers (and indirectly their own tech support staff) just because the customer owns the modem. Comcast updates the firmware on customer owned modems the same as it does for its leased modems. In fact, they are currently starting to push the latest 1.0.6.10 firmware for the SB612x and SB6141 modems to those modems that are attached to their network. They don't care who owns it, they only want all modems of the same class to have the same firmware for performance and support purposes. </p></div>That's heartwarming. I'm glad to hear it. It certainly does sound like TWC deserves the blame. Their business practices are moronic in so many ways, why should I be surprised at one more dumb policy?<br><br>Murica - this isn't Motorola's choice. Like Meatball said, it's the DOCSIS 3 standard. Motorola <i>can't</i> do it. It's the responsibility of the cable internet provider.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-SB6141-Firmware-Update-28068600</guid>
<pubDate>Mon, 04 Mar 2013 23:17:51 EDT</pubDate>
</item>

<item>
<title>Re: SB6141 Firmware Update?</title>
<link>http://www.dslreports.com/forum/Re-SB6141-Firmware-Update-28068581</link>
<description><![CDATA[Meatball posted : I think you guys changed my mind, this isn't Motorolla's fault.  They're just following the DOCSIS 3 standard.  The blame for all this lies squarely in the lap of Time Warner Cable.<br><br><a href="http://www.timewarnercable.com/en/residential-home/support/topics/internet/buy-your-modem.html">Time Warner has 7 modems that you can 'buy'</a> that they say are compatible with the DOCSIS 3.0 service.<br><br><b>Vendor 	Model</b><br>Motorola 	SBG6580<br>Motorola 	SB6141<br>Netgear  	CMD31T<br>Motorola 	SB6121<br>Zoom 	5341J<br>Zoom 	5350<br>ZyXEL 	CDA-30360<br><br>I checked every one of of them and none of them offer firmware upgrades for end users, they all say the ISP is supposed to do it.  Heck, the ZyXEL modem is discontinued.<br><br>Man, every day I think I can't dislike the support and business practices of Time Warner Cable any more, and yet every day I'm amazed that I find a new reason.  ]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-SB6141-Firmware-Update-28068581</guid>
<pubDate>Mon, 04 Mar 2013 23:12:13 EDT</pubDate>
</item>

<item>
<title>Re: SB6141 Firmware Update?</title>
<link>http://www.dslreports.com/forum/Re-SB6141-Firmware-Update-28068495</link>
<description><![CDATA[MURICA posted : Pretty incredible that the T3 timeout issue is still going on and both sides are too full of bureaucracy to get anything fixed.<br><br>I had trouble with this in July of last year. As it stands now the only way to ensure you get a properly working DOCSIS 3.0 modem on Time Warner Cable's network is to ditch Motorola altogether. I've had issues with SB6141s and SBG6850s.<br><br>Want to know what fixed it? I sent the SB6141 back to Amazon and bought a Ubee DDW3611 off eBay and stuck it in bridge mode. Never again would I see a T3 timeout error. It's been rock solid these past 9 months.<br><br> Motorola used to be known as a reliable modem manufacturer. They really dropped the ball on this one. It may indeed be fixed in a recent firmware but imo Motorola doesn't deserve our support. I don't appreciate being treated like a criminal and told I can't update my own hardware because they're too incompetent to find a way to stop pirates that doesn't involve punishing the legitimate customer.<br><br> With no way to update them, every modem that Motorola has sold to a customer up until this update is essentially a $100 brick. I'm surprised no one has filed a lawsuit yet.<br><br>The Ubees have worked from day one and for that reason Ubee gets my support.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-SB6141-Firmware-Update-28068495</guid>
<pubDate>Mon, 04 Mar 2013 22:39:24 EDT</pubDate>
</item>

<item>
<title>Re: SB6141 Firmware Update?</title>
<link>http://www.dslreports.com/forum/Re-SB6141-Firmware-Update-28067742</link>
<description><![CDATA[NetFixer posted : <div class="bquote"><said>said by <a href="/profile/1859033" onClick="this.blur(); return popup(event,'/uidpop?ajh=1&uid=1859033');">permutations</a>:</said><p><div class="bquote"><said>said by <a href="/profile/1343930" onClick="this.blur(); return popup(event,'/uidpop?ajh=1&uid=1343930');">Meatball</a>:</said><p>...but then they shouldn't be allowed to sell it directly to end users without some sort of auto updating feature built in.  They're happy to take your $70-$100 for the modem, but if it won't work b/c the firmware is too old, oh well.<br> </p></div>I agree!! Motorola's consumer-targeted modems should have to be sold with a prominent disclaimer, like with cigarettes. For example: <br><br>"<b>WARNING: The firmware in consumer-owned cable modems will never be updated. Neither consumers nor manufacturers are allowed to do it (per the DOCSIS standard), and cable internet providers refuse to update the firmware of a modem they do not own. So if there's a bug in the current version, it will never be fixed. Nor can future compatibility issues be addressed.</b>"<br> </p></div>That would not be correct. Not all ISPs punish their customers (and indirectly their own tech support staff) just because the customer owns the modem. Comcast updates the firmware on customer owned modems the same as it does for its leased modems. In fact, they are currently starting to push the latest 1.0.6.10 firmware for the SB612x and SB6141 modems to those modems that are attached to their network. They don't care who owns it, they only want all modems of the same class to have the same firmware for performance and support purposes.<br><br>Your problem is with your ISP, not with the modem or the modem's manufacturer. DOCSIS standards require that the ISP do the firmware updating and configuration for security reasons; if your ISP is not honoring its commitment to the DOCSIS standards, then place the blame where it belongs.<br><small>--<br>A well-regulated militia, being necessary to the security of a free State, the right of the people to keep and bear arms shall not be infringed.<br><br>When governments fear people, there is liberty. When the people fear the government, there is tyranny.</small>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-SB6141-Firmware-Update-28067742</guid>
<pubDate>Mon, 04 Mar 2013 18:41:37 EDT</pubDate>
</item>

<item>
<title>Re: SB6141 Firmware Update?</title>
<link>http://www.dslreports.com/forum/Re-SB6141-Firmware-Update-28067617</link>
<description><![CDATA[permutations posted : <div class="bquote"><said>said by <a href="/profile/1343930" onClick="this.blur(); return popup(event,'/uidpop?ajh=1&uid=1343930');">Meatball</a>:</said><p>...but then they shouldn't be allowed to sell it directly to end users without some sort of auto updating feature built in.  They're happy to take your $70-$100 for the modem, but if it won't work b/c the firmware is too old, oh well.<br> </p></div>I agree!! Motorola's consumer-targeted modems should have to be sold with a prominent disclaimer, like with cigarettes. For example: <br><br>"<b>WARNING: The firmware in consumer-owned cable modems will never be updated. Neither consumers nor manufacturers are allowed to do it (per the DOCSIS standard), and cable internet providers refuse to update the firmware of a modem they do not own. So if there's a bug in the current version, it will never be fixed. Nor can future compatibility issues be addressed.</b>"]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-SB6141-Firmware-Update-28067617</guid>
<pubDate>Mon, 04 Mar 2013 18:02:29 EDT</pubDate>
</item>

<item>
<title>Re: SB6141 Firmware Update?</title>
<link>http://www.dslreports.com/forum/Re-SB6141-Firmware-Update-28066869</link>
<description><![CDATA[Meatball posted : Hey, I'm fine with that, but then they shouldn't be allowed to sell it directly to end users without some sort of auto updating feature built in.  They're happy to take your $70-$100 for the modem, but if it won't work b/c the firmware is too old, oh well.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-SB6141-Firmware-Update-28066869</guid>
<pubDate>Mon, 04 Mar 2013 14:53:18 EDT</pubDate>
</item>

<item>
<title>Re: SB6141 Firmware Update?</title>
<link>http://www.dslreports.com/forum/Re-SB6141-Firmware-Update-28066687</link>
<description><![CDATA[permutations posted : <div class="bquote"><said>said by <a href="/profile/1343930" onClick="this.blur(); return popup(event,'/uidpop?ajh=1&uid=1343930');">Meatball</a>:</said><p>I wonder if someone smarter than I can figure out a way to pull the firmware image off one of the newer modems. If that's the case, I'm sure we could push it up to the older ones since according to Motorolla one of the benefits of the modems are to be able to "Easily add the SB6141 to a deployed family of SB6120s and SB6121s, all three models utilize the same firmware image. This reduces qualification time and eliminates setup headaches." I'm pretty sure the modem has tftp built in, and if that's the case I wonder if there is a way to pull and push the image file. </p></div>Apparently there are serious security issues in letting end-users flash firmware in cable modems because they could hack it. That's why the DOCSIS standard allows it only to be done through the cable. The Motorola site has two sections describing the SB6141 - one aimed at end-users, and one aimed at cable internet providers. The part you quote is clearly aimed at cable internet providers.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-SB6141-Firmware-Update-28066687</guid>
<pubDate>Mon, 04 Mar 2013 14:22:08 EDT</pubDate>
</item>

<item>
<title>Re: SB6141 Firmware Update?</title>
<link>http://www.dslreports.com/forum/Re-SB6141-Firmware-Update-28065281</link>
<description><![CDATA[Meatball posted : I did find this one other little tidbit on Motorola's site.<br><br><a haref="http://broadband.custhelp.com/app/answers/detail/a_id/17811">http://broadband.custhelp.com/app/answers/detail/a_id/17811</a><br><br>"<i>Can I upgrade the Firmware on my Motorola Cable Modem?<br><br>We apologize about the inconvenience, but your Motorola modem does not support manual upgrades. Motorola is not allowed to control the upgrades of DOCSIS devices, per the standards specification.  Any firmware or software changes must be implemented via the cable network. Your cable provider can update the firmware based on what they have approved for their network distribution. Because of that Motorola is not capable of installing firmware for cable modems.  Please contact the cable operator to obtain information on upgrading firmware on the cable modem.</i>"<br><br>If it's truly in the DOCSIS standard that vendors can't control the upgrades then this is squarely on the shoulders of ISP's purposely trying to screw customers to try to force them to lease directly from them.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-SB6141-Firmware-Update-28065281</guid>
<pubDate>Mon, 04 Mar 2013 08:02:15 EDT</pubDate>
</item>

<item>
<title>Re: SB6141 Firmware Update?</title>
<link>http://www.dslreports.com/forum/Re-SB6141-Firmware-Update-28065278</link>
<description><![CDATA[Meatball posted : Perm, I didn't get to the point of emailed execs as it cleared up before I did.  On the other hand, I had posted my woes about TWC on twitter and was contacted by someone on their Social Media team.  She didn't really help, but she was able to credit me a month of service.  As for starting a war, I know the feeling.  I didn't want to, but by the same token, I couldn't deal with the service the way it was, I work from home.  You can only drop out of so many conference calls with your boss before he/she starts to get mad.<br><br>I wonder if someone smarter than I can figure out a way to pull the firmware image off one of the newer modems.  If that's the case, I'm sure we could push it up to the older ones since according to Motorolla one of the benefits of the modems are to be able to "Easily add the SB6141 to a deployed family of SB6120s and SB6121s, all three models utilize the same firmware image. This reduces qualification time and eliminates setup headaches."  I'm pretty sure the modem has tftp built in, and if that's the case I wonder if there is a way to pull and push the image file.<br><br>Anyone?]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-SB6141-Firmware-Update-28065278</guid>
<pubDate>Mon, 04 Mar 2013 07:58:30 EDT</pubDate>
</item>

<item>
<title>Re: SB6141 Firmware Update?</title>
<link>http://www.dslreports.com/forum/Re-SB6141-Firmware-Update-28065071</link>
<description><![CDATA[permutations posted : I called Level 3 tech support at TWC tonight and asked whether they'd ever upgrade the firmware of a consumer-owned cable modem. He said absolutely not. Never. For that reason alone, it makes no sense to me to own my own cable modem. I wish they'd mentioned that critical detail when they sent out the announcement of the rental fee and the option to buy my own. <br><br>What jerks they are. They are costing themselves a ton of money with this policy. Many (most?) of the SB6141 problems are due to outdated firmware. Consider what they've spent in man-hours just on Meatball and myself. They (and we) could have avoided all this pain had they simply thought out the situation better. The only reason that TWC is still in business is they have a monopoly on high-speed internet in many places (including my apartment building, which is too small for Verizon Wireless to invest in high-speed FIOS).<br><br>Meatball, did you ever email TWC execs about your troubles? You talked about planning to do it several times in this thread. If you did, what was the response? How about the other strategies (tweeting to @twc and posting to consumerist.com). I'm hesitant to start a war with TWC when I'm so dependent on their good will. I'm afraid that will only make things worse.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-SB6141-Firmware-Update-28065071</guid>
<pubDate>Mon, 04 Mar 2013 01:38:40 EDT</pubDate>
</item>

<item>
<title>Re: SB6141 Firmware Update?</title>
<link>http://www.dslreports.com/forum/Re-SB6141-Firmware-Update-28064797</link>
<description><![CDATA[Meatball posted : <div class="bquote"><said>said by <a href="/profile/917132" onClick="this.blur(); return popup(event,'/uidpop?ajh=1&uid=917132');">swintec</a>:</said><p><div class="bquote"><said>said by <a href="/profile/1859033" onClick="this.blur(); return popup(event,'/uidpop?ajh=1&uid=1859033');">permutations</a>:</said><p>One thing I've discovered that you haven't mentioned... The black Motorola 6141 modems that you can buy on Amazon or eBay are NOT new, no matter what they're advertised as. That's why they have old firmware.<br> </p></div>They have old(er) firmware because that is what was current when the modems were built, at that time.  Do you think it is simply coincidence that the new white versions recently debuted for the retail channels have a newer firmware version?  Of course not.<br> </p></div>I don't know, he might be onto something about the 'used' modems.  My 6121 showed up the other day in a nice new box, everything looked great, yet strangely enough I noticed there were two entries in the log from last fall about the modem rebooting and such and the modem firmware is circa Dec. 2010.<br><br>On the plus side, it's been up a full 48 hours without a single hiccup.  If only I could get TWC to push the new firmware or Moto to give it out.<br><br>Perm, there's a few things you can try to get out of the mess you are in with them.  Can't promise they'll help, but they might.<br><br>1) If you are on any social networks such as Facebook/Twitter, post about your problems.  TWC hates bad press as much as the next guy and you may get one of their "Social Media" people who will do whatever they can to get you to stop posting bad stuff about them.<br><br>2) Go to a site like the Consumerist.com and send them your problem in all it's sordid detail.  They might post it, and that'll definitely help you get some traction.<br><br>3) Try to find some TWC exec emails and start email blasting them.  Last thing they want to deal with is a bunch of emails from irate customers and they may be able to twist the right arms behind the scenes to get it fixed.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-SB6141-Firmware-Update-28064797</guid>
<pubDate>Sun, 03 Mar 2013 22:44:39 EDT</pubDate>
</item>

<item>
<title>Re: SB6141 Firmware Update?</title>
<link>http://www.dslreports.com/forum/Re-SB6141-Firmware-Update-28064706</link>
<description><![CDATA[swintec posted : <div class="bquote"><said>said by <a href="/profile/1859033" onClick="this.blur(); return popup(event,'/uidpop?ajh=1&uid=1859033');">permutations</a>:</said><p>One thing I've discovered that you haven't mentioned... The black Motorola 6141 modems that you can buy on Amazon or eBay are NOT new, no matter what they're advertised as. That's why they have old firmware.<br> </p></div>They have old(er) firmware because that is what was current when the modems were built, at that time.  Do you think it is simply coincidence that the new white versions recently debuted for the retail channels have a newer firmware version?  Of course not.<br><small>--<br><A HREF="http://blocknews.net">Usenet Block Accounts</a> | <A HREF="http://usenetnow.net">Unlimited Accounts</a></small>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-SB6141-Firmware-Update-28064706</guid>
<pubDate>Sun, 03 Mar 2013 22:06:53 EDT</pubDate>
</item>

<item>
<title>Re: SB6141 Firmware Update?</title>
<link>http://www.dslreports.com/forum/Re-SB6141-Firmware-Update-28064681</link>
<description><![CDATA[permutations posted : Meatball, you have no idea how much I identify with your ordeal. Unfortunately, I'm still going through it and it's been over a year. My problem is intermittant. My connection will be fine for a week or two, and then my modem will start "flapping" (TWC term). I envy your 2-9 disconnects per day. When my modem is flapping, it happens 6 times an hour or more - 150-200 times in a 24-hour period. I'm connected for 5-10 minutes, then disconnected for 1-2 minutes, then connected again for 5-10 minutes, etc., 24/7.<br><br>I can't count how many hours I have spent on the phone with TWC, or how many visits I've had from TWC technicians. Their procedures drive me nuts. I'm convinced that those automated calls about a problem in my area being fixed are a scam - a way to get out of sending a technician. Their computer calls to confirm appointments EVERY DAY - it drives me nuts.<br><br>I can't find the words to express how much I hate TWC. My issue has been escalated so I have a Customer Relations person working with me, but she is awful. She's snarky, she doesn't believe what I tell her, and she's a lazy do-nothing who doesn't return phone calls. Little Miss Company Girl.<br><br>One thing I've discovered that you haven't mentioned... The black Motorola 6141 modems that you can buy on Amazon or eBay are NOT new, no matter what they're advertised as. That's why they have old firmware. I called Motorola about a warranty replacement and they told me this. Dishonest vendors are buying them used from cable internet providers and selling them as new.<br><br>During the last visit I had from a TWC tech, he switched out my SB6141 for an Arris CM820. I get the same error messages with the Arris as I got with the SB6141, but it doesn't drop the connection completely - it just stutters, lags. I have old firmware on the SB6141 because it's black, and unbeknownst to me, it was not new when I bought it (I was defrauded). The firmware version is 1.0.6.3. I want to confirm the firmware update issue with TWC. If it's true, there's no point in using my own cable modem.<br><br>I work at home and use the internet heavily. This problem has cost me a fortune in Verizon Wireless data overage charges because at times I simply must have internet access. I talk to clients in other countries, and there's no other way but the internet, so I have to connect through my cell phone.<br><br>Also, like you, I have no other option but TWC or I would have dropped them long ago.<br><br>Did I mention that I hate TWC?]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-SB6141-Firmware-Update-28064681</guid>
<pubDate>Sun, 03 Mar 2013 21:56:42 EDT</pubDate>
</item>

<item>
<title>Re: SB6141 Firmware Update?</title>
<link>http://www.dslreports.com/forum/Re-SB6141-Firmware-Update-28055141</link>
<description><![CDATA[Meatball posted : Happened to notice some guys up the road the other day laying in new cable and then the other night I saw a few synch/disconnect errors.  Guessing they finally replaced whatever bad cable was out there.<br><br>I may be tempting fate, but I picked up a Motorolla 6121 on eBay and I'm going to switch over to that.  Hopefully it'll be stable so I can stop paying the modem lease fee.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-SB6141-Firmware-Update-28055141</guid>
<pubDate>Thu, 28 Feb 2013 12:24:05 EDT</pubDate>
</item>

<item>
<title>Re: SB6141 Firmware Update?</title>
<link>http://www.dslreports.com/forum/Re-SB6141-Firmware-Update-28038728</link>
<description><![CDATA[mpgstuff posted : Meatball, glad to hear your issue seems to be resolved.<br>I get a DHCP tftp "notice" in my logs every 2-4 days as well, I think this is normal.  I haven't noticed any issues because of this message.<br><br>I still see a single T3 timeout here and there, but have not experienced anything like it was (rebooting 5-20 times a day).  ]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-SB6141-Firmware-Update-28038728</guid>
<pubDate>Fri, 22 Feb 2013 22:26:53 EDT</pubDate>
</item>

<item>
<title>Re: SB6141 Firmware Update?</title>
<link>http://www.dslreports.com/forum/Re-SB6141-Firmware-Update-28026912</link>
<description><![CDATA[tonyram57 posted : I know what you are going through.  I went through this crap starting August 26th for a couple of months.  New cable drop, swapped modems etc and I still have problems sometimes at night with slow upstream.  I now own the SB6141 to see if it helps with this.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-SB6141-Firmware-Update-28026912</guid>
<pubDate>Tue, 19 Feb 2013 18:49:59 EDT</pubDate>
</item>

<item>
<title>Re: SB6141 Firmware Update?</title>
<link>http://www.dslreports.com/forum/Re-SB6141-Firmware-Update-28025396</link>
<description><![CDATA[RySean posted : Yeah, that sucks :-( I read this thread through all the way because I've been experiencing T3 and T4 timeouts regularly. I was hoping a firmware update would fix it, because I really don't want to deal with having technicians sent out since they tend to mess things up half the time, but it appears I may not have a choice :-/ What's strange is that I was using this same SB6141 at an address not far from here without issue, but once I brought it here, any amount of torrent traffic causes the internet to go out almost immediately (even with super conservative settings for connection speeds and number of connections allowed to be made). It's a bit ridiculous, hopefully I don't have to go through what you did to fix it.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-SB6141-Firmware-Update-28025396</guid>
<pubDate>Tue, 19 Feb 2013 12:25:15 EDT</pubDate>
</item>

<item>
<title>Re: SB6141 Firmware Update?</title>
<link>http://www.dslreports.com/forum/Re-SB6141-Firmware-Update-28023319</link>
<description><![CDATA[Meatball posted : Just a quick update on my whole fiasco.  It _appears_ to be fixed.  I don't know what they did, and noone will return my call to tell me if they actually fixed anything, but the last 'T3 timeout' error I ran into was back on Feb 2nd.  Since then things have been pretty solid and I've only had two or three disconnects.  I have seen a pretty regular recurrence of two DHCP errors.  I get a "DHCP RENEW WARNING - Field invalid in response v4 option;" and then a "DHCP Renew - lease parameters tftp file" every 3-4 days. <br><br>It doesn't appear to actually knock me offline, so I haven't really called in about it.  I did make 2-3 attempts to call the local supervisor that had been helping me to at least get verification that they had fixed _something_ and if they could let me know what it was so I know if it happens again, but he never answers or returns my calls.<br><br>So it took 7-8 weeks to get my issue fixed.  During that time I called their support line and talked to 30+ Level 1 & Level 3 phone technicians, 'chatted' with 10+ online chat support technicians, went to their office twice, had 9 technician trucks at my house and 5-6 maintenance trucks visit the neighborhood.  All the while having anywhere from 10-20 disconnects per day during the entire time.<br><br>TWC has some of the worst customer service I've ever seen, and if I had any other realistic option, I'd drop them in a second.  Every person you talk to or that visits your house is interested in simply closing out the 'ticket' they are working on and handing your problem off to the next person in line.  There is no ownership of any problems and they could care less if they actually fix your issue, but just that they can put a check in the box that they attempted to help.  You can be passed from online chat, to L1 phone, to L3 phone to truck at your house and to maintenance, and not one of those people are actually held accountable for your issue being fixed.  Just that they passed it on to the next step.<br><br>Until TWC makes technicians truly responsible for 'fixing' and issue and seeing it all the way to the end, they'll always be a mess.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-SB6141-Firmware-Update-28023319</guid>
<pubDate>Mon, 18 Feb 2013 19:06:54 EDT</pubDate>
</item>

<item>
<title>Re: SB6141 Firmware Update?</title>
<link>http://www.dslreports.com/forum/Re-SB6141-Firmware-Update-28023275</link>
<description><![CDATA[Meatball posted : Yeah, I'd almost bet my modem that they will not upgrade yours b/c you own it.  Multiple people I talked to made it point to specifically state that they 'do not upgrade customer owned equipment'.  They claim it's due to the fact that since they don't own it, if they brick it, they don't want to be responsible for replacement.  And while that's probably partially true, I'm sure they also want to do whatever they can to drive folks to rent from them.<br><br>I don't even have the option to rent the 6141 here, only the old Ubee or the Arris DG860.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-SB6141-Firmware-Update-28023275</guid>
<pubDate>Mon, 18 Feb 2013 18:49:59 EDT</pubDate>
</item>

<item>
<title>Re: SB6141 Firmware Update?</title>
<link>http://www.dslreports.com/forum/Re-SB6141-Firmware-Update-28022959</link>
<description><![CDATA[RySean posted : There's a new firmware update for Time Warner cable for the SB6141, apparently as of today :-D It's SB_KOMODO-1.0.6.10-SCM00-NOSH according to the TWC rep I talked to. They said they couldn't push it manually, but it would be rolling out over time. Hopefully that doesn't exclude mine which is owned by me rather than rented.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-SB6141-Firmware-Update-28022959</guid>
<pubDate>Mon, 18 Feb 2013 16:50:12 EDT</pubDate>
</item>

<item>
<title>Re: SB6141 Firmware Update?</title>
<link>http://www.dslreports.com/forum/Re-SB6141-Firmware-Update-27949199</link>
<description><![CDATA[Meatball posted : They haven't offered January reimbursement yet, but we'll see.  At this point I've about exhausted every support avenue I have.  Still having the issues and L1 can't help, they pass me up to L3.  I've talked to two L3 guys in the last day that were both oblivious.  One said he couldn't schedule maintenance directly and would have to send out another tech.  Another told me that I should get business class service with a static IP, because that's my problem.  What? <br><br>So, my only hope left is that local supervisor who only returns 1 out of 10 of my calls.  I called him twice and left voicemails in the last 24 hours telling him I'm still having issues.<br><br>They have till Tuesday evening to fix this.  I won't be around/doing much online until then and it gives them 4 days.  At that point I'm going to email blast my text log file (now up to 28 KB in size) of everything that's happened to any TWC executive I can find.<br><br>So, does anyone know where I can find email addresses for TWC executives? ]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-SB6141-Firmware-Update-27949199</guid>
<pubDate>Sat, 26 Jan 2013 11:15:44 EDT</pubDate>
</item>

<item>
<title>Re: SB6141 Firmware Update?</title>
<link>http://www.dslreports.com/forum/Re-SB6141-Firmware-Update-27949138</link>
<description><![CDATA[mpgstuff posted : Meatball, I appreciate you keeping this thread up to date.  When I read this all I can do is shake my head, I truly hope they fix this soon.  <br><br>Have they offered to refund you January's service cost?<br><br>As far as switching back to the Motorola SB6141 once it's fixed, in my personal experience, I haven't had any problems.  I was receiving the same disconnects/timeouts as you describe and show in your logs, but I guess we can't say for sure the root cause is the same (I don't know what they actually fixed in my case, I received an automated call saying something was fixed in the neighborhood.  Several days later I had a tech come out for a pre-existnig appointment and he put a new line in from outside to inside, put an AMP and a new splitter in - I truly don't think this "fixed anything".  Whatever they fixed in the neighborhood did it).<br><br>My SB6141 has been up since the 9th, when the tech visited and started snipping all the wires.  To my knowledge, there have been no issues.  I get advertised speeds, my latency is fine (although Fri/Sat nights I do experience short spikes, that could be/probably is something on my end of the network).<br><br>Over the 16 day period, I still see an occasional "No Ranging Response received T3 Timeout".  My log is still showing the messages from the 9th (with this issue, as you know, the log would completely fill up and turnover multiple times in a day - so I guess this is a "good" sign that there aren't a ton of messages).  Since the 9th I show 5 "T3 Timeouts", but I haven't noticed them.<br><br>Good luck and keep us updated.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-SB6141-Firmware-Update-27949138</guid>
<pubDate>Sat, 26 Jan 2013 10:54:32 EDT</pubDate>
</item>

<item>
<title>Re: SB6141 Firmware Update?</title>
<link>http://www.dslreports.com/forum/Re-SB6141-Firmware-Update-27945519</link>
<description><![CDATA[Meatball posted : Well, here's the latest and greatest.  Talking to L3 on Tuesday night, he saw that maintenance was supposed to be out, but there were no notes, so he asked for an update and was going to check into it.  They'd call me.  (Yeah, I've heard that before.)<br><br>Wednesday I wasn't home most of the day, but when I did get home I saw I had had 2 disconnects, so I called in again and immediately got bumped up to L3.  This L3 tech told me that noone had put a maintenance request in until that morning, but they had not come out that day.  She said they should be out the next day.<br><br>Thursday I was out again most of the day, but around 5:30 at night the supervisor that had been ignoring called and left me a long VM.  Apparently my call to L3 must have kicked them going again and he said they were watching the modems on the street that day and were seeing some spikes and corrections.  He had talked to a maintenance supervisor and they were sending out a truck that night to replace the GNA/Amplifier down at the end of the block.  He said if that didn't work, everything had been changed out other than the 'tap face plate' and they'd have to hand over the information to Engineering so they could look to see if there was a problem with the card servicing our area.<br><br>I didn't get home till close to 8 PM, so I don't know if the truck actually showed up.  I had 3 disconnects Thursday before that 5:30 PM call from the supervisor, but nothing in the 12 hours since.  So, now I wait and see if any errors pop up.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-SB6141-Firmware-Update-27945519</guid>
<pubDate>Fri, 25 Jan 2013 05:37:05 EDT</pubDate>
</item>

<item>
<title>Re: SB6141 Firmware Update?</title>
<link>http://www.dslreports.com/forum/Re-SB6141-Firmware-Update-27937884</link>
<description><![CDATA[Meatball posted : Ah, all good things come to an end.  I was hopeful when I got up this morning and still hadn't disconnected.  I had to go into work today, so I was gone most of the day, but after 25 hours of no disconnects, I dropped.  Then dropped again a few hours later.  So, we're back in the same boat.  <br><br>Supervisor is now ignoring my calls, so I'm back to calling TWC support directly and seeing if they can get the trucks out here.  Talking to L3 support right now.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-SB6141-Firmware-Update-27937884</guid>
<pubDate>Tue, 22 Jan 2013 21:35:11 EDT</pubDate>
</item>

<item>
<title>Re: SB6141 Firmware Update?</title>
<link>http://www.dslreports.com/forum/Re-SB6141-Firmware-Update-27934420</link>
<description><![CDATA[Meatball posted : As it stands right now, I've not seen a disconnect for 12 hours.  Of course, I've seen it go 20 hours on occasion and then go crazy again.  Maybe they were out here first thing AM and finally figured out what the problem was, but I didn't see any trucks and noone called me to say anything was fixed.<br><br>Until I see this thing stable for 48 hours I won't get my hopes up, and I won't believe it's been fixed until I see it stable for 5-7 days.<br><br>That leads me to the next question, once I believe it's fixed, do I take the risk of tossing the Moto back in since the firmware is already 19 months old and will never get updated. :)]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-SB6141-Firmware-Update-27934420</guid>
<pubDate>Mon, 21 Jan 2013 22:01:00 EDT</pubDate>
</item>

<item>
<title>Re: SB6141 Firmware Update?</title>
<link>http://www.dslreports.com/forum/Re-SB6141-Firmware-Update-27933970</link>
<description><![CDATA[JohnnyG101 posted : let us know how this plays out if you dont mind.  <br><br>Sucks about the whole firmware update problem.  I do understand their position but I wish there was a way for us to do it on our own. oh well.<br><small>--<br>Driving with 2 feet since 1999</small>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-SB6141-Firmware-Update-27933970</guid>
<pubDate>Mon, 21 Jan 2013 19:39:28 EDT</pubDate>
</item>

<item>
<title>Re: SB6141 Firmware Update?</title>
<link>http://www.dslreports.com/forum/Re-SB6141-Firmware-Update-27930923</link>
<description><![CDATA[Meatball posted : Yeah, I've had a joyous time in the last day or so.  I had 8 disconnects yesterday after the tech left, and today I've had at least 19.  I say at least because the modem log only holds the last 20 entries and there were about 10 hours that I can't actually account for because by the time I was home/awake to check the log, it had rolled over past a big block of entries.<br><br>On average I'm seeing the full disconnect every 20-30 minutes.  I've called the supervisor twice today (he's off, so not answering) and the tech that was out here today.  The tech actually answered and said 'he'll see what he can do', but I'm not holding my breath.  If they haven't called me by 9 AM tomorrow morning, I'm going on a calling spree.<br><br>And I've about had it with this.  I work from home, so this is just absolutely unacceptable.  I feel like I've been patient enough and with almost 7 weeks of issues if this isn't fixed by Friday I'm going to start hunting for every TWC exec email I can find and email them my text log detailing every call/visit and disconnect I've been seeing.  That text file is over 450 lines long and 20Kb in size already.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-SB6141-Firmware-Update-27930923</guid>
<pubDate>Sun, 20 Jan 2013 20:22:21 EDT</pubDate>
</item>

</channel>
</rss>
