Search:  

 
 
   All ForumsHot TopicsGallery






how-to block ads


 
Forums » US Cable Support » Cable users » Problem with Motorola SB5101 often dropping out
Search Topic:
Uniqs:
305
Share Topic:
RSS topic:
toggle:
flat / full
normal / watch
Posting:
Post a:
Post a:
RG59 from street to RG6 in the house »
« A quick technical question  
AuthorAll Replies


SLL

@stofanet.dk

Problem with Motorola SB5101 often dropping out

Hey,

I new here, but wanted to hear you guys about a drop out problem if have, where the modem looses connection for about 10-20 seconds, and then automatically connects again. sometimes all LEDs (except power) starts to flash one by one top/down, and then eventually connection works again. Other times, connections just drops with all LEDs on?

I'm not 100% sure, but I think the problems are worse in winter times, and better when its warmer.

I can also see, that my upstream channel Id and freq. are zero when dropout is happning, like this:

Channel ID 0
Frequency 0

So it could be a problem in the upstream path, somewhere.

Here is the normal values:
Downstream:
Frequency 143000000 Hz
Signal To Noise Ratio 41.8 dB
Power Level 1.7 dBmV

Upstream:
Channel ID 4
Frequency 14800000 Hz
Power 47.5 dBmV

I've had these problems for more years now, and they irritates my as hell. My ISP has done anything they could to try to solve these drop out problems, but nothing seems to work.

ISP have tried:
- changing filters, changing connectors, I'm on my 4th modem, measured signals, dragged a direct wire connection from the splitter box outside, and into my cable modem, monitored signal.... and the list goes on.....

And they still haven't found the problem. I'm starting to thing, that the whole general cable path is too old and probably introducing all kinds of bad things for a steady connection. But I don't think I can get my ISP på admit that, since they want my money for the Internet connection

Here is the log, right after a short dropout:

