SB5101 Config Files - dslreports.com

Author	All Replies
Johkal Cool Cat Premium,MVM join:2002-11-13 Happy Valley clubs: ·Comcast Digital Vo.. ·Comcast ·Vonage 3 edits	SB5101 Config Files I'm curious what Config files and Software Versions are being sent to Comcast customers who have an SB5101. If you have an SB5101: Post City/State where you are. Post Config File: »192.168.100.1/RgEventLog.asp Post Software Version: »192.168.100.1/RgHelp.asp *You may need to reboot modem to see Config File in log. Thanks! For Ref, my info: State College, PA Config file d11_m_sb5100_silverdeluxe_c01.cm Software Version: SB5101-2.4.1.5-SCM01-NOSH -- Write me up a 125.......I Can't Drive 55 »redrocker.com/ »cabowabo.com/
	to forum · permalink · · 2007-05-29 12:44:11 · (locked)
RR Conductor RailRoadDude Premium join:2002-04-02 Redwood Valley, CA ·Comcast 1 edit	Redwood Valley, CA (Mendocino County, NW CA-A former Adelphia area) Config File: Not sure, we're on the 8000/768 Tier though Software Version:SB5101-2.4.1.5-SCM01-NOSH Edit-We keep getting this file sent to us over and over, but it's for the 5100- SW Download INIT - Via Config file d11_m_sb5100_speedtier_c01.cm It fails everytime, for obvious reasons.
	to forum · permalink · · 2007-05-29 12:48:03 · (locked)
