Greejj's profile

Regular Visitor

 • 

3 Messages

Tue, Dec 1, 2020 8:00 AM

Internet Constantly Disconnects Multiple Times A day

Trying to figure this out. My internet signal keeps dropping out randomly throughout the day. Sometimes it will just be one time I lose internet connection, and then there are other days we lose our connection 4-5 times a day. Then there are times where it will be 2 or 3 days of perfect internet. This has been going on for months and is really starting to get old. Any help would be appreciated. 

 

My modem is an ARRIS - SURFboard 32 x 8 DOCSIS 3.0 Cable Modem and my router is a NETGEAR - Nighthawk AX8 8-Stream AX6000 Wi-Fi 6 Router. I have replaced both of these and talked to both company's customer support. 

 

I am getting these messages when looking at my modem's event log. "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=14:c0:3e:c1:02:49;CMTS-MAC=00:cc:fc:61:31:d0;CM-QOS=1.1;CM-VER=3.0;" & "Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=14:c0:3e:c1:02:49;CMTS-MAC=00:cc:fc:61:31:d0;CM-QOS=1.1;CM-VER=3.0;"

 

Here is my event log:

 

Time Priority Description
Mon Nov 30 12:25:50 20203Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=14:c0:3e:c1:02:49;CMTS-MAC=00:cc:fc:61:31:d0;CM-QOS=1.1;CM-VER=3.0;
Mon Nov 30 12:26:00 20203Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=14:c0:3e:c1:02:49;CMTS-MAC=00:cc:fc:61:31:d0;CM-QOS=1.1;CM-VER=3.0;
Mon Nov 30 12:26:50 20203Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=14:c0:3e:c1:02:49;CMTS-MAC=00:cc:fc:61:31:d0;CM-QOS=1.1;CM-VER=3.0;
Mon Nov 30 12:26:50 20203Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=14:c0:3e:c1:02:49;CMTS-MAC=00:cc:fc:61:31:d0;CM-QOS=1.1;CM-VER=3.0;
Mon Nov 30 12:27:10 20203Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=14:c0:3e:c1:02:49;CMTS-MAC=00:cc:fc:61:31:d0;CM-QOS=1.1;CM-VER=3.0;
Mon Nov 30 12:27:20 20203Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=14:c0:3e:c1:02:49;CMTS-MAC=00:cc:fc:61:31:d0;CM-QOS=1.1;CM-VER=3.0;
Mon Nov 30 12:27:30 20203Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=14:c0:3e:c1:02:49;CMTS-MAC=00:cc:fc:61:31:d0;CM-QOS=1.1;CM-VER=3.0;
Mon Nov 30 12:27:40 20203Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=14:c0:3e:c1:02:49;CMTS-MAC=00:cc:fc:61:31:d0;CM-QOS=1.1;CM-VER=3.0;
Mon Nov 30 12:28:30 20203Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=14:c0:3e:c1:02:49;CMTS-MAC=00:cc:fc:61:31:d0;CM-QOS=1.1;CM-VER=3.0;
Mon Nov 30 12:28:30 20203Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=14:c0:3e:c1:02:49;CMTS-MAC=00:cc:fc:61:31:d0;CM-QOS=1.1;CM-VER=3.0;
Mon Nov 30 12:28:50 20203Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=14:c0:3e:c1:02:49;CMTS-MAC=00:cc:fc:61:31:d0;CM-QOS=1.1;CM-VER=3.0;
Mon Nov 30 12:29:00 20203Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=14:c0:3e:c1:02:49;CMTS-MAC=00:cc:fc:61:31:d0;CM-QOS=1.1;CM-VER=3.0;
Mon Nov 30 12:29:10 20203Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=14:c0:3e:c1:02:49;CMTS-MAC=00:cc:fc:61:31:d0;CM-QOS=1.1;CM-VER=3.0;
Mon Nov 30 12:29:20 20203Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=14:c0:3e:c1:02:49;CMTS-MAC=00:cc:fc:61:31:d0;CM-QOS=1.1;CM-VER=3.0;
Mon Nov 30 12:30:10 20203Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=14:c0:3e:c1:02:49;CMTS-MAC=00:cc:fc:61:31:d0;CM-QOS=1.1;CM-VER=3.0;
Mon Nov 30 12:30:10 20203Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=14:c0:3e:c1:02:49;CMTS-MAC=00:cc:fc:61:31:d0;CM-QOS=1.1;CM-VER=3.0;
Mon Nov 30 12:30:30 20203Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=14:c0:3e:c1:02:49;CMTS-MAC=00:cc:fc:61:31:d0;CM-QOS=1.1;CM-VER=3.0;
Mon Nov 30 12:30:40 20203Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=14:c0:3e:c1:02:49;CMTS-MAC=00:cc:fc:61:31:d0;CM-QOS=1.1;CM-VER=3.0;
Mon Nov 30 12:30:50 20203Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=14:c0:3e:c1:02:49;CMTS-MAC=00:cc:fc:61:31:d0;CM-QOS=1.1;CM-VER=3.0;
Mon Nov 30 12:31:00 20203Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=14:c0:3e:c1:02:49;CMTS-MAC=00:cc:fc:61:31:d0;CM-QOS=1.1;CM-VER=3.0;
 

 

