Search:  

 
 
   All ForumsHot TopicsGallery






how-to block ads


 
Forums » US Cable Support » Comcast » Comcast HSI » comcast cable modem sb5100
Search Topic:
Share Topic:
RSS topic:
toggle:
flat / full
normal / watch
Posting:
Post a:
Post a:
[DNS] 04-2005 Connection Problems - Discussion »
« CRAN in Pittsburgh - sucks  
AuthorAll Replies

wildstyle

join:2002-09-24
Salinas, CA

reply to wildstyle
Re: comcast cable modem sb5100

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


Big_D
Premium
join:2003-06-02
Augusta, GA

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!

Kip patterson
Premium
join:2000-10-23
Columbus, OH

reply to wildstyle
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.
Forums » US Cable Support » Comcast » Comcast HSI[DNS] 04-2005 Connection Problems - Discussion »
« CRAN in Pittsburgh - sucks  


Friday, 27-Nov 17:41:50 Terms of Use | Privacy Policy | Hosting by www.nac.net - DSL,Hosting & Co-lo | feedback | contact
over 10 years online! © 1999-2009 dslreports.com.
page compression OFF
Most commented news this week
· [119] Time Warner Cable Fires Broadside At Broadcasters
· [109] New AT&T Ad Campaign Hits Back At Verizon
· [95] Apple Joins AT&T Verizon Snark Fest
· [87] New Bill Takes Aim At Higher Verizon ETFs
· [70] TiVo Sees Record Customer Losses
· [68] In-Flight Internet Headed For Bumpy Landing?
· [60] Thanksgiving Open Thread
· [55] Verizon CEO: Hulu Will Be Dead Soon
· [38] EFF Wages War On Fine Print
· [38] ICANN Slams DNS Redirection
Most people now reading
· 5 hour energy for diabetic [General Questions]
· Windows 7 boot manager editing questions [Microsoft Help]
· 3.x Feral Druid - Bear Tanking Guide [World of Warcraft]
· HOW-TO: QoS and Tomato (fixes "choppy voice") [MagicJack]
· Leveling to 85 [World of Warcraft]
· Connecting to Google Voice Via SIP [VOIP Tech Chat]
· Whats the big deal about being "Old School"....? [World of Warcraft]
· Only firefox accesses Internet? [Security]
· Bell Response to PIPEDA Request [TekSavvy]
· Newegg Black Friday Sale started [Users Find Hot Deals]