axelrose Ban Tornadoes join:2005-05-25 Chattanooga, TN ·Comcast 1 edit	reply to Johkal said by Johkal : If you own an SB5101: Post City/State where you are. Post Config File: »192.168.100.1/RgEventLog.asp Post Software Version: »192.168.100.1/RgHelp.asp *You may need to reboot modem to see Config File in log. Thanks! Warning, this is a VERY UBER LONG reply! NOTE:Didn't reboot modem, should I have?? City/state Chattanooga,TN Config File[s]..? Time Priority Code Description 2007-04-25 11:17:45 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 2007-04-25 11:17:35 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing 2007-04-25 11:17:33 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 2007-04-25 11:17:33 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing 2007-04-25 11:17:32 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 2007-04-25 11:17:32 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing 2007-04-25 11:17:24 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 2007-04-25 11:16:42 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o 2007-04-25 11:16:42 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing 2007-04-23 23:59:43 3-Critical R002.0 No Ranging Response received - T3 time-out 2007-04-23 23:59:38 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing 2007-04-23 23:59:33 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 2007-04-23 23:59:33 3-Critical U001.0 No UCD's Received - Timeout 2007-04-23 23:58:07 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 2007-04-23 23:58:07 3-Critical U001.0 No UCD's Received - Timeout 2007-04-23 23:57:24 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 2007-04-23 23:57:22 3-Critical U001.0 No UCD's Received - Timeout 2007-04-23 23:56:39 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 2007-04-23 23:56:38 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing 2007-04-23 23:56:37 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 2007-04-23 23:56:13 3-Critical U001.0 No UCD's Received - Timeout 2007-04-23 23:56:03 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 2007-04-23 23:55:53 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o 2007-04-23 23:55:53 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing 2007-04-20 08:22:31 3-Critical R002.0 No Ranging Response received - T3 time-out 2007-04-20 08:22:21 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 2007-04-20 08:18:51 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o 2007-04-20 08:18:51 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing 2007-04-18 17:49:27 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out 1970-01-01 00:31:29 3-Critical R002.0 No Ranging Response received - T3 time-out 1970-01-01 00:30:02 3-Critical R003.0 Init RANGING Critical Ranging Request Retries exhausted 1970-01-01 00:30:02 3-Critical R002.0 No Ranging Response received - T3 time-out 1970-01-01 00:28:50 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 1970-01-01 00:28:49 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing 1970-01-01 00:28:49 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 1970-01-01 00:28:38 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing 1970-01-01 00:28:38 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 1970-01-01 00:28:37 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing 1970-01-01 00:28:36 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 1970-01-01 00:28:30 3-Critical U001.0 No UCD's Received - Timeout 1970-01-01 00:28:09 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 1970-01-01 00:28:08 3-Critical U001.0 No UCD's Received - Timeout 1970-01-01 00:27:26 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 1970-01-01 00:27:25 3-Critical U001.0 No UCD's Received - Timeout 1970-01-01 00:27:15 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing 1970-01-01 00:27:13 3-Critical R003.0 Init RANGING Critical Ranging Request Retries exhausted 1970-01-01 00:27:13 3-Critical R002.0 No Ranging Response received - T3 time-out 1970-01-01 00:26:21 3-Critical R003.0 Init RANGING Critical Ranging Request Retries exhausted 1970-01-01 00:26:21 3-Critical R002.0 No Ranging Response received - T3 time-out 1970-01-01 00:25:25 3-Critical R003.0 Init RANGING Critical Ranging Request Retries exhausted 1970-01-01 00:25:25 3-Critical R002.0 No Ranging Response received - T3 time-out 1970-01-01 00:24:14 3-Critical R003.0 Init RANGING Critical Ranging Request Retries exhausted 1970-01-01 00:24:14 3-Critical R002.0 No Ranging Response received - T3 time-out 1970-01-01 00:23:04 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing 1970-01-01 00:22:59 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 1970-01-01 00:22:56 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing 1970-01-01 00:22:54 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 1970-01-01 00:22:54 3-Critical U001.0 No UCD's Received - Timeout 1970-01-01 00:21:27 3-Critical R003.0 Init RANGING Critical Ranging Request Retries exhausted 1970-01-01 00:21:27 3-Critical R002.0 No Ranging Response received - T3 time-out 1970-01-01 00:20:38 3-Critical R003.0 Init RANGING Critical Ranging Request Retries exhausted 1970-01-01 00:20:38 3-Critical R002.0 No Ranging Response received - T3 time-out 1970-01-01 00:19:51 3-Critical R003.0 Init RANGING Critical Ranging Request Retries exhausted 1970-01-01 00:19:51 3-Critical R002.0 No Ranging Response received - T3 time-out 1970-01-01 00:19:05 3-Critical R003.0 Init RANGING Critical Ranging Request Retries exhausted 1970-01-01 00:19:05 3-Critical R002.0 No Ranging Response received - T3 time-out 1970-01-01 00:18:09 3-Critical U001.0 No UCD's Received - Timeout 1970-01-01 00:17:26 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 1970-01-01 00:17:25 3-Critical U001.0 No UCD's Received - Timeout 1970-01-01 00:16:42 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 1970-01-01 00:16:41 3-Critical R003.0 Init RANGING Critical Ranging Request Retries exhausted 1970-01-01 00:16:41 3-Critical R002.0 No Ranging Response received - T3 time-out 1970-01-01 00:15:29 3-Critical R003.0 Init RANGING Critical Ranging Request Retries exhausted 1970-01-01 00:15:29 3-Critical R002.0 No Ranging Response received - T3 time-out 1970-01-01 00:14:26 3-Critical R003.0 Init RANGING Critical Ranging Request Retries exhausted 1970-01-01 00:14:26 3-Critical R002.0 No Ranging Response received - T3 time-out 1970-01-01 00:13:25 3-Critical R003.0 Init RANGING Critical Ranging Request Retries exhausted 1970-01-01 00:13:25 3-Critical R002.0 No Ranging Response received - T3 time-out 1970-01-01 00:12:33 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 1970-01-01 00:12:32 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing 1970-01-01 00:12:32 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 1970-01-01 00:12:08 3-Critical R003.0 Init RANGING Critical Ranging Request Retries exhausted 1970-01-01 00:12:08 3-Critical R002.0 No Ranging Response received - T3 time-out 1970-01-01 00:11:19 3-Critical R003.0 Init RANGING Critical Ranging Request Retries exhausted 1970-01-01 00:11:19 3-Critical R002.0 No Ranging Response received - T3 time-out 1970-01-01 00:10:15 3-Critical R003.0 Init RANGING Critical Ranging Request Retries exhausted 1970-01-01 00:10:15 3-Critical R002.0 No Ranging Response received - T3 time-out 1970-01-01 00:09:21 3-Critical R003.0 Init RANGING Critical Ranging Request Retries exhausted 1970-01-01 00:09:21 3-Critical R002.0 No Ranging Response received - T3 time-out 1970-01-01 00:08:16 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 1970-01-01 00:08:15 3-Critical R003.0 Init RANGING Critical Ranging Request Retries exhausted 1970-01-01 00:08:15 3-Critical R002.0 No Ranging Response received - T3 time-out 1970-01-01 00:07:29 3-Critical R003.0 Init RANGING Critical Ranging Request Retries exhausted 1970-01-01 00:07:29 3-Critical R002.0 No Ranging Response received - T3 time-out 1970-01-01 00:06:40 3-Critical R003.0 Init RANGING Critical Ranging Request Retries exhausted 1970-01-01 00:06:40 3-Critical R002.0 No Ranging Response received - T3 time-out 1970-01-01 00:05:50 3-Critical R003.0 Init RANGING Critical Ranging Request Retries exhausted 1970-01-01 00:05:50 3-Critical R002.0 No Ranging Response received - T3 time-out 1970-01-01 00:04:59 3-Critical U001.0 No UCD's Received - Timeout 1970-01-01 00:04:48 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing Software Version Software Version: SB5101-2.4.1.6-SCM02-NOSH Hardware Version: 1 MIB Version: II GUI Version: 1.0 ------------------------------------------------------- What the verdict sir? -- "If you wait by the river long enough, the bodies of your enemies will float by." - Sun Tsu (544 – 496 BC)
	to forum · permalink · · 2007-05-29 13:36:09 · (locked)
