Search:  

 
 
   All ForumsHot TopicsGallery






how-to block ads


 
Forums » US Cable Support » OptimumOnline » Cable modem disconnects?
Search Topic:
Uniqs:
580
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

badkarma0007

join:2000-05-09
Yonkers, NY

Cable modem disconnects?

Hello All

Without having to get into specific models and such I just wanted to know if anyone else out there experience this issue like me?

Scenario:
My cable modem works fine for hours or maybe even a day and then I loose connectivity to the Net. All the lights start flashing and then nothing else.

Fix:
Pulling out the plug doesn't do anything. I've learned that I have to pull the plug and also disconnect the cable wire. Then I can plug the power back in and while the modem is going through POST, I can then plug in the cable wire.

any ideas of the issue?

THANK YOU IN ADVANCE!!!


Thinkdiff
Premium,MVM
join:2001-08-07
Bronx, NY
What kind of modem?

»192.168.100.1/

What are your signal levels?


jaa
Premium,MVM
join:2000-06-13
New Canaan, CT
·Vonage
·Optimum Online

reply to badkarma0007
If the modem needs to be disconnected from the cable to boot properly, there is something very wrong - either with your cable line or your modem. Is the cable grounded where it comes into the premises?
--
NOTHING justifies terrorism. We don't negotiate with terrorists. Those that support terrorists are terrorists.

badkarma0007

join:2000-05-09
Yonkers, NY

reply to Thinkdiff
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?  


Thursday, 21-Aug 09:35:13 Terms of Use | Privacy Policy | Hosting by www.nac.net - DSL,Hosting & Co-lo | feedback | contact
over 9 years online! © 1999-2008 dslreports.com.
page compression OFF
Most commented news this week
· [99] Was FiOS a Good Idea?
· [77] Landscaping, Courtesy of AT&T?
· [76] ISPs Whine About Network Neutrality 'Paranoia'
· [74] FCC Finally Issues Comcast Throttling Order
· [56] Google Launches White Space Broadband Website
· [56] Craig Moffett: Network Upgrades Are For Ninnies
· [53] Did Apple iPhone Fix Make Problems Worse?
· [52] Qwest, Unions Strike Deal
· [49] Olympics Didn't Cause The Exaflood
· [49] AT&T Cooking Up New VoIP Product
Most people now reading
· [Speed] Comcast to throttle individual users; all protocols [Comcast HSI]
· How do you file things on your computer? [General Questions]
· How I Stole Someone's Identity [Security]
· Criss Angel revealed. [56k lookout! (broadband heavy)]
· release 1.6.0 build 6.86 [Verizon FIOS TV]
· how do I get the washing machine hose off the faucet? [Home Repair & Improvement]
· Anyone know how to capture NBCOlympics.com video streams [General Questions]
· DIR-655 Firmware 1.20 Released [D-Link]
· MA Realignment [Verizon FIOS TV]
· Verizon rolls out first commercial EBIF app [Verizon FIOS TV]