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

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

<channel>
<title>Topic &#x27;DPC2100 new firmware&#x27; in forum &#x27;W.O.W.&#x27; - dslreports.com</title>
<link>http://www.dslreports.com/forum/DPC2100-new-firmware-27675873</link>
<description></description>
<language>en</language>
<pubDate>Mon, 20 May 2013 13:36:30 EDT</pubDate>
<lastBuildDate>Mon, 20 May 2013 13:36:30 EDT</lastBuildDate>

<item>
<title>Re: DPC2100 new firmware</title>
<link>http://www.dslreports.com/forum/Re-DPC2100-new-firmware-27719199</link>
<description><![CDATA[cincy4852000 posted : WOW technician came in and said my modem was bad. This is a modem I have owned and has been working for over 3-4 years.<br><br>He replaced it with another dpc2100 with firmware version that lower. It works now.<br><br>But I am not happy with WOW. While I dont disagree that electronic items can go bad, I dont think thats what happened here. I think this is a case of bad firmware causing the issue.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-DPC2100-new-firmware-27719199</guid>
<pubDate>Mon, 12 Nov 2012 10:39:54 EDT</pubDate>
</item>

<item>
<title>Re: DPC2100 new firmware</title>
<link>http://www.dslreports.com/forum/Re-DPC2100-new-firmware-27698421</link>
<description><![CDATA[baess posted : <div class="bquote"><said>said by <a href="/profile/1386557" onClick="this.blur(); return popup(event,'/uidpop?ajh=1&uid=1386557');">LWC</a>:</said><p>Still seeing this in the log though:<br>Tue Nov 06 01:29:30 2012  	 Error (4) 	 DCC-ACK rejected unknown transaction ID <br> Tue Nov 06 01:29:28 2012  	 Error (4) 	 DCC-ACK not received <br> 	</p></div>Seeing the same.<br><br>Always got the DCC-ACK not received.<br><br>DCC-ACK rejected unknown transaction ID is new since yesterday for me.<br><br>Dan?]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-DPC2100-new-firmware-27698421</guid>
<pubDate>Tue, 06 Nov 2012 08:56:43 EDT</pubDate>
</item>

<item>
<title>Re: DPC2100 new firmware</title>
<link>http://www.dslreports.com/forum/Re-DPC2100-new-firmware-27698221</link>
<description><![CDATA[LWC posted : My last one was Saturday morning.<br>Still seeing this in the log though:<br>Tue Nov 06 01:29:30 2012  	 Error (4) 	 DCC-ACK rejected unknown transaction ID <br> Tue Nov 06 01:29:28 2012  	 Error (4) 	 DCC-ACK not received <br> Mon Nov 05 04:35:23 2012  	 Error (4) 	 DCC-ACK rejected unknown transaction ID <br> Mon Nov 05 04:35:21 2012  	 Error (4) 	 DCC-ACK not received <br> Sun Nov 04 18:29:39 2012  	 Error (4) 	 DCC-ACK rejected unknown transaction ID <br> Sun Nov 04 18:29:37 2012  	 Error (4) 	 DCC-ACK not received <br> Sun Nov 04 06:44:35 2012  	 Error (4) 	 DCC-ACK rejected unknown transaction ID <br> Sun Nov 04 06:44:35 2012  	 Error (4) 	 DCC-ACK not received <br> Sun Nov 04 02:30:14 2012  	 Error (4) 	 DCC-ACK rejected unknown transaction ID <br> Sun Nov 04 02:30:12 2012  	 Error (4) 	 DCC-ACK not received ]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-DPC2100-new-firmware-27698221</guid>
<pubDate>Tue, 06 Nov 2012 07:16:03 EDT</pubDate>
</item>

<item>
<title>Re: DPC2100 new firmware</title>
<link>http://www.dslreports.com/forum/Re-DPC2100-new-firmware-27698012</link>
<description><![CDATA[slyphoxj posted : I haven't gotten a watchdog timer expiration since Friday morning.  My DPC2100 has been up over 3 days and 19 hours now.<br><br><knocks on (pseudo?) wooden end table>.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-DPC2100-new-firmware-27698012</guid>
<pubDate>Tue, 06 Nov 2012 01:51:48 EDT</pubDate>
</item>

<item>
<title>Re: DPC2100 new firmware</title>
<link>http://www.dslreports.com/forum/Re-DPC2100-new-firmware-27694088</link>
<description><![CDATA[baess posted : I did have another watchdog timer.  Sure hope it is the last.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-DPC2100-new-firmware-27694088</guid>
<pubDate>Mon, 05 Nov 2012 00:00:19 EDT</pubDate>
</item>

<item>
<title>Re: DPC2100 new firmware</title>
<link>http://www.dslreports.com/forum/Re-DPC2100-new-firmware-27691607</link>
<description><![CDATA[cincy4852000 posted : I am on the same firmware and I have been having tremendous problems since the last 3-4 days. I dont know if its related to firmware or 'service problems'<br><br>I have been on hold for over 75 minutes now :(<br><br>Here is the log<br> Sat Nov 03 20:37:55 2012  	 Critical (3) 	 Started Unicast Maintenance Ranging - No Response received - ... <br> Sat Nov 03 20:14:07 2012  	 Notice (6) 	 TLV-11 - unrecognized OID <br> Time Not Established 	 Critical (3) 	 DHCP FAILED - Requested Info not supported. <br> Time Not Established 	 Critical (3) 	 Started Unicast Maintenance Ranging - No Response received - ... <br> Time Not Established 	 Critical (3) 	 DHCP FAILED - Request sent, No response <br> Time Not Established 	 Critical (3) 	 Started Unicast Maintenance Ranging - No Response received - ... <br> Time Not Established 	 Critical (3) 	 DHCP FAILED - Request sent, No response <br> Time Not Established 	 Critical (3) 	 DHCP FAILED - Discover sent, no offer received <br> Time Not Established 	 Critical (3) 	 Started Unicast Maintenance Ranging - No Response received - ... <br> Sat Nov 03 17:36:46 2012  	 Critical (3) 	 DHCP FAILED - Requested Info not supported. <br> Sat Nov 03 17:36:30 2012  	 Critical (3) 	 No Ranging Response received - T3 time-out <br> Sat Nov 03 17:36:17 2012  	 Critical (3) 	 Received Response to Broadcast Maintenance Request, But no Un... <br> Sat Nov 03 17:29:46 2012  	 Critical (3) 	 Started Unicast Maintenance Ranging - No Response received - ... <br> Time Not Established 	 Critical (3) 	 DHCP FAILED - Requested Info not supported. <br> Time Not Established 	 Critical (3) 	 DHCP FAILED - Request sent, No response <br> Time Not Established 	 Critical (3) 	 DHCP FAILED - Discover sent, no offer received <br> Time Not Established 	 Critical (3) 	 No Ranging Response received - T3 time-out <br> Sat Nov 03 11:28:52 2012  	 Critical (3) 	 Started Unicast Maintenance Ranging - No Response received - ... <br> Time Not Established 	 Critical (3) 	 DHCP FAILED - Requested Info not supported. <br> Time Not Established 	 Critical (3) 	 DHCP FAILED - Request sent, No response <br> Time Not Established 	 Critical (3) 	 No Ranging Response received - T3 time-out <br> Time Not Established 	 Critical (3) 	 Received Response to Broadcast Maintenance Request, But no Un... <br> Time Not Established 	 Critical (3) 	 Started Unicast Maintenance Ranging - No Response received - ... <br> Sat Nov 03 11:17:40 2012  	 Critical (3) 	 TFTP failed - configuration file NOT FOUND ]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-DPC2100-new-firmware-27691607</guid>
<pubDate>Sun, 04 Nov 2012 00:41:50 EDT</pubDate>
</item>

<item>
<title>Re: DPC2100 new firmware</title>
<link>http://www.dslreports.com/forum/Re-DPC2100-new-firmware-27686586</link>
<description><![CDATA[baess posted : <div class="bquote"><said>said by unregwow :</said><p>Dan brought this to my attention. The timer has been removed from the configuration, in the event your modem should reset again, it should no longer have this option set.<br> </p></div>No watchdog timers that I can tell since the first one.  So not sure how the timer would have been removed but I'm at 2.5 days with no resets.<br><br>Thanks to you (oh unnamed WOW employee) and Dan ;-).]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-DPC2100-new-firmware-27686586</guid>
<pubDate>Fri, 02 Nov 2012 10:52:13 EDT</pubDate>
</item>

<item>
<title>Re: DPC2100 new firmware</title>
<link>http://www.dslreports.com/forum/Re-DPC2100-new-firmware-27683267</link>
<description><![CDATA[anon posted : Dan brought this to my attention. The timer has been removed from the configuration, in the event your modem should reset again, it should no longer have this option set.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-DPC2100-new-firmware-27683267</guid>
<pubDate>Thu, 01 Nov 2012 13:31:02 EDT</pubDate>
</item>

<item>
<title>Re: DPC2100 new firmware</title>
<link>http://www.dslreports.com/forum/Re-DPC2100-new-firmware-27679409</link>
<description><![CDATA[baess posted : <div class="bquote"><said>said by <a href="/profile/1386557" onClick="this.blur(); return popup(event,'/uidpop?ajh=1&uid=1386557');">LWC</a>:</said><p><div class="bquote"><said>said by <a href="/profile/649054" onClick="this.blur(); return popup(event,'/uidpop?ajh=1&uid=649054');">slyphoxj</a>:</said><p>Yep, I got the new firmware again... AND the @#%$#in Watchdog Timer issue AGAIN.   :(<br> </p></div>Same here.<br>Whats all this mean?<br><br> Time Not Established 	 Critical (3) 	 No Ranging Response received - T3 time-out <br> Wed Oct 31 06:53:48 2012  	 Critical (3) 	 Reset due to expiration of watchdog timer <br>  Time Not Established 	 Critical (3) 	 No Ranging Response received - T3 time-out <br> Wed Oct 31 01:10:38 2012  	 Critical (3) 	 Reset due to expiration of watchdog timer <br> </p></div>It means your modem is disconnecting and rebooting.  The new firmware is causing it.<br><br>I wonder what benefits, if any, this new firmware has that made WOW want to roll it out when they knew their customers would have the rebooting problem?]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-DPC2100-new-firmware-27679409</guid>
<pubDate>Wed, 31 Oct 2012 12:44:47 EDT</pubDate>
</item>

<item>
<title>Re: DPC2100 new firmware</title>
<link>http://www.dslreports.com/forum/Re-DPC2100-new-firmware-27679332</link>
<description><![CDATA[LWC posted : <div class="bquote"><said>said by <a href="/profile/649054" onClick="this.blur(); return popup(event,'/uidpop?ajh=1&uid=649054');">slyphoxj</a>:</said><p>Yep, I got the new firmware again... AND the @#%$#in Watchdog Timer issue AGAIN.   :(<br> </p></div>Same here.<br>Whats all this mean?<br>Wed Oct 31 07:46:28 2012  	 Error (4) 	 DCC-ACK not received <br> Wed Oct 31 06:55:00 2012  	 Notice (6) 	 TLV-11 - unrecognized OID <br> Time Not Established 	 Critical (3) 	 DHCP FAILED - Requested Info not supported. <br> Time Not Established 	 Critical (3) 	 No Ranging Response received - T3 time-out <br> Wed Oct 31 06:53:48 2012  	 Critical (3) 	 Reset due to expiration of watchdog timer <br> Time Not Established 	 Critical (3) 	 DHCP FAILED - Requested Info not supported. <br> Time Not Established 	 Critical (3) 	 No Ranging Response received - T3 time-out <br> Wed Oct 31 01:10:38 2012  	 Critical (3) 	 Reset due to expiration of watchdog timer ]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-DPC2100-new-firmware-27679332</guid>
<pubDate>Wed, 31 Oct 2012 12:26:48 EDT</pubDate>
</item>

<item>
<title>Re: DPC2100 new firmware</title>
<link>http://www.dslreports.com/forum/Re-DPC2100-new-firmware-27677994</link>
<description><![CDATA[slyphoxj posted : Yep, I got the new firmware again... AND the @#%$#in Watchdog Timer issue AGAIN.   :(]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-DPC2100-new-firmware-27677994</guid>
<pubDate>Wed, 31 Oct 2012 00:47:49 EDT</pubDate>
</item>

<item>
<title>Re: DPC2100 new firmware</title>
<link>http://www.dslreports.com/forum/Re-DPC2100-new-firmware-27677305</link>
<description><![CDATA[baess posted : Well I've already had one reboot and the log says Watchdog Timer.<br><br>With the previous firmware my modem would go months with no reboots, no issues whatsoever.<br><br>WOW knew the watchdog timer was too sensitive and I thought they were going to fix it before releasing this firmware. To quote WOW_Dan from August:<br><br><i>We are investigating what to do with the watchdog timer. It gets triggered by your modem losing connectivity briefly, the modem will reboot to resolve the issue. This was a new feature of the DPC2100 firmware, and it doesn't seem to be working exactly as it should. I see yours rebooted once on 8/27 and once on 8/29, so it's not happening too often, but it is something we're already looking into.</i><br><br>Hoping Dan will comment.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-DPC2100-new-firmware-27677305</guid>
<pubDate>Tue, 30 Oct 2012 21:00:01 EDT</pubDate>
</item>

<item>
<title>Re: DPC2100 new firmware</title>
<link>http://www.dslreports.com/forum/Re-DPC2100-new-firmware-27677274</link>
<description><![CDATA[baess posted : <div class="bquote"><said>said by <a href="/profile/1758208" onClick="this.blur(); return popup(event,'/uidpop?ajh=1&uid=1758208');">Body Count</a>:</said><p>http://www.lmgtfy.com/?q=dpc2100rx-v202r1256-120710Uas<br> </p></div>I'm aware.  I had this firmware in August and alerted Dan to the fact that the watchdog timer was rebooting too often. He acknowledged a problem and moved me and a few others back to the -060303 and no more problems.<br><br>So in August WOW knew this firmware and it's watchdog timer was too sensitive.  ]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-DPC2100-new-firmware-27677274</guid>
<pubDate>Tue, 30 Oct 2012 20:51:34 EDT</pubDate>
</item>

<item>
<title>Re: DPC2100 new firmware</title>
<link>http://www.dslreports.com/forum/Re-DPC2100-new-firmware-27677163</link>
<description><![CDATA[clocks11 posted : No update here, but maybe the DPX takes different firmware.<br><br>WebSTAR DPX2100<br>v2.0.1r1142-050302(dpx2100-v201r1142-050302a.bin)]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-DPC2100-new-firmware-27677163</guid>
<pubDate>Tue, 30 Oct 2012 20:28:47 EDT</pubDate>
</item>

<item>
<title>Re: DPC2100 new firmware</title>
<link>http://www.dslreports.com/forum/Re-DPC2100-new-firmware-27677007</link>
<description><![CDATA[Body Count posted : &raquo;<A HREF="http://www.lmgtfy.com/?q=dpc2100rx-v202r1256-120710Uas" >www.lmgtfy.com/?q=dpc2100rx-v202&middot;&middot;&middot;20710Uas</A>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-DPC2100-new-firmware-27677007</guid>
<pubDate>Tue, 30 Oct 2012 19:43:52 EDT</pubDate>
</item>

<item>
<title>DPC2100 new firmware</title>
<link>http://www.dslreports.com/forum/DPC2100-new-firmware-27675873</link>
<description><![CDATA[baess posted : At 1:45 PM today my modem rebooted and new firmware was put on.<br><br>It is now dpc2100rx-v202r1256-120710Uas.  Anyone else?<br><br>I hope this doesn't have the Watchdog Timer.<br><br>Set up page is now different too.  Maybe Dan can comment, please.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/DPC2100-new-firmware-27675873</guid>
<pubDate>Tue, 30 Oct 2012 14:50:53 EDT</pubDate>
</item>

</channel>
</rss>
