[Connectivity] Insight

Author	All Replies
soooflusterated @rr.com	[Connectivity] Insight been getting constant loss of sync for half hour chunks over the weekend, drops and stays gone for half and hour then comes back, anybody else got issues or just me? Thanks Ed
	to forum · permalink · 2009-05-10 22:14:44 ·

lilhurricane Crunchin' For Cures Premium,Mod join:2003-01-11 Purple Zone kudos:51	What area (market) are you in?
	to forum · permalink · 2009-05-10 22:15:33 ·
soooflusterated @rr.com	New Albany Ohio
	to forum · permalink · 2009-05-10 22:21:47 ·
Singular Premium join:2008-08-13 Shelbyville, KY kudos:2	reply to soooflusterated Humm... Louisville Head end seems fine. Have you logged into your modem to see what error its getting? Checked the SNR and other stats? What type of modem do you have, so that I can direct you on how to look up this information if you don't already know.
	to forum · permalink · 2009-05-10 22:41:53 ·
soooflusterated @rr.com	heres what i got, any thoughts are appricated. Thanks Frequency 555000000 Hz Signal To Noise Ratio 34.4 dB Power Level -1.5 dBmV Upstream Value Channel ID 9 Frequency 20400000 Hz Power 50.3 dBmV 2009-05-11 02:00:09 3-Critical R002.0 No Ranging Response received - T3 time-out 2009-05-11 02:00:04 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 2009-05-11 01:59:36 3-Critical R002.0 No Ranging Response received - T3 time-out 2009-05-11 01:59:06 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o 2009-05-11 01:57:44 3-Critical R002.0 No Ranging Response received - T3 time-out 2009-05-11 01:57:27 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o 2009-05-11 01:56:18 3-Critical R002.0 No Ranging Response received - T3 time-out 2009-05-11 01:56:03 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o 2009-05-11 00:30:49 3-Critical R002.0 No Ranging Response received - T3 time-out 2009-05-11 00:30:29 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o 2009-05-10 16:13:15 3-Critical R002.0 No Ranging Response received - T3 time-out 2009-05-10 16:12:56 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o 2009-05-10 16:11:44 3-Critical R002.0 No Ranging Response received - T3 time-out 2009-05-10 16:11:21 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o 2009-05-10 15:55:21 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 2009-05-10 15:55:12 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing 2009-05-10 15:55:12 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 2009-05-10 15:54:52 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o 2009-05-10 15:52:16 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 2009-05-10 15:52:15 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing 2009-05-10 15:52:07 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 2009-05-10 15:52:07 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing 2009-05-10 15:51:55 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 2009-05-10 15:51:40 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o 2009-05-10 15:49:10 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 2009-05-10 15:48:40 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o 2009-05-10 15:46:04 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 2009-05-10 15:45:28 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o 2009-05-10 15:42:59 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 2009-05-10 15:42:51 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing 2009-05-10 15:42:50 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 2009-05-10 15:42:41 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing 2009-05-10 15:42:41 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 2009-05-10 15:42:38 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing 2009-05-10 15:42:37 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 2009-05-10 15:42:31 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o 2009-05-10 15:41:00 3-Critical R002.0 No Ranging Response received - T3 time-out 2009-05-10 15:40:38 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o 2009-05-10 15:39:25 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing 2009-05-10 15:39:25 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 2009-05-10 15:39:21 3-Critical U001.0 No UCD's Received - Timeout 2009-05-10 15:38:39 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing 2009-05-10 15:38:37 3-Critical U001.0 No UCD's Received - Timeout 2009-05-10 15:36:17 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o 2009-05-10 10:23:35 3-Critical R002.0 No Ranging Response received - T3 time-out 2009-05-10 15:22:57 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing 2009-05-10 15:22:57 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 2009-05-10 15:22:55 3-Critical U001.0 No UCD's Received - Timeout 2009-05-10 15:18:23 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o 2009-05-10 15:15:41 3-Critical R002.0 No Ranging Response received - T3 time-out 2009-05-10 15:15:13 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o 2009-05-10 15:12:45 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 2009-05-10 15:12:35 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o 2009-05-10 15:10:03 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 2009-05-10 15:10:03 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing 2009-05-10 15:10:02 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 2009-05-10 15:09:55 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing 2009-05-10 15:09:54 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 2009-05-10 15:09:28 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o 2009-05-10 15:05:35 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 2009-05-10 15:05:34 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing 2009-05-10 15:05:34 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 2009-05-10 15:05:01 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o 2009-05-10 15:02:31 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 2009-05-10 15:02:03 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o 2009-05-10 14:56:46 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 2009-05-10 14:56:44 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing 2009-05-10 14:56:43 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 2009-05-10 14:56:41 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing 2009-05-10 14:56:40 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 2009-05-10 14:56:40 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing 2009-05-10 14:56:34 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 2009-05-10 14:56:33 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing 2009-05-10 14:56:22 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 2009-05-10 14:56:16 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o 2009-05-10 14:40:34 3-Critical R002.0 No Ranging Response received - T3 time-out 2009-05-10 14:40:23 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 2009-05-10 14:40:06 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing 2009-05-10 14:40:06 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 2009-05-10 14:39:51 3-Critical R002.0 No Ranging Response received - T3 time-out 2009-05-10 14:38:52 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o 2009-05-10 14:37:26 3-Critical R002.0 No Ranging Response received - T3 time-out 2009-05-10 14:37:07 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o 2009-05-10 14:35:46 3-Critical R002.0 No Ranging Response received - T3 time-out 2009-05-10 14:35:13 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 2009-05-10 14:34:23 3-Critical R002.0 No Ranging Response received - T3 time-out 2009-05-10 14:34:04 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o 2009-05-10 14:32:35 3-Critical R002.0 No Ranging Response received - T3 time-out 2009-05-10 14:30:55 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o 2009-05-10 14:29:36 3-Critical R002.0 No Ranging Response received - T3 time-out 2009-05-10 14:28:52 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 2009-05-10 14:28:44 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing 2009-05-10 14:28:44 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 2009-05-10 14:28:43 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing 2009-05-10 14:28:43 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 2009-05-10 14:28:42 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing 2009-05-10 14:28:42 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 2009-05-10 14:28:41 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing 2009-05-10 14:28:40 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 2009-05-10 14:28:34 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
	to forum · permalink · 2009-05-10 22:47:02 ·
Singular Premium join:2008-08-13 Shelbyville, KY kudos:2	reply to soooflusterated All of the errors look like the normal stuff that comes up. To be honest the log is almost a perfect match to my own. All of the numbers look to be in range as well. To be honest, I am not sure what the problem could be. Are you having any other problems with your services? The only thing I could think of is a bad modem, a problem at the head end or possibly a bad splitter, or some type of interference. Its just to hard to tell, so many variables. I think you should talk to InsighTech5 if he hasn't sent you a PM already and start a web chat and have them look over everything on their end.
	to forum · permalink · 2009-05-10 23:13:35 ·

US Cable Support > Inside Insight > [Connectivity] Insight