Ripper Premium join:2002-02-07 West Palm Beach, FL ·Comcast	reply to Johkal If you can't see your config file in your logs,you can use this small program to check your config file.I needed to run modem right into PC for it to work,otherwise it just reads your router info.I had to hit query a number of times before it came up.The program is called Query Tool and can be downloaded from »www.weird-solutions.com/
	to forum · permalink · · 2007-05-29 14:03:53 · (locked)
odog Cable Centric Vendor Biased Premium join:2001-08-05 Norcross, GA clubs:	Not on Comcast Software Version: SB5101-2.6.2.0-SCM00-NOSH Some version after 2.4.1.5 nukes the config name from the log entries I'm not sure which one.
	to forum · permalink · · 2007-05-29 16:46:16 · (locked)
Johkal Cool Cat Premium,MVM join:2002-11-13 Happy Valley clubs: ·Comcast Digital Vo.. ·Comcast ·Vonage	reply to axelrose When I reboot my SB5101, I see: Config file d11_m_sb5100_silverdeluxe_c01.cm You don't need to post all your log entries. Just look for the example I posted. -- Write me up a 125.......I Can't Drive 55 »redrocker.com/ »cabowabo.com/
	to forum · permalink · · 2007-05-29 18:51:39 · (locked)
RR Conductor RailRoadDude Premium join:2002-04-02 Redwood Valley, CA ·Comcast 1 edit	Are you resetting the paramaters when you reboot, or just reboot? Edit-I rebooted, but just got this again- 2007-05-29 15:03:40 4-Error E107.0 SW upgrade Failed after download - Incompatible SW file 2007-05-29 15:03:37 6-Notice E102.0 SW Download INIT - Via Config file d11_m_sb5100_speedtier_c01.cm
	to forum · permalink · · 2007-05-29 19:00:23 · (locked)
Johkal Cool Cat Premium,MVM join:2002-11-13 Happy Valley clubs: ·Comcast Digital Vo.. ·Comcast ·Vonage	You can either disconnect power from it or use the "Restart Cable Modem" option from here: »192.168.100.1/RgConfig.asp -- Write me up a 125.......I Can't Drive 55 »redrocker.com/ »cabowabo.com/
	to forum · permalink · · 2007-05-29 19:07:25 · (locked)
RR Conductor RailRoadDude Premium join:2002-04-02 Redwood Valley, CA	Should I try a "Restore Factory Defaults" too?
	to forum · permalink · · 2007-05-29 19:08:21 · (locked)
Johkal Cool Cat Premium,MVM join:2002-11-13 Happy Valley clubs: ·Comcast Digital Vo.. ·Comcast ·Vonage	I don't see a need for that. Your reboot yielded: Via Config file d11_m_sb5100_speedtier_c01.cm That's it. -- Write me up a 125.......I Can't Drive 55 »redrocker.com/ »cabowabo.com/
	to forum · permalink · · 2007-05-29 19:11:51 · (locked)
