Visitor
•
4 Messages
Motorola MB8611 keeps losing connection and rebooting throughout the day
My modem keeps rebooting throughout the day. I have had 4 different modems and modem/routers in the last 3 years and this continuously keeps happening regardless of what I try. I have rebooted it dozens of times, replaced almost every cable connecting to my system (excluding the ones running through the walls), and changed out various splitters. Normally this wouldn't bother me but I recently started working from home so a stable internet connection is crucial for my work.
Below are the latest Error Logs, Downstream, and Upstream Channels from about 30 minutes before posting this:
Time |
Priority |
Description |
16:18:07 |
Critical (3) |
SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-VER=3.1; |
16:18:07 |
Critical (3) |
Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-VER=3.1; |
16:18:50 |
Critical (3) |
SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-VER=3.1; |
16:18:50 |
Critical (3) |
Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-VER=3.1; |
16:18:51 |
Critical (3) |
SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-VER=3.1; |
16:18:51 |
Critical (3) |
Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-VER=3.1; |
16:19:18 |
Critical (3) |
SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-VER=3.1; |
16:19:18 |
Critical (3) |
Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-VER=3.1; |
16:19:33 |
Critical (3) |
SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-VER=3.1; |
16:19:34 |
Critical (3) |
Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-VER=3.1; |
16:20:18 |
Critical (3) |
SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-VER=3.1; |
16:20:18 |
Critical (3) |
Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-VER=3.1; |
Time Not Established |
Critical (3) |
SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-VER=3.1; |
16:26:30 |
Critical (3) |
Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-VER=3.1; |
16:26:30 |
Critical (3) |
TFTP Failed - OUT OF ORDER packets;CM-VER=3.1; |
16:26:30 |
Critical (3) |
TFTP Request Retries exceeded, CM unable to register |
16:26:44 |
Critical (3) |
No Ranging Response received - T3 time-out;CM-VER=3.1; |
Time Not Established |
Critical (3) |
SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-VER=3.1; |
Time Not Established |
Critical (3) |
No Ranging Response received - T3 time-out;CM-VER=3.1; |
Time Not Established |
Critical (3) |
SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-VER=3.1; |
Time Not Established |
Critical (3) |
No Ranging Response received - T3 time-out;CM-VER=3.1; |
Time Not Established |
Critical (3) |
SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-VER=3.1; |
Time Not Established |
Critical (3) |
No Ranging Response received - T3 time-out;CM-VER=3.1; |
Time Not Established |
Critical (3) |
SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-VER=3.1; |
Time Not Established |
Critical (3) |
No Ranging Response received - T3 time-out;CM-VER=3.1; |
10:19:44 |
Critical (3) |
Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-VER=3.1; |
Time Not Established |
Critical (3) |
SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-VER=3.1; |
Time Not Established |
Critical (3) |
No Ranging Response received - T3 time-out;CM-VER=3.1; |
Time Not Established |
Critical (3) |
SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-VER=3.1; |
Time Not Established |
Critical (3) |
No Ranging Response received - T3 time-out;CM-VER=3.1; |
Time Not Established |
Notice (6) |
Honoring MDD; IP provisioning mode = IPv6 |
11:10:51 |
Notice (6) |
DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-VER=3.1; |
Channel |
Lock Status |
Modulation |
Channel ID |
Freq. (MHz) |
Pwr (dBmV) |
SNR (dB) |
Corrected |
Uncorrected |
1 |
Locked |
QAM256 |
20 |
603.0 |
-6.4 |
37.2 |
0 |
0 |
2 |
Locked |
QAM256 |
17 |
585.0 |
-5.4 |
37.7 |
0 |
0 |
3 |
Locked |
QAM256 |
18 |
591.0 |
-5.7 |
37.8 |
0 |
0 |
4 |
Locked |
QAM256 |
19 |
597.0 |
-5.8 |
37.7 |
0 |
0 |
5 |
Locked |
QAM256 |
21 |
609.0 |
-6.7 |
37.0 |
0 |
0 |
6 |
Locked |
QAM256 |
22 |
615.0 |
-6.8 |
37.0 |
0 |
0 |
7 |
Locked |
QAM256 |
23 |
621.0 |
-6.3 |
37.4 |
0 |
0 |
8 |
Locked |
QAM256 |
24 |
627.0 |
-5.8 |
37.7 |
0 |
0 |
9 |
Locked |
QAM256 |
25 |
633.0 |
-6.0 |
37.8 |
0 |
0 |
10 |
Locked |
QAM256 |
26 |
639.0 |
-6.4 |
37.5 |
0 |
0 |
11 |
Locked |
QAM256 |
27 |
645.0 |
-6.6 |
37.2 |
0 |
0 |
12 |
Locked |
QAM256 |
28 |
651.0 |
-7.1 |
37.0 |
0 |
0 |
13 |
Locked |
QAM256 |
29 |
657.0 |
-6.4 |
37.2 |
0 |
0 |
14 |
Locked |
QAM256 |
30 |
663.0 |
-6.0 |
37.5 |
0 |
0 |
15 |
Locked |
QAM256 |
31 |
669.0 |
-5.6 |
37.9 |
0 |
0 |
16 |
Locked |
QAM256 |
32 |
675.0 |
-5.7 |
37.2 |
0 |
0 |
17 |
Locked |
QAM256 |
33 |
681.0 |
-5.6 |
37.7 |
0 |
0 |
18 |
Locked |
QAM256 |
34 |
687.0 |
-5.6 |
37.5 |
0 |
0 |
19 |
Locked |
QAM256 |
35 |
693.0 |
-5.7 |
37.4 |
0 |
0 |
20 |
Locked |
QAM256 |
36 |
699.0 |
-5.4 |
37.5 |
0 |
0 |
21 |
Locked |
QAM256 |
37 |
705.0 |
-5.0 |
38.0 |
0 |
0 |
22 |
Locked |
QAM256 |
38 |
711.0 |
-5.1 |
38.3 |
0 |
0 |
23 |
Locked |
QAM256 |
39 |
717.0 |
-5.2 |
38.0 |
0 |
0 |
24 |
Locked |
QAM256 |
40 |
723.0 |
-6.0 |
37.6 |
0 |
0 |
25 |
Locked |
QAM256 |
41 |
729.0 |
-5.9 |
37.5 |
0 |
0 |
26 |
Locked |
QAM256 |
42 |
735.0 |
-5.7 |
37.7 |
0 |
0 |
27 |
Locked |
QAM256 |
43 |
741.0 |
-5.8 |
37.8 |
0 |
0 |
28 |
Locked |
QAM256 |
44 |
747.0 |
-5.3 |
38.2 |
0 |
0 |
29 |
Locked |
QAM256 |
45 |
753.0 |
-5.0 |
38.5 |
0 |
0 |
30 |
Locked |
QAM256 |
46 |
759.0 |
-5.2 |
38.3 |
0 |
0 |
31 |
Locked |
QAM256 |
47 |
765.0 |
-5.9 |
38.0 |
0 |
0 |
32 |
Locked |
OFDM PLC |
48 |
805.0 |
-3.7 |
38.4 |
10003812 |
0 |
Channel |
Lock Status |
Channel Type |
Channel ID |
Symb. Rate (Ksym/sec) |
Freq. (MHz) |
Pwr (dBmV) |
1 |
Locked |
SC-QAM |
1 |
2560 |
10.4 |
48.3 |
2 |
Locked |
SC-QAM |
2 |
5120 |
16.4 |
49.0 |
3 |
Locked |
SC-QAM |
3 |
5120 |
22.8 |
49.5 |
4 |
Locked |
SC-QAM |
4 |
5120 |
29.2 |
49.8 |
5 |
Locked |
SC-QAM |
5 |
5120 |
35.6 |
49.8 |
6 |
Locked |
SC-QAM |
6 |
2560 |
40.4 |
50.3 |
EG
Expert
•
95K Messages
1分前
Both the downstream and the upstream power levels are marginal and they may be intermittently fluctuating even farther to out of spec levels. That can cause random disconnects, spontaneous re-booting of the modem, speed, packet loss, latency problems, and the un-bonding of channels.
In an effort to try to obtain better connectivity / more wiggle room, check to see if there are there any excess/unneeded coax cable splitters in the line leading to the modem that can be eliminated/re-configured. Any splitters that remain should be high quality and cable rated for 5-1000 MHz, bi-directional, and no gold colored garbage from Radio Shack, Home Depot, Target, etc. Splitters should be swapped with known to be good / new ones to test.
Also check the coax cable for any damage such as cuts, nicks, kinks, sharp bends, etc.
If there aren't any unneeded splitters that can be eliminated and if your coax wiring setup can't be reconfigured so that there is a single two-way splitter connected directly off of the drop from the street / pole with one port feeding the modem and the other port feeding the rest of the house/equipment with additional splits as needed and you've checked all the wiring and fittings for integrity and tightness and refresh them by taking them apart then check for and clean off any corrosion / oxidation on the center wire and put them back together again, then perhaps it's best to book a tech visit to investigate and correct.
Good luck with it !
1
EG
Expert
•
95K Messages
1分前
So what do the signal stat figures look like now ?
1
0
EG
Expert
•
95K Messages
1分前
It's still N/G. If there is nothing more that can be done to improve the connection quality, then you'll need a tech visit as stated.
Bear in mind that if the premises facing techs can not find or fix a problem at your home, it is they who are responsible for escalating it to their line / network / maintenance dept. techs. The problem may lie beyond your home in the local neighborhood infrastructure somewhere but it is their S.O.P. to start at the home. And if the problem is found to be on their side of the demarcation point, there will not be any charge.
Good luck !
3