republican-creole
Search:  

 
 
   All ForumsHot TopicsGallery






how-to block ads


 
Forums » US Cable Support » OptimumOnline » Cable modem disconnects?
Search Topic:
Share Topic:
RSS topic:
toggle:
flat / full
normal / watch
Posting:
Post a:
Post a:
[OOL] Help! »
« [iO] 4200's really finicky on signal?  
AuthorAll Replies


Thinkdiff
Premium,MVM
join:2001-08-07
Los Angeles, CA
reply to badkarma0007
Re: Cable modem disconnects?

What kind of modem?

»192.168.100.1/

What are your signal levels?

badkarma0007

join:2000-05-09
Yonkers, NY

I have a Surfboard 5100.

Software Version: SB5100-2.3.1.3-SCM00-NOSH
Hardware Version: 1
MIB Version: II
GUI Version: 1.0
VxWorks Version: 5.4

Frequency 603000000 Hz Locked
Signal to Noise Ratio 36 dB
Power Level -13 dB 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 28000000 Hz Ranged

Power Level 51 dBmV

Below is an excerpt from the logs:

Time Priority Code Message
2008-05-06 17:49:20 3-Critical 0x040D9A2C DHCP WARNING - Non-critical field invalid in response.
2008-05-06 17:49:06 3-Critical 0x04E33948 No Ranging Response received - T3 time-out
2008-05-06 17:48:19 3-Critical 0x04E339AC Init RANGING Critical Ranging Request Retries exhausted
2008-05-06 17:48:19 3-Critical 0x04E33948 No Ranging Response received - T3 time-out
2008-05-06 17:46:12 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-05-06 17:46:11 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-05-06 17:46:11 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-05-06 17:46:11 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-05-06 17:46:10 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-05-06 17:46:09 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-05-06 17:46:09 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-05-06 17:46:08 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-05-06 17:46:08 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-05-06 17:46:07 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-05-06 17:46:07 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-05-06 17:46:00 3-Critical 0x04E339AC Init RANGING Critical Ranging Request Retries exhausted
2008-05-06 17:46:00 3-Critical 0x04E33948 No Ranging Response received - T3 time-out
2008-05-06 17:44:19 3-Critical 0x04E339AC Init RANGING Critical Ranging Request Retries exhausted
2008-05-06 17:44:19 3-Critical 0x04E33948 No Ranging Response received - T3 time-out
2008-05-06 17:42:46 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-05-06 17:42:45 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-05-06 17:42:45 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-05-06 17:42:34 3-Critical 0x04E339AC Init RANGING Critical Ranging Request Retries exhausted
2008-05-06 17:42:34 3-Critical 0x04E33948 No Ranging Response received - T3 time-out
2008-05-06 17:40:14 3-Critical 0x04E339AC Init RANGING Critical Ranging Request Retries exhausted
2008-05-06 17:40:14 3-Critical 0x04E33948 No Ranging Response received - T3 time-out
2008-05-06 17:38:00 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-05-06 17:37:59 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-05-06 17:37:59 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-05-06 17:37:48 3-Critical 0x04E339AC Init RANGING Critical Ranging Request Retries exhausted
2008-05-06 17:37:48 3-Critical 0x04E33948 No Ranging Response received - T3 time-out
2008-05-06 17:35:01 3-Critical 0x04E339AC Init RANGING Critical Ranging Request Retries exhausted
2008-05-06 17:35:01 3-Critical 0x04E33948 No Ranging Response received - T3 time-out
2008-05-06 17:33:19 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-05-06 17:33:10 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-05-06 17:33:10 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-05-06 17:33:05 3-Critical 0x04E339AC Init RANGING Critical Ranging Request Retries exhausted
2008-05-06 17:33:05 3-Critical 0x04E33948 No Ranging Response received - T3 time-out
2008-05-06 17:31:03 3-Critical 0x04E339AC Init RANGING Critical Ranging Request Retries exhausted
2008-05-06 17:31:03 3-Critical 0x04E33948 No Ranging Response received - T3 time-out
2008-05-06 17:29:03 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-05-06 17:29:02 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-05-06 17:29:02 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-05-06 17:29:00 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-05-06 17:28:59 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-05-06 17:28:59 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-05-06 17:28:59 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-05-06 17:28:58 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-05-06 17:28:57 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-05-06 17:28:57 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-05-06 17:28:56 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-05-06 17:28:56 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-05-06 17:28:56 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-05-06 17:28:40 3-Critical 0x04E339AC Init RANGING Critical Ranging Request Retries exhausted
2008-05-06 17:28:40 3-Critical 0x04E33948 No Ranging Response received - T3 time-out
2008-05-06 17:28:10 3-Critical 0x04E339AC Init RANGING Critical Ranging Request Retries exhausted
2008-05-06 17:28:10 3-Critical 0x04E33948 No Ranging Response received - T3 time-out
2008-05-06 17:27:34 3-Critical 0x04E339AC Init RANGING Critical Ranging Request Retries exhausted
2008-05-06 17:27:34 3-Critical 0x04E33948 No Ranging Response received - T3 time-out
2008-05-06 17:26:58 3-Critical 0x04E339AC Init RANGING Critical Ranging Request Retries exhausted
2008-05-06 17:26:58 3-Critical 0x04E33948 No Ranging Response received - T3 time-out
2008-05-06 17:26:10 3-Critical 0x04E339AC Init RANGING Critical Ranging Request Retries exhausted
2008-05-06 17:26:10 3-Critical 0x04E33948 No Ranging Response received - T3 time-out
2008-05-06 17:25:35 3-Critical 0x04E339AC Init RANGING Critical Ranging Request Retries exhausted
2008-05-06 17:25:35 3-Critical 0x04E33948 No Ranging Response received - T3 time-out
2008-05-06 17:24:50 3-Critical 0x04E339AC Init RANGING Critical Ranging Request Retries exhausted
2008-05-06 17:24:50 3-Critical 0x04E33948 No Ranging Response received - T3 time-out
2008-05-06 17:24:09 3-Critical 0x04E339AC Init RANGING Critical Ranging Request Retries exhausted
2008-05-06 17:24:09 3-Critical 0x04E33948 No Ranging Response received - T3 time-out
2008-05-06 17:23:28 3-Critical 0x04E339AC Init RANGING Critical Ranging Request Retries exhausted
2008-05-06 17:23:28 3-Critical 0x04E33948 No Ranging Response received - T3 time-out
2008-05-06 17:21:45 3-Critical 0x04E339AC Init RANGING Critical Ranging Request Retries exhausted
2008-05-06 17:21:45 3-Critical 0x04E33948 No Ranging Response received - T3 time-out
2008-05-06 17:20:03 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-05-06 17:20:01 3-Critical 0x04E339AC Init RANGING Critical Ranging Request Retries exhausted
2008-05-06 17:20:01 3-Critical 0x04E33948 No Ranging Response received - T3 time-out
2008-05-06 17:17:54 3-Critical 0x04E339AC Init RANGING Critical Ranging Request Retries exhausted
2008-05-06 17:17:54 3-Critical 0x04E33948 No Ranging Response received - T3 time-out
2008-05-06 17:15:48 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-05-06 17:15:34 3-Critical 0x04E339AC Init RANGING Critical Ranging Request Retries exhausted
2008-05-06 17:15:34 3-Critical 0x04E33948 No Ranging Response received - T3 time-out
2008-05-06 17:12:50 3-Critical 0x04E339AC Init RANGING Critical Ranging Request Retries exhausted
2008-05-06 17:12:50 3-Critical 0x04E33948 No Ranging Response received - T3 time-out
2008-05-06 17:09:54 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-05-06 17:09:53 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-05-06 17:09:53 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-05-06 17:09:43 3-Critical 0x04E339AC Init RANGING Critical Ranging Request Retries exhausted
2008-05-06 17:09:43 3-Critical 0x04E33948 No Ranging Response received - T3 time-out
2008-05-06 17:07:09 3-Critical 0x04E339AC Init RANGING Critical Ranging Request Retries exhausted
2008-05-06 17:07:09 3-Critical 0x04E33948 No Ranging Response received - T3 time-out
2008-05-06 17:04:06 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-05-06 17:04:01 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-05-06 17:04:01 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-05-06 17:03:59 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-05-06 17:03:59 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-05-06 17:03:56 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-05-06 17:03:55 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-05-06 17:03:54 3-Critical 0x04E339AC Init RANGING Critical Ranging Request Retries exhausted
2008-05-06 17:03:54 3-Critical 0x04E33948 No Ranging Response received - T3 time-out
2008-05-06 17:00:30 3-Critical 0x04E339AC Init RANGING Critical Ranging Request Retries exhausted

