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

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

<channel>
<title>Topic &#x27;[TWC] Frequent disconnects, TWC claims everything is fine&#x27; in forum &#x27;Time Warner Internet Services&#x27; - dslreports.com</title>
<link>http://www.dslreports.com/forum/TWC-Frequent-disconnects-TWC-claims-everything-is-fine-27748883</link>
<description></description>
<language>en</language>
<pubDate>Sat, 18 May 2013 20:47:09 EDT</pubDate>
<lastBuildDate>Sat, 18 May 2013 20:47:09 EDT</lastBuildDate>

<item>
<title>Re: [TWC] Frequent disconnects, TWC claims everything is fine</title>
<link>http://www.dslreports.com/forum/Re-TWC-Frequent-disconnects-TWC-claims-everything-is-fine-27777276</link>
<description><![CDATA[mackey posted : Pshhhh, although 0 is "perfect," 7dBmV works just fine.  Mine varies between 6 and 7 now that I put a 12db attenuator on there; it was locking up without it.  Grab yourself a 6db attuenuator  off amazon if you really want to, but really it's fine as it is.<br><br>/M]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-TWC-Frequent-disconnects-TWC-claims-everything-is-fine-27777276</guid>
<pubDate>Fri, 30 Nov 2012 21:46:10 EDT</pubDate>
</item>

<item>
<title>Re: [TWC] Frequent disconnects, TWC claims everything is fine</title>
<link>http://www.dslreports.com/forum/Re-TWC-Frequent-disconnects-TWC-claims-everything-is-fine-27773175</link>
<description><![CDATA[Bigman397 posted : Now your signal is a bit too hot. Put a splitter in front of the modem to reduce signal a bit, try to keep things as close to 0dbmv on the downstream power levels. Definately keep it under 5dbmv]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-TWC-Frequent-disconnects-TWC-claims-everything-is-fine-27773175</guid>
<pubDate>Thu, 29 Nov 2012 18:46:59 EDT</pubDate>
</item>

<item>
<title>Re: [TWC] Frequent disconnects, TWC claims everything is fine</title>
<link>http://www.dslreports.com/forum/Re-TWC-Frequent-disconnects-TWC-claims-everything-is-fine-27767127</link>
<description><![CDATA[Jedis posted : Update:<br><br>TWC came out today and found the coax cable was badly damaged out on their pole. They repaired the cable. We were able to get them to swap out our old Motorola SB5101U for a brand new Motorola SB6141. New stats are below:<br><br>&raquo;<A HREF="http://i.imgur.com/WhAJV.png" >i.imgur.com/WhAJV.png</A><br><br>Anything I should keep an eye on, or do these stats look reasonable?]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-TWC-Frequent-disconnects-TWC-claims-everything-is-fine-27767127</guid>
<pubDate>Wed, 28 Nov 2012 01:21:19 EDT</pubDate>
</item>

<item>
<title>Re: [TWC] Frequent disconnects, TWC claims everything is fine</title>
<link>http://www.dslreports.com/forum/Re-TWC-Frequent-disconnects-TWC-claims-everything-is-fine-27762016</link>
<description><![CDATA[Bigman397 posted : Definately a signal issue, however tracking down why it is so intermittent will be tough. You will need to get a twc rep out to check every splitter, fitting, etc... in the place and make sure nothing is wiggling lose or being subject to ingress]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-TWC-Frequent-disconnects-TWC-claims-everything-is-fine-27762016</guid>
<pubDate>Mon, 26 Nov 2012 16:42:19 EDT</pubDate>
</item>

<item>
<title>Re: [TWC] Frequent disconnects, TWC claims everything is fine</title>
<link>http://www.dslreports.com/forum/Re-TWC-Frequent-disconnects-TWC-claims-everything-is-fine-27761231</link>
<description><![CDATA[anon posted : My internet is down again. Modem light is stuck on Upstream Ranging.<br><br>Down<br>Frequency: 657000000 Locked<br>Snr: 32 dB<br>Power: -15 dBmV<br><br>Up<br>Frequency 31000000 Hz In Progress<br>Power: 24 dBmV]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-TWC-Frequent-disconnects-TWC-claims-everything-is-fine-27761231</guid>
<pubDate>Mon, 26 Nov 2012 14:03:22 EDT</pubDate>
</item>

<item>
<title>Re: [TWC] Frequent disconnects, TWC claims everything is fine</title>
<link>http://www.dslreports.com/forum/Re-TWC-Frequent-disconnects-TWC-claims-everything-is-fine-27761045</link>
<description><![CDATA[cramer posted : Go to the direct forum and post your logs full of DCC failures.<br><br>It's 30db <i>on the channel that works</i>; it may be much worse on other channels.  If he has a HDHomeRun (network tuner), then he could test the SNR of every channel; but short of that, a TWC minion would have to come out and test.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-TWC-Frequent-disconnects-TWC-claims-everything-is-fine-27761045</guid>
<pubDate>Mon, 26 Nov 2012 12:04:12 EDT</pubDate>
</item>

<item>
<title>Re: [TWC] Frequent disconnects, TWC claims everything is fine</title>
<link>http://www.dslreports.com/forum/Re-TWC-Frequent-disconnects-TWC-claims-everything-is-fine-27760086</link>
<description><![CDATA[Bigman397 posted : IYour signal(power level) looks a bit hot on the forward(downstream), getting it closer to 0dbmv would provide a much more stable connection. If you have a splitter put it in front of the modem as an easy solution, that should drop it 2-3dbmv.<br><br>An SNR of 30db is fine, this depends on the quality of the plant; the leg you are off might just be noisy. <br><br>Pay attention to the lights, when it goes out which lights specifically go off? Downstream is the forward and first to be established. Upstream or return is the second. Online is the final one to go solid, indicating the config has been loaded and the service should be ready to go.<br><br>PC activity is just a lan link indicator. It is solid or blinking in normal operation. If this light goes out while the others continue to stay on this indicates a local issue like your router going out or a bad ethernet cable.<br><br>If the TWC system shows you losing sync twice that might indicate a more local problem. Just food for thought]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-TWC-Frequent-disconnects-TWC-claims-everything-is-fine-27760086</guid>
<pubDate>Mon, 26 Nov 2012 01:44:09 EDT</pubDate>
</item>

<item>
<title>Re: [TWC] Frequent disconnects, TWC claims everything is fine</title>
<link>http://www.dslreports.com/forum/Re-TWC-Frequent-disconnects-TWC-claims-everything-is-fine-27760032</link>
<description><![CDATA[Jedis posted : What would you suggest I do to get this resolved, seeing as they claim nothing is wrong?]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-TWC-Frequent-disconnects-TWC-claims-everything-is-fine-27760032</guid>
<pubDate>Mon, 26 Nov 2012 00:38:33 EDT</pubDate>
</item>

<item>
<title>Re: [TWC] Frequent disconnects, TWC claims everything is fine</title>
<link>http://www.dslreports.com/forum/Re-TWC-Frequent-disconnects-TWC-claims-everything-is-fine-27760010</link>
<description><![CDATA[cramer posted : This *is* a TWC problem.  See all those DCC errors? That's the CMTS (headend) commanding your modem to a different channel.  Either the channel(s) is(are) unavailable to you or the signal level is too low to be usable.  Neither are within your power to fix.<br><br>Your SNR would suggest the signal is too weak, or too noisy.  TWC is lying when they say nothing is wrong.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-TWC-Frequent-disconnects-TWC-claims-everything-is-fine-27760010</guid>
<pubDate>Mon, 26 Nov 2012 00:19:53 EDT</pubDate>
</item>

<item>
<title>Re: [TWC] Frequent disconnects, TWC claims everything is fine</title>
<link>http://www.dslreports.com/forum/Re-TWC-Frequent-disconnects-TWC-claims-everything-is-fine-27759992</link>
<description><![CDATA[Jedis posted : Downstream	Value<br>Frequency:	 675000000 Hz Locked<br>Signal to Noise Ratio:	30 dB<br>Power Level	: 5 dBmV<br><br>Upstream	Value<br>Channel ID:	12<br>Frequency:	 31000000 Hz Ranged<br>Power Level:	46 dBmV]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-TWC-Frequent-disconnects-TWC-claims-everything-is-fine-27759992</guid>
<pubDate>Sun, 25 Nov 2012 23:56:10 EDT</pubDate>
</item>

<item>
<title>Re: [TWC] Frequent disconnects, TWC claims everything is fine</title>
<link>http://www.dslreports.com/forum/Re-TWC-Frequent-disconnects-TWC-claims-everything-is-fine-27750794</link>
<description><![CDATA[hotshot187 posted : Looks like an upstream signal problem.  Please post signal levels for modem.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-TWC-Frequent-disconnects-TWC-claims-everything-is-fine-27750794</guid>
<pubDate>Wed, 21 Nov 2012 22:33:37 EDT</pubDate>
</item>

<item>
<title>[TWC] Frequent disconnects, TWC claims everything is fine</title>
<link>http://www.dslreports.com/forum/TWC-Frequent-disconnects-TWC-claims-everything-is-fine-27748883</link>
<description><![CDATA[Jedis posted : We've been having issues for about a month now. The modem will just randomly drop the signal and the PC activity light will go out. I've tried swapping modems with no change. It is now booting everyone offline - trying to play Madden and Diablo 3 online and it stays disconnected long enough to boot everyone out of their game. TWC came out and moved the modem from upstairs to downstairs. They looked at the logs and claim everything is fine and that they only see us losing signal twice in the last month. They are either blind or not wanting to admit to any issues, as the modem has lost sync more times than that in one day.<br><br>Any suggestions? Here is the log from the modem.<br><br>Time	Priority	Code	Message<br>2012-11-21 12:10:27	3-Critical	D003.0	DHCP WARNING - Non-critical field invalid in response.<br>2012-11-21 12:10:15	3-Critical	C204.0	DCC aborted unable to acquire new downstream channel<br>2012-11-21 12:10:15	3-Critical	T002.0	SYNC Timing Synchronization failure - Failed to acquire FEC framing<br>2012-11-21 10:18:53	3-Critical	D003.0	DHCP WARNING - Non-critical field invalid in response.<br>2012-11-21 10:18:42	3-Critical	C205.0	DCC aborted no UCD for new upstream channel<br>2012-11-21 09:45:40	3-Critical	D003.0	DHCP WARNING - Non-critical field invalid in response.<br>2012-11-21 09:45:30	3-Critical	C204.0	DCC aborted unable to acquire new downstream channel<br>2012-11-21 09:45:30	3-Critical	T002.0	SYNC Timing Synchronization failure - Failed to acquire FEC framing<br>2012-11-21 07:42:52	3-Critical	R005.0	Started Unicast Maintenance Ranging - No Response received - T3 time-out<br>2012-11-21 05:41:23	3-Critical	D003.0	DHCP WARNING - Non-critical field invalid in response.<br>2012-11-21 05:41:15	3-Critical	C204.0	DCC aborted unable to acquire new downstream channel<br>2012-11-21 05:41:15	3-Critical	T002.0	SYNC Timing Synchronization failure - Failed to acquire FEC framing<br>2012-11-21 04:50:08	3-Critical	D003.0	DHCP WARNING - Non-critical field invalid in response.<br>2012-11-21 04:49:59	3-Critical	C204.0	DCC aborted unable to acquire new downstream channel<br>2012-11-21 04:49:59	3-Critical	T002.0	SYNC Timing Synchronization failure - Failed to acquire FEC framing<br>2012-11-20 23:19:26	3-Critical	D003.0	DHCP WARNING - Non-critical field invalid in response.<br>2012-11-20 23:19:20	3-Critical	R002.0	No Ranging Response received - T3 time-out<br>2012-11-20 23:19:16	3-Critical	C204.0	DCC aborted unable to acquire new downstream channel<br>2012-11-20 23:19:16	3-Critical	T002.0	SYNC Timing Synchronization failure - Failed to acquire FEC framing<br>2012-11-20 22:53:18	3-Critical	D003.0	DHCP WARNING - Non-critical field invalid in response.<br>2012-11-20 22:53:12	3-Critical	R002.0	No Ranging Response received - T3 time-out<br>2012-11-20 22:53:08	3-Critical	C204.0	DCC aborted unable to acquire new downstream channel<br>2012-11-20 22:53:08	3-Critical	T002.0	SYNC Timing Synchronization failure - Failed to acquire FEC framing<br>2012-11-20 17:58:59	3-Critical	R005.0	Started Unicast Maintenance Ranging - No Response received - T3 time-out<br>2012-11-20 17:25:35	3-Critical	T005.0	SYNC Timing Synchronization failure - Loss of Sync<br>2012-11-20 17:25:31	3-Critical	T004.0	SYNC Timing Synchronization failure - Failed to receive MAC SYNC frame within time-out period<br>2012-11-20 17:23:31	3-Critical	R005.0	Started Unicast Maintenance Ranging - No Response received - T3 time-out<br>2012-11-20 17:15:32	4-Error	C401.0	DCC-ACK not received<br>2012-11-20 17:12:28	3-Critical	D003.0	DHCP WARNING - Non-critical field invalid in response.<br>2012-11-20 17:12:19	3-Critical	C204.0	DCC aborted unable to acquire new downstream channel<br>2012-11-20 17:12:19	3-Critical	T002.0	SYNC Timing Synchronization failure - Failed to acquire FEC framing<br>2012-11-20 15:31:54	3-Critical	D003.0	DHCP WARNING - Non-critical field invalid in response.<br>2012-11-20 15:31:46	3-Critical	C204.0	DCC aborted unable to acquire new downstream channel<br>2012-11-20 15:31:46	3-Critical	T002.0	SYNC Timing Synchronization failure - Failed to acquire FEC framing<br>2012-11-20 14:25:37	3-Critical	R005.0	Started Unicast Maintenance Ranging - No Response received - T3 time-out<br>2012-11-20 00:42:26	3-Critical	D003.0	DHCP WARNING - Non-critical field invalid in response.<br>2012-11-20 00:42:19	3-Critical	C204.0	DCC aborted unable to acquire new downstream channel<br>2012-11-20 00:42:19	3-Critical	T002.0	SYNC Timing Synchronization failure - Failed to acquire FEC framing<br>2012-11-19 17:32:27	3-Critical	T004.0	SYNC Timing Synchronization failure - Failed to receive MAC SYNC frame within time-out period<br>2012-11-19 17:30:24	3-Critical	R005.0	Started Unicast Maintenance Ranging - No Response received - T3 time-out<br>2012-11-19 17:27:17	3-Critical	D003.0	DHCP WARNING - Non-critical field invalid in response.<br>2012-11-19 17:27:08	3-Critical	C205.0	DCC aborted no UCD for new upstream channel<br>2012-11-18 22:46:23	3-Critical	D003.0	DHCP WARNING - Non-critical field invalid in response.<br>2012-11-18 22:46:13	3-Critical	C206.0	DCC aborted unable to communicate on new upstream channel<br>2012-11-18 22:46:13	3-Critical	R004.0	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 timeout<br>2012-11-18 22:45:41	3-Critical	R005.0	Started Unicast Maintenance Ranging - No Response received - T3 time-out<br>2012-11-18 22:45:26	3-Critical	T002.0	SYNC Timing Synchronization failure - Failed to acquire FEC framing<br>2012-11-18 22:33:41	3-Critical	D003.0	DHCP WARNING - Non-critical field invalid in response.<br>2012-11-18 22:33:32	3-Critical	C205.0	DCC aborted no UCD for new upstream channel<br>2012-11-18 15:25:17	3-Critical	D003.0	DHCP WARNING - Non-critical field invalid in response.<br>2012-11-18 15:25:06	3-Critical	C204.0	DCC aborted unable to acquire new downstream channel<br>2012-11-18 15:25:06	3-Critical	T002.0	SYNC Timing Synchronization failure - Failed to acquire FEC framing<br>1970-01-01 00:00:09	3-Critical	D003.0	DHCP WARNING - Non-critical field invalid in response.<br>1970-01-01 00:01:15	3-Critical	R004.0	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 timeout<br>1970-01-01 00:00:42	3-Critical	R005.0	Started Unicast Maintenance Ranging - No Response received - T3 time-out<br>1970-01-01 00:00:05	3-Critical	R002.0	No Ranging Response received - T3 time-out<br>1970-01-01 00:00:10	3-Critical	D003.0	DHCP WARNING - Non-critical field invalid in response.<br>2012-11-17 12:26:59	3-Critical	R004.0	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 timeout<br>2012-11-17 12:26:27	3-Critical	R005.0	Started Unicast Maintenance Ranging - No Response received - T3 time-out<br>2012-11-17 12:25:49	3-Critical	R002.0	No Ranging Response received - T3 time-out<br>2012-11-17 12:25:44	3-Critical	C204.0	DCC aborted unable to acquire new downstream channel<br>2012-11-17 12:25:44	3-Critical	T002.0	SYNC Timing Synchronization failure - Failed to acquire FEC framing<br>2012-11-17 12:22:54	3-Critical	D003.0	DHCP WARNING - Non-critical field invalid in response.<br>2012-11-17 12:22:43	3-Critical	C204.0	DCC aborted unable to acquire new downstream channel<br>2012-11-17 12:22:43	3-Critical	T002.0	SYNC Timing Synchronization failure - Failed to acquire FEC framing<br>2012-11-17 12:02:47	3-Critical	D003.0	DHCP WARNING - Non-critical field invalid in response.<br>2012-11-17 12:02:42	3-Critical	R002.0	No Ranging Response received - T3 time-out<br>2012-11-17 12:02:38	3-Critical	C204.0	DCC aborted unable to acquire new downstream channel<br>2012-11-17 12:02:38	3-Critical	T002.0	SYNC Timing Synchronization failure - Failed to acquire FEC framing<br>2012-11-17 09:55:44	3-Critical	D003.0	DHCP WARNING - Non-critical field invalid in response.<br>2012-11-17 09:55:33	3-Critical	R002.0	No Ranging Response received - T3 time-out<br>2012-11-17 09:55:29	3-Critical	T002.0	SYNC Timing Synchronization failure - Failed to acquire FEC framing<br>2012-11-17 09:55:28	3-Critical	R004.0	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 timeout<br>2012-11-17 09:54:55	3-Critical	R005.0	Started Unicast Maintenance Ranging - No Response received - T3 time-out<br>2012-11-16 18:33:23	3-Critical	D003.0	DHCP WARNING - Non-critical field invalid in response.<br>2012-11-16 18:33:14	3-Critical	C204.0	DCC aborted unable to acquire new downstream channel<br>2012-11-16 18:33:14	3-Critical	T002.0	SYNC Timing Synchronization failure - Failed to acquire FEC framing<br>2012-11-16 16:19:32	3-Critical	D003.0	DHCP WARNING - Non-critical field invalid in response.<br>2012-11-16 16:19:24	3-Critical	T001.0	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing<br>2012-11-16 16:19:13	3-Critical	T002.0	SYNC Timing Synchronization failure - Failed to acquire FEC framing<br>2012-11-16 16:19:13	3-Critical	T001.0	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing<br>2012-11-16 16:19:12	3-Critical	T002.0	SYNC Timing Synchronization failure - Failed to acquire FEC framing<br>2012-11-16 16:19:12	3-Critical	T001.0	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing<br>2012-11-16 16:19:12	3-Critical	T002.0	SYNC Timing Synchronization failure - Failed to acquire FEC framing<br>2012-11-16 16:19:11	3-Critical	T001.0	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing<br>2012-11-16 16:19:10	3-Critical	T002.0	SYNC Timing Synchronization failure - Failed to acquire FEC framing<br>2012-11-16 16:19:06	3-Critical	T001.0	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing<br>2012-11-16 16:19:05	3-Critical	T002.0	SYNC Timing Synchronization failure - Failed to acquire FEC framing<br>2012-11-16 16:19:03	3-Critical	T001.0	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing<br>2012-11-16 16:19:03	3-Critical	T002.0	SYNC Timing Synchronization failure - Failed to acquire FEC framing<br>2012-11-16 16:19:00	3-Critical	T001.0	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing<br>2012-11-16 16:18:59	3-Critical	T002.0	SYNC Timing Synchronization failure - Failed to acquire FEC framing<br>2012-11-16 16:18:59	3-Critical	T001.0	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing<br>2012-11-16 16:18:59	3-Critical	T002.0	SYNC Timing Synchronization failure - Failed to acquire FEC framing<br>2012-11-16 16:18:58	3-Critical	T001.0	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing<br>2012-11-16 16:18:58	3-Critical	T002.0	SYNC Timing Synchronization failure - Failed to acquire FEC framing<br>2012-11-16 16:18:55	3-Critical	T001.0	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing<br>2012-11-16 16:18:55	3-Critical	T002.0	SYNC Timing Synchronization failure - Failed to acquire FEC framing<br>2012-11-16 16:18:54	3-Critical	T001.0	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing<br>2012-11-16 16:18:53	3-Critical	T002.0	SYNC Timing Synchronization failure - Failed to acquire FEC framing]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/TWC-Frequent-disconnects-TWC-claims-everything-is-fine-27748883</guid>
<pubDate>Wed, 21 Nov 2012 12:40:12 EDT</pubDate>
</item>

</channel>
</rss>
