comcast cable modem sb5100

Kip patterson Premium join:2000-10-23 Columbus, OH	reply to wildstyle Re: comcast cable modem sb5100 Ignore all SYNC messages. They mean that tin the process of rebooting the modem tried a channel that contained a TV signal rather than a modem signal. Things are not right on your end, however. The down stream signal is approaching the maximum, the upstream is approaching the minimum, and the SNR is too low. You'll need the cable company to get them fixed.
	to forum · permalink · · 2005-04-24 12:57:30 ·
Big_D Premium join:2003-06-02 Augusta, GA	reply to wildstyle Most of those entries are all from one event, you lost connection for 4 minutes at 4 am on the 19th. The others are pretty much normal. The loss of connection at 4am very well could have been some sort of maintenance event. If you are not having any problems I wouldn't worry about it. -- You want the truth? You can't handle the truth!
	to forum · permalink · · 2005-04-23 17:25:38 ·
wildstyle join:2002-09-24 Salinas, CA	reply to wildstyle 1970-01-01 00:00:49 3-Critical 0x04E33A74 Started Unicast Maintenance Ranging - No Response received - T3 time-out 1970-01-01 00:00:44 3-Critical 0x04E33948 No Ranging Response received - T3 time-out 1970-01-01 00:00:17 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 1970-01-01 00:00:03 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing 1970-01-01 00:00:03 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 1970-01-01 00:00:02 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing 1970-01-01 00:00:02 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 2005-04-19 04:08:12 3-Critical 0x04E339AC Init RANGING Critical Ranging Request Retries exhausted 2005-04-19 04:08:12 3-Critical 0x04E33948 No Ranging Response received - T3 time-out 2005-04-19 04:07:11 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 2005-04-19 04:07:09 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing 2005-04-19 04:07:08 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 2005-04-19 04:07:00 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing 2005-04-19 04:07:00 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 2005-04-19 04:06:50 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing 2005-04-19 04:06:50 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 2005-04-19 04:06:50 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing 2005-04-19 04:06:49 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 2005-04-19 04:06:48 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing 2005-04-19 04:06:48 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 2005-04-19 04:06:47 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing 2005-04-19 04:06:47 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 2005-04-19 04:06:46 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing 2005-04-19 04:06:46 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 2005-04-19 04:06:45 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing 2005-04-19 04:06:45 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 2005-04-19 04:06:40 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing 2005-04-19 04:06:40 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 2005-04-19 04:06:39 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing 2005-04-19 04:06:38 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 2005-04-19 04:06:38 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing 2005-04-19 04:06:38 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 2005-04-19 04:06:37 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing 2005-04-19 04:06:37 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 2005-04-19 04:06:36 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing 2005-04-19 04:06:36 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 2005-04-19 04:06:34 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing 2005-04-19 04:06:34 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 2005-04-19 04:06:34 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing 2005-04-19 04:06:33 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 2005-04-19 04:06:30 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing 2005-04-19 04:06:27 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 2005-04-19 04:06:27 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing 2005-04-19 04:06:25 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 2005-04-19 04:06:25 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing 2005-04-19 04:06:24 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 2005-04-19 04:06:24 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing 2005-04-19 04:06:24 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 2005-04-19 04:06:23 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing 2005-04-19 04:06:23 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 2005-04-19 04:06:21 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing 2005-04-19 04:06:21 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 2005-04-19 04:06:20 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing 2005-04-19 04:06:20 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 2005-04-19 04:06:18 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing 2005-04-19 04:06:17 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 2005-04-19 04:06:17 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing 2005-04-19 04:06:17 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 2005-04-19 04:06:09 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing 2005-04-19 04:06:08 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 2005-04-19 04:05:50 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing 2005-04-19 04:05:49 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 2005-04-19 04:05:49 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing 2005-04-19 04:05:48 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 2005-04-19 04:05:46 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing 2005-04-19 04:05:46 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 2005-04-19 04:05:43 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing 2005-04-19 04:05:42 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 2005-04-19 04:05:42 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing 2005-04-19 04:05:42 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 2005-04-19 04:05:41 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing 2005-04-19 04:05:40 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 2005-04-19 04:05:40 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing 2005-04-19 04:05:39 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 2005-04-19 04:05:37 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing 2005-04-19 04:05:37 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 2005-04-19 04:05:36 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing 2005-04-19 04:05:36 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 2005-04-19 04:05:35 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing 2005-04-19 04:05:35 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 2005-04-19 04:05:35 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing 2005-04-19 04:05:34 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 2005-04-19 04:05:32 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing 2005-04-19 04:05:32 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 2005-04-19 04:05:32 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing 2005-04-19 04:05:30 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 2005-04-19 04:05:30 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing 2005-04-19 04:05:26 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 2005-04-19 04:05:26 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing 2005-04-19 04:05:26 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 2005-04-19 04:05:23 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing 2005-04-19 04:05:23 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 2005-04-19 04:05:11 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing 2005-04-19 04:05:11 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 2005-04-19 04:05:08 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing 2005-04-19 04:05:08 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 2005-04-19 04:05:01 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing 2005-04-19 04:05:01 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 2005-04-19 04:05:00 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing 2005-04-19 04:04:59 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing Downstream Value Frequency 705000000 Hz Locked Signal to Noise Ratio 32 dB Power Level 11 dBmV The Downstream Power Level reading is a snapshot taken at the time this page was requested. Please Reload/Refresh this Page for a new reading Upstream Value Channel ID 3 Frequency 32000000 Hz Ranged Power Level 28 dBmV also did a powercycle for 10 min
	to forum · permalink · · 2005-04-23 16:09:34 ·
wildstyle join:2002-09-24 Salinas, CA	iv been looking at my log file and i need to know what this means 2005-04-23 12:44:15 3-Critical 0x04E33A74 Started Unicast Maintenance Ranging - No Response received - T3 time-out 1970-01-01 00:00:44 3-Critical 0x04E33948 No Ranging Response received - T3 time-out 1970-01-01 00:00:17 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 1970-01-01 00:00:03 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing it keeps repeating this
	to forum · permalink · · 2005-04-23 15:46:24 ·


Thursday, 03-Dec 14:10:46	Terms of Use \| Privacy Policy \| Hosting by www.nac.net - DSL,Hosting & Co-lo \| feedback \| contact over 10 years online! © 1999-2009 dslreports.com.republican-creole page compression OFF