And here is my status list: 

 

 
Startup Procedure
ProcedureStatusComment
Acquire Downstream Channel Locked
Connectivity StateOKOperational
Boot StateOKOperational
Configuration FileOK 
SecurityEnabledBPI+
DOCSIS Network Access EnabledAllowed 

 
Downstream Bonded Channels
ChannelLock StatusModulationChannel IDFrequencyPowerSNRCorrectedUncorrectables
1Locked256QAM17537.00 MHz7.90 dBmV38.98 dB484330431
2Locked256QAM1423.00 MHz7.30 dBmV38.61 dB633733383
3Locked256QAM2435.00 MHz7.20 dBmV38.98 dB567027622
4Locked256QAM3447.00 MHz7.60 dBmV40.37 dB499526063
5Locked256QAM4453.00 MHz7.20 dBmV40.37 dB518028196
6Locked256QAM5459.00 MHz7.30 dBmV40.37 dB531625970
7Locked256QAM6465.00 MHz7.40 dBmV38.98 dB531928307
8Locked256QAM7471.00 MHz7.50 dBmV38.98 dB543727060
9Locked256QAM8477.00 MHz7.60 dBmV38.98 dB602128910
10Locked256QAM9483.00 MHz7.60 dBmV38.61 dB511326835
11Locked256QAM10489.00 MHz7.50 dBmV38.98 dB479129411
12Locked256QAM11495.00 MHz7.70 dBmV38.61 dB617726901
13Locked256QAM12507.00 MHz7.80 dBmV38.61 dB529528277
14Locked256QAM13513.00 MHz7.90 dBmV38.61 dB466829340
15Locked256QAM14519.00 MHz7.60 dBmV38.98 dB498928331
16Locked256QAM15525.00 MHz7.60 dBmV38.61 dB481928075
17Locked256QAM16531.00 MHz8.00 dBmV38.98 dB556728882
18Locked256QAM18543.00 MHz7.60 dBmV38.98 dB502529049
19Locked256QAM19549.00 MHz7.90 dBmV38.61 dB589329843
20Locked256QAM20555.00 MHz7.50 dBmV38.61 dB573327968
21Locked256QAM21561.00 MHz7.00 dBmV38.61 dB449826972
22Locked256QAM22567.00 MHz6.70 dBmV38.61 dB436028084
23Locked256QAM23573.00 MHz6.20 dBmV38.61 dB464730087
24Locked256QAM24579.00 MHz6.30 dBmV38.61 dB461030932
25Locked256QAM25585.00 MHz5.90 dBmV38.60 dB38655
26Locked256QAM26591.00 MHz5.20 dBmV38.20 dB69643
27Locked256QAM27597.00 MHz5.00 dBmV38.20 dB65719
28Locked256QAM28603.00 MHz4.80 dBmV38.20 dB58753
29Locked256QAM29609.00 MHz4.70 dBmV38.20 dB71654
30Locked256QAM30615.00 MHz4.70 dBmV38.20 dB69750
31Locked256QAM31621.00 MHz4.50 dBmV38.20 dB34641
32Locked256QAM32627.00 MHz4.40 dBmV38.20 dB60665

 
>>>Upstream Bonded Channels
ChannelLock StatusUS Channel TypeChannel IDSymbol RateFrequencyPower
1LockedATDMA45120 kSym/s35.70 MHz34.25 dBmV
2LockedATDMA51280 kSym/s41.20 MHz29.75 dBmV
3--------3----29.20 MHz----
4--------2----22.70 MHz----
5--------1----16.20 MHz----

 

Responses

Tymtaker

Frequent Visitor

 • 

16 Messages

6 m ago

Please keep us in the loop! I have a CM1200 modem with the exact same problems. I had 2 techs come out and "check the lines and connections" and both times said everything looks fine, its your modem blah blah blah. I even showed them the error event logs off of the modem with them still saying, no its your modem. So frustrating! 

Regular Visitor

 • 

3 Messages

5 m ago

Just an update. I have a tech coming out to look at our connections tomorrow, January 5th, 2021.

Regular Visitor

 • 

3 Messages

5 m ago

Will do. I just replaced my modem to a ARRIS SURFboard S33 32 x 8 DOCSIS 3.1 Multi-Gig Cable Modem with 2.5 Gbps Ethernet Port after Comcast notified me that my modem "doesn't work with my current plan" but I still have the same issue even with this new modem. 

New to the Community?

Start Here