2008-06-04 21:16:14 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
1970-01-01 00:00:14 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
2008-06-04 20:31:21 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
2008-06-04 17:50:49 5-Warning D103.0 DHCP RENEW WARNING - Field invalid in response
2008-06-04 17:40:29 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
1970-01-01 00:00:17 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
1970-01-01 00:00:08 3-Critical R002.0 No Ranging Response received - T3 time-out
2008-06-04 13:50:22 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o
2008-06-04 11:16:33 5-Warning D103.0 DHCP RENEW WARNING - Field invalid in response
1970-01-01 00:00:12 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
2008-06-03 17:58:46 5-Warning D103.0 DHCP RENEW WARNING - Field invalid in response
2008-06-03 17:15:44 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
1970-01-01 00:00:18 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
2008-06-02 19:40:04 5-Warning D103.0 DHCP RENEW WARNING - Field invalid in response
1970-01-01 00:00:16 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
2008-05-31 20:06:28 5-Warning D103.0 DHCP RENEW WARNING - Field invalid in response
1970-01-01 00:00:14 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
2008-05-29 17:32:40 5-Warning D103.0 DHCP RENEW WARNING - Field invalid in response
1970-01-01 00:00:14 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
2008-05-28 18:49:14 5-Warning D103.0 DHCP RENEW WARNING - Field invalid in response
2008-05-28 16:35:06 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
1970-01-01 00:00:14 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
2008-05-28 02:41:29 5-Warning D103.0 DHCP RENEW WARNING - Field invalid in response
2008-05-28 00:16:22 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
2008-05-27 22:41:29 5-Warning D103.0 DHCP RENEW WARNING - Field invalid in response
2008-05-27 18:14:43 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
2008-05-27 14:41:29 5-Warning D103.0 DHCP RENEW WARNING - Field invalid in response
1970-01-01 00:00:12 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
2008-05-25 20:36:27 5-Warning D103.0 DHCP RENEW WARNING - Field invalid in response
1970-01-01 00:00:16 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
2008-05-24 19:35:24 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
2008-05-24 18:10:16 5-Warning D103.0 DHCP RENEW WARNING - Field invalid in response
1970-01-01 00:00:13 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
2008-05-23 15:26:43 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
2008-05-23 12:49:28 5-Warning D103.0 DHCP RENEW WARNING - Field invalid in response
2008-05-22 21:38:46 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
2008-05-22 20:49:28 5-Warning D103.0 DHCP RENEW WARNING - Field invalid in response
1970-01-01 00:00:14 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
2008-05-18 21:12:46 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
2008-05-18 21:05:26 5-Warning D103.0 DHCP RENEW WARNING - Field invalid in response
2008-05-18 19:21:36 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
2008-05-18 17:05:26 5-Warning D103.0 DHCP RENEW WARNING - Field invalid in response
1970-01-01 00:00:16 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
2008-05-16 20:16:41 5-Warning D103.0 DHCP RENEW WARNING - Field invalid in response
2008-05-16 13:06:49 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
1970-01-01 00:00:14 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
1970-01-01 00:00:26 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:00:19 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:00:19 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:00:18 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:00:18 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:00:17 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:00:16 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:00:15 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:00:14 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:00:13 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:00:12 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:00:10 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:00:08 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:00:07 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:00:06 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:00:04 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:00:20 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
2008-05-12 20:10:39 5-Warning D103.0 DHCP RENEW WARNING - Field invalid in response
1970-01-01 00:00:15 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
1970-01-01 00:08:07 3-Critical D001.0 DHCP FAILED - Discover sent, no offer received
1970-01-01 00:07:35 3-Critical R002.0 No Ranging Response received - T3 time-out
1970-01-01 00:07:28 3-Critical D001.0 DHCP FAILED - Discover sent, no offer received
1970-01-01 00:04:15 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:04:11 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:04:11 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:04:08 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:04:07 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:04:06 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:04:06 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:04:03 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:04:03 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:04:00 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:04:00 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:03:59 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:03:55 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:03:55 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:03:51 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:03:50 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:03:47 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:03:15 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:03:09 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:03:08 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:03:05 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:03:04 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:03:01 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:03:00 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:02:56 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:02:55 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:02:52 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:02:20 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:02:15 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:02:13 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:02:11 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:02:10 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing

--------------------------------

Is there any of you out there, that can translate this log into something understandable? Is there something in there, that looks bad?

All the best,
SLL

joos

join:2008-06-26
Taunton, MA
unfortunantly you probably don't own a dsam meter but it sounds like you have some poor BER(bit error rates) contact your local cable company and have the tech run a docsis scan on it.
-
Forums » US Cable Support » Cable usersRG59 from street to RG6 in the house »
« A quick technical question  


Wednesday, 20-Aug 21:05: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.republican-creole
page compression OFF
Most commented news this week
· [93] Was FiOS a Good Idea?
· [77] Landscaping, Courtesy of AT&T?
· [71] ISPs Whine About Network Neutrality 'Paranoia'
· [64] FCC Finally Issues Comcast Throttling Order
· [56] Google Launches White Space Broadband Website
· [53] Craig Moffett: Network Upgrades Are For Ninnies
· [52] Qwest, Unions Strike Deal
· [49] Olympics Didn't Cause The Exaflood
· [49] AT&T Cooking Up New VoIP Product
· [44] First Android Phone Gets FCC Approval
Most people now reading
· Neighbor Yanks a Power Line & Voltage Overloads the Block [Home Repair & Improvement]
· [Connectivity] Sandvine kills more than just P2P [Comcast HSI]
· Anyone know how to capture NBCOlympics.com video streams [General Questions]
· VoIP and the 911 dilemma [VOIP Tech Chat]
· WPA TKIP or AES? [Wireless Security]
· How I Stole Someone's Identity [Security]
· [iPhone] 2.0.2 firmware is out, Please post outcome [All things Macintosh]
· How-to: make ActionTec MI424-WR a network bridge [Verizon Fiber Optics]
· [Speed] Comcast to throttle individual users; all protocols [Comcast HSI]