Visitor
•
2 Messages
Internet keeps disconnecting
My internet disconnects randomly throughout the day. It all started when I had an Xfinity supplied modem. I was on the fence about turning my Xfinity modem in and getting my own modem and router, so it seemed like a good time to make the switch. I now have a Motorola MB8611 modem and a TPLink AX11000 WiFi router. The disconnecting is still occurring. It is happening more and more often. I did some diagnostics with my setup. I have done the following:
1. I have removed a signal splitter from the wiring setup (Now the cable coming into my house goes directly into the modem). The coax cable goes directly through the floor, so there are no behind the wall connections.
2. I have shut off and unplugged my WiFi router. (Taking it out of the network setup.)
3. I replaced the ethernet cable I was using with a brand new ethernet cable. (The cable now goes directly from my modem to my computer.)
4. I have gone outside and cut back any branches that could have come in contact on a windy day with the coax cable going from the pole to my house.
5. I have checked all the connections in my set up for tightness and corrosion. (All connections are tight and no corrosion found.)
6. I have checked the coax cable from the Comcast box on the lower part of my house all the way to where it connects to my modem. There are not kinks, cuts, or abrasions in the line.
7. I have talked to my neighbors and none of them have internet disconnect issues. Here is the event log:
Event Log
Critical (3) No Ranging Response received - T3 time-out; CM-QOS=1.1; CM-VER=3.1 Time Not Established
Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing; CM-QOS=1.1; CM-VER=3.1; Time Not Established
Critical (3) No Ranging Response received - T3 time-out; CM-CM-QOS=1.1; CM-VER=3.1; Time Not Established
Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing; CM-QOS=1.1;CM-VER=3.1; Time Not Established
Critical (3) No Ranging Response received - T3 time-out; CM-CM-QOS=1.1; CM-VER=3.1; Time Not Established
Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing; CM-QOS=1.1; CM-VER=3.1; Time Not Established
Critical (3) No Ranging Response received - T3 time-out; CM-QOS=1.1; CM-VER=3.1; Time Not Established
Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing; CM-QOS=1.1;CM-VER=3.1; Time Not Established
Critical (3) No Ranging Response received - T3 time-out; CM-QOS=1.1; CM-VER=3.1; Time Not Established
Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing; CM-QOS=1.1; CM-VER=3.1; Time Not Established
Critical (3) No Ranging Response received - T3 time-out; CM-QOS=1.1; CM-VER=3.1; Time Not Established
Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing; CM-QOS=1.1; CM-VER=3.1; Time Not Established
Critical (3) No Ranging Response received - T3 time-out; CM-QOS=1.1; CM-VER=3.1; Time Not Established
Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing; CM-QOS=1.1;CM-VER=3.1;Time Not Established
Critical (3) No Ranging Response received - T3 time-out; CM-QOS=1.1; CM-VER=3.1; Time Not Established
Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing; CM-QOS=1.1; CM-VER=3.1; Time Not Established
Critical (3) No Ranging Response received - T3 time-out; CM-QOS=1.1; CM-VER=3.1; Time Not Established
Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing; CM-QOS=1.1; CM-VER=3.1; Time Not Established
Critical (3) No Ranging Response received - T3 time-out; CM-QOS=1.1; CM-VER=3.1; Time Not Established
Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out; CM-QOS=1.1; CM-VER=3.1; Time Not Established
Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out; CM-QOS=1.1; CM-VER=3.1; Time Not Established
Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing; CM-QOS=1.1; CM-VER=3.1; Time Not Established
Critical (3) No Ranging Response received - T3 time-out; CM-QOS=1.1; CM-VER=3.1; Time Not Established
Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing; CM-QOS=1.1; CM-VER=3.1; Time Not Established
Critical (3) No Ranging Response received - T3 time-out; CM-QOS=1.1; CM-VER=3.1; Time Not Established
Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing; CM-QOS=1.1; CM-VER=3.1; Time Not Established
Critical (3) No Ranging Response received - T3 time-out; CM-QOS=1.1; CM-VER=3.1; Time Not Established
Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing; CM-QOS=1.1; CM-VER=3.1; 17:27:40 Tue Mar 15 2022
Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out; CM-QOS=1.1; CM-VER=3.1; Time Not Established
Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing; CM-QOS=1.1; CM-VER=3.1; Time Not Established
Notice (6) Honoring MDD; IP provisioning mode = IPv6 18:43:45 Tue Mar 15 2022 Warning (5) REG-RSP-MP Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value; CM-QOS=1.1; CM-VER=3.1;
Here is the connectivity information:
Acquire Downstream Channel 675000000 Hz Locked
Upstream Connection OK Operational
Boot State OK Operational
Configuration File OK
Security Enabled BPI+
Connection Status
System Up Time 0 days 00h:02m:56s
Network Access Allowed
Downstream Bonded Channels
Channel Lock Status Modulation Channel ID Freq. (MHz) Pwr (dBmV) SNR (dB) Corrected Uncorrected
1 Locked QAM256 41 675.0 1.9 39.3 0 0
2 Locked QAM256 13 507.0 0.3 39.8 0 0
3 Locked QAM256 14 513.0 0.5 40.1 0 0
4 Locked QAM256 15 519.0 0.9 40.3 0 0
5 Locked QAM256 16 525.0 1.2 40.5 0 0
6 Locked QAM256 17 531.0 1.6 40.6 0 0
7 Locked QAM256 18 537.0 1.9 40.6 0 0
8 Locked QAM256 19 543.0 2.0 40.6 0 0
9 Locked QAM256 20 549.0 2.4 40.5 0 0
10 Locked QAM256 21 555.0 2.5 40.9 0 0
11 Locked QAM256 22 561.0 2.4 40.7 0 0
12 Locked QAM256 23 567.0 2.3 40.6 0 0
13 Locked QAM256 24 573.0 2.1 40.6 0 0
14 Locked QAM256 25 579.0 1.6 40.3 0 0
15 Locked QAM256 26 585.0 1.7 40.1 0 0
16 Locked QAM256 27 591.0 1.5 40.3 0 0
17 Locked QAM256 28 597.0 1.5 40.2 0 0
18 Locked QAM256 29 603.0 1.7 40.2 0 0
19 Locked QAM256 30 609.0 1.5 40.2 0 0
20 Locked QAM256 31 615.0 1.8 40.3 0 0
21 Locked QAM256 32 621.0 1.7 40.0 0 0
22 Locked QAM256 33 627.0 1.6 39.6 0 0
23 Locked QAM256 34 633.0 1.6 39.3 0 0
24 Locked QAM256 35 639.0 1.6 39.5 0 0
25 Locked QAM256 36 645.0 1.3 39.5 0 0
26 Locked QAM256 37 651.0 1.7 39.6 0 0
27 Locked QAM256 38 657.0 1.6 39.4 0 0
28 Locked QAM256 39 663.0 1.9 39.7 0 0
29 Locked QAM256 40 669.0 2.0 39.6 0 0
30 Locked QAM256 42 681.0 2.1 39.7 0 0
31 Locked QAM256 43 687.0 2.3 39.8 0 0
32 Locked QAM256 44 693.0 2.3 39.5 0 0
33 Locked OFDM PLC 159 702.0 4.3 40.4 0 0
Upstream Bonded Channels
Channel Lock Status Channel Type Channel ID Symb. Rate (Ksym/sec) Freq. (MHz) Pwr (dBmV)
1 Locked SC-QAM 9 2560 10.4 31.8
2 Locked SC-QAM 10 5120 16.4 28.8
3 Locked SC-QAM 11 5120 22.8 27.8
4 Locked SC-QAM 12 5120 29.2 26.8
5 Locked SC-QAM 13 5120 35.6 25.8
6 Locked SC-QAM 14 2560 40.4 23.8
Any suggestions?
XfinityBrie
Administrator
•
671 Messages
3 years ago
Hey there @The13thpaladin, thanks for joining us here in the Xfinity Support Forums. I appreciate you providing all the information posted here--looks like you've done some extensive testing and troubleshooting as it is, so let's dig in based off that.
From what you're describing it sounds like there is connection issues both on Wi-Fi and using an ethernet connection--just to clarify though, is the ethernet connection going into the modem or the router?
Additionally, are the disconnects truly sporadic or are they happening more frequently at certain times?
1
0
XfinityBrie
Administrator
•
671 Messages
3 years ago
@The13thpaladin
Thank you for that additional information--every little bit helps, especially when it comes to these intermittent types of issues. Let's go ahead and take a look at the account and device on the back-end, I can also check to see if there were any issues reported in the area over the last few months. Once we've uncovered more details, we'll circle back here on the thread and provide the resolution in the event anyone else runs into the same issue in the future.
To send a direct message:
Please only send a direct message when requested by an official employee--sending a chat when not requested may result in the chat being lost given the high volume of chat requests received daily.
We ask that you please include your name, the account holder name (if different), and the service address alongside your inquiry so we can best assist.
0
0