daveinpoway

join:2006-07-03
Poway, CA

Your downstream power is quite low and the upstream power is somewhat high; it is possible they could fluctuate further during the day. Make sure there is no more than one splitter between where the cable enters the house and the modem's input. Also, make sure all of the connections are tight. If you've done this, and the levels are still marginal, it's time for a tech to come out.
-
Forums » US Cable Support » OptimumOnline[OOL] Help! »
« [iO] 4200's really finicky on signal?  


Saturday, 30-Aug 05:19:34 Terms of Use | Privacy Policy | Hosting by www.nac.net - DSL,Hosting & Co-lo | feedback | contact
over 9 years online! © 1999-2008 dslreports.com.republican-creole
page compression OFF
Most commented news this week
· [332] Comcast 250GB Cap Goes Live October 1
· [223] FBI To Allow Warrantless Investigations
· [156] Industry Reacts To Comcast Cap Plans
· [130] AT&T Thanks Democrats For Telecom Immunity
· [123] Time Warner Cable Cripples TiVO, Gets FCC Fine
· [120] Why Run FTTH When You Can Pretend You Do?
· [72] Friday Open Thread
· [67] Telus CAPS 'Unlimited' EVDO Data Plans
· [65] Game Publishers Follow The RIAA's Lead
· [60] Qwest Defends Not Running FTTH
Most people now reading
· Comcast has new Acceptable Use Policy besides the 250GB cap [Comcast HSI]
· Bandwidth Monitor for Computers-Suggestions? [Comcast HSI]
· Antivirus XP 08 [Security]
· Hurricane Gustav [Weather]
· Battlegrounds Auto-queue, Auto-Join Add-ons [World of Warcraft]
· Xp Stuck in LOOP [Microsoft help]
· [northeast] Might be torrent throttling, might not be? Help! [Verizon Fiber Optics]
· [General] DLink VTA-VR [VOIP Tech Chat]
· I got a copy of someone's drivers license from ... [Rants, Raves, & Praise]