RR Conductor RailRoadDude Premium join:2002-04-02 Redwood Valley, CA	You're right, I am losing it in my old age LOL
	to forum · permalink · · 2007-05-29 19:12:44 · (locked)
Presage join:2004-06-01 Londonderry, NH 1 edit	Londonderry, NH Behind a router/don't see a config file SB5101-2.4.1.6-SCM02-NOSH
	to forum · permalink · · 2007-05-29 20:39:00 · (locked)
axelrose Ban Tornadoes join:2005-05-25 Chattanooga, TN ·Comcast	reply to Johkal said by Johkal : When I reboot my SB5101, I see: Config file d11_m_sb5100_silverdeluxe_c01.cm You don't need to post all your log entries. Just look for the example I posted. I rebooted [power off 30 sec's] and found no such entry. Is this bad, good, ok? I'm suppose to be on that dreaded 6000/384 tier With LIEboost -- "If you wait by the river long enough, the bodies of your enemies will float by." - Sun Tsu (544 – 496 BC)
	to forum · permalink · · 2007-05-29 21:00:35 · (locked)
Johkal Cool Cat Premium,MVM join:2002-11-13 Happy Valley clubs: ·Comcast Digital Vo.. ·Comcast ·Vonage	Not bad at all. The modem doesn't always have to download the config file after reboot. -- Write me up a 125.......I Can't Drive 55 »redrocker.com/ »cabowabo.com/
	to forum · permalink · · 2007-05-29 22:42:18 · (locked)
odog Cable Centric Vendor Biased Premium join:2001-08-05 Norcross, GA clubs: ·Comcast ·Metrocast Communic.. ·Vonage	said by Johkal : Not bad at all. The modem doesn't always have to download the config file after reboot. Actually it definitely should pull a file each time it reboots. Not doing so would likely get it bricked by the cmts as an anti theft of service countermeasure. It's likely axel has a firmware version that removes the config file name from the log entries.
	to forum · permalink · · 2007-05-29 23:20:59 · (locked)
Johkal Cool Cat Premium,MVM join:2002-11-13 Happy Valley clubs:	What ever the reason, some modems don't show a config file after reboot.
	to forum · permalink · · 2007-05-30 01:03:17 · (locked)
Ripper Premium join:2002-02-07 West Palm Beach, FL ·Comcast	said by Johkal : What ever the reason, some modems don't show a config file after reboot. I think its fair to say,that most modems do not show config file unless there is some kind of error with it.
	to forum · permalink · · 2007-05-30 08:30:08 · (locked)
Johkal Cool Cat Premium,MVM join:2002-11-13 Happy Valley clubs: ·Comcast Digital Vo.. ·Comcast ·Vonage	Ok, what I am looking for specifically is people who have an SB5101 and have a config file for an "SB5100". These people like myself may see the config file in there log, due to the fact that a software update is pushed & rejected via that config file. Example from my log: 2007-05-30 06:42:02 4-Error E107.0 SW upgrade Failed after download - Incompatible SW file 2007-05-30 06:41:57 6-Notice E102.0 SW Download INIT - Via Config file d11_m_sb5100_silverdeluxe_c01.cm I'll continue to see these errors until I am sent a correct config file for the SB5101. To clarify why my concern; I'm not having connection or speed issues, but I will not be able to receive any needed firmware updates as long as I have a config file for an SB5100. -- Write me up a 125.......I Can't Drive 55 »redrocker.com/ »cabowabo.com/
	to forum · permalink · · 2007-05-30 12:50:47 · (locked)
S0uL join:2002-05-14 Flint, MI	reply to Johkal Flint, mi Config file d11_m_sb5100_silver_c01.cm Software Version: SB5101-2.4.1.6-SCM02-NOSH
	to forum · permalink · · 2007-05-30 12:57:09 · (locked)
Johkal Cool Cat Premium,MVM join:2002-11-13 Happy Valley clubs: ·Comcast Digital Vo.. ·Comcast ·Vonage	said by S0uL : Flint, mi Config file d11_m_sb5100_silver_c01.cm Software Version: SB5101-2.4.1.6-SCM02-NOSH Do you own the modem or is it leased? -- Write me up a 125.......I Can't Drive 55 »redrocker.com/ »cabowabo.com/
	to forum · permalink · · 2007-05-30 13:04:26 · (locked)


Saturday, 05-Dec 14:38:24	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