U

Visitor

 • 

4 Messages

Tuesday, February 7th, 2023 10:08 PM

Closed

Outdoor Exposed Cable and Random Short Internet Connection Drops

I have 2 issues. Please let me know if 2 separate forum entries need to be submitted.

Issue 1: In April 2020, Xfinity installed a new cable line from the road to the box on the side of my house. The cable has since become exposed above ground in 3 areas of my gravel driveway (fairly close to each other). This cable needs to be properly buried. Please let me know how to proceed to have this done.

Issue 2: One computer is connected to the modem with an Ethernet cable and one laptop uses WiFi. We were experiencing random internet outages (5-25 minutes in length) while using a Motorola MG7550 router/modem (both wired and wireless). It happened about once a week, then started happening every 2-3 days. The router/modem would have to be rebooted 2-3 times in a row before we would have internet service again. This device was almost 3 years old, so we replaced it with a new MG8702 router/modem on 1/10/23.

With the new router, we started randomly losing connection for very brief moments, at least once a day (both wired and wireless, day and night). The internet drop is so short that it doesn't even show up on the taskbar as a lost connection and seems to automatically resolve itself (we don't have to reboot the router/modem). The router/modem does not reset/recycle. When the internet drops for that brief moment, we get disconnected from online games.

Rebooting the router/modem did not prevent the drops from happening again (usually happens once or twice a day). The drop is so brief that the modem does not reboot itself. We have to log back in to our online games.

We do not have a cable tv account. Only one cable line is used for the router/modem. Alexa (WiFi) and our WiFi driveway alarm are not affected by the brief drops. They were affected with the old modem, because we were losing internet connection for longer periods of time.

There are no loose cables.

The cable line from the box going into the house was not replaced when the cable was installed in 2020. The cable goes from the box (which is locked with a zip tie by Xfinity) located on the outside of the house, under the house eaves, and through a hole in the wall of the house (there is no outlet on the wall). That cable goes directly into the router/modem from the locked box on the outside of the house.

Below this message are my downstream, upstream, and event log reports for the new MG8702 router/modem in use. According to the connection status, the device has not been rebooted in 23 days. Please let me know if you want to see the reports right after a reboot. Thanks!

   Downstream Bonded Channels  
  
   Channel Lock Status Modulation Channel ID Freq. (MHz) Pwr (dBmV) SNR (dB) Corrected Uncorrected
   1 Locked QAM256 44 681.0 -0.1 41.5 676 465
   2 Locked QAM256 13 489.0 0.8 43.1 34 0
   3 Locked QAM256 14 495.0 0.6 42.9 33 0
   4 Locked QAM256 15 501.0 0.5 42.9 63 0
   5 Locked QAM256 16 507.0 0.3 42.6 59 0
   6 Locked QAM256 17 513.0 0.4 42.7 41 0
   7 Locked QAM256 18 519.0 0.3 42.5 29 0
   8 Locked QAM256 19 525.0 0.3 42.7 18 0
   9 Locked QAM256 20 531.0 0.2 42.5 20 0
   10 Locked QAM256 21 537.0 0.3 42.4 21 0
   11 Locked QAM256 22 543.0 0.3 42.5 14 0
   12 Locked QAM256 23 555.0 0.5 42.5 11 0
   13 Locked QAM256 24 561.0 0.7 42.7 14 0
   14 Locked QAM256 25 567.0 0.5 42.6 10 0
   15 Locked QAM256 26 573.0 0.6 42.6 8 0
   16 Locked QAM256 27 579.0 0.5 42.5 11 0
   17 Locked QAM256 28 585.0 0.5 42.3 11 0
   18 Locked QAM256 29 591.0 0.4 42.3 17 0
   19 Locked QAM256 30 597.0 0.6 42.2 17 0
   20 Locked QAM256 31 603.0 0.5 42.2 28 0
   21 Locked QAM256 32 609.0 0.5 42.2 65 0
   22 Locked QAM256 33 615.0 0.6 42.2 125 0
   23 Locked QAM256 34 621.0 0.9 41.9 123 0
   24 Locked QAM256 35 627.0 0.7 42.1 166 29
   25 Locked QAM256 36 633.0 0.6 42.1 165 81
   26 Locked QAM256 37 639.0 0.5 42.0 2131 2137
   27 Locked QAM256 38 645.0 0.3 41.9 141 160
   28 Locked QAM256 39 651.0 0.3 41.8 138 50
   29 Locked QAM256 40 657.0 0.2 41.6 163 0
   30 Locked QAM256 41 663.0 -0.2 41.4 31 0
   31 Locked QAM256 42 669.0 -0.1 41.6 481 466
   32 Locked QAM256 43 675.0 0.1 40.6 661 689
   33 Locked OFDM PLC 193 805.0 0.5 41.2 -1424909778 157


   Upstream Bonded Channels  
  
   Channel Lock Status Channel Type Channel ID Symb. Rate (Ksym/sec) Freq. (MHz) Pwr (dBmV)
   1 Locked SC-QAM 1 5120 16.4 49.8
   2 Locked SC-QAM 2 5120 22.8 48.3
   3 Locked SC-QAM 3 5120 29.2 47.3
   4 Locked SC-QAM 4 5120 35.6 47.0
   5 Locked SC-QAM 5 2560 40.4 47.3
   6 Locked SC-QAM 6 2560 10.4 50.0

Event Log
   Log  
  
    Time    Priority    Description 
    17:16:14
Mon Jan 30 2023
  Warning (5)   RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
    17:16:14
Mon Jan 30 2023
  Warning (5)   Dynamic Range Window violation
    14:06:50
Tue Jan 31 2023
  Warning (5)   RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
    14:06:50
Tue Jan 31 2023
  Warning (5)   Dynamic Range Window violation
    16:19:05
Wed Feb 1 2023
  Warning (5)   RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
    16:19:05
Wed Feb 1 2023
  Warning (5)   Dynamic Range Window violation
    13:51:34
Thu Feb 2 2023
  Warning (5)   RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
    13:51:34
Thu Feb 2 2023
  Warning (5)   Dynamic Range Window violation
    17:41:05
Thu Feb 2 2023
  Warning (5)   RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
    17:41:05
Thu Feb 2 2023
  Warning (5)   Dynamic Range Window violation
    10:32:09
Fri Feb 3 2023
  Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
    15:37:24
Fri Feb 3 2023
  Warning (5)   RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
    15:37:24
Fri Feb 3 2023
  Warning (5)   Dynamic Range Window violation
    19:40:32
Fri Feb 3 2023
  Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
    20:34:02
Fri Feb 3 2023
  Critical (3)   SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
    20:34:06
Fri Feb 3 2023
  Critical (3)   No Ranging Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
    00:17:08
Sat Feb 4 2023
  Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
    01:33:46
Sat Feb 4 2023
  Warning (5)   RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
    01:33:46
Sat Feb 4 2023
  Warning (5)   Dynamic Range Window violation
    01:33:46
Sat Feb 4 2023
  Warning (5)   RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
    01:33:46
Sat Feb 4 2023
  Warning (5)   Dynamic Range Window violation
    13:40:11
Sat Feb 4 2023
  Warning (5)   RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
    13:40:11
Sat Feb 4 2023
  Warning (5)   Dynamic Range Window violation
    15:19:59
Sat Feb 4 2023
  Warning (5)   RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
    15:19:59
Sat Feb 4 2023
  Warning (5)   Dynamic Range Window violation
    18:13:24
Sat Feb 4 2023
  Warning (5)   RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
    18:13:24
Sat Feb 4 2023
  Warning (5)   Dynamic Range Window violation
    10:22:21
Sun Feb 5 2023
  Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
    17:21:13
Sun Feb 5 2023
  Warning (5)   RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
    17:21:13
Sun Feb 5 2023
  Warning (5)   Dynamic Range Window violation
    15:35:59
Mon Feb 6 2023
  Warning (5)   RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
    15:35:59
Mon Feb 6 2023
  Warning (5)   Dynamic Range Window violation

Problem Solver

 • 

311 Messages

2 years ago

Hello @user_d2450f thank you for reaching out to our team regarding your concerns, which include the cable lines being exposed, and intermittent, these issues can be addressed here.

 

Can you please send our team a direct message [private message]:

   Click "Sign In" if necessary
   Click the "Direct Message" icon or https://forums.xfinity.com/direct-messaging
   Click the "New message" (pencil and paper) icon
   The "To:" line prompts you to "Type the name of a person". Instead, type "Xfinity Support" there.
   - As you are typing a drop-down list appears. Select "Xfinity Support" from that list.
   - An "Xfinity Support" graphic replaces the "To:" line.
   Type your message in the text area near the bottom of the window
   Press Enter to send it

 

 

 

 

 

 

Visitor

 • 

4 Messages

@XfinityFelicia​ Thank you for the response.  I followed your instructions and direct messaged Xfinity Support.  Thanks!

Visitor

 • 

2 Messages

2 years ago

Checking in to see if you happened to get resolution to your issue and if so what it took to resolve

Visitor

 • 

4 Messages

@user_ekosch​   Xfinity Support has been very responsive. A technician was sent out the next day. However, before the tech had shown up, I had received an automated phone call telling me that the problem had been found and fixed.  I was then given the option to keep my appointment with the tech or cancel it.  Sorry, I don't remember the exact words of the message, because I had been asleep when they had called at 7:30 am.  Since I had no way of knowing if the issue had been resolved, I kept the appointment. The technician checked the lines and couldn't find any issues.  He tightened something at the roadside pole, but didn't think it would have been the cause of random internet drops.  I told the tech about the earlier phone call.  He told me they could have cleared the problem at the node (not located on my property).  A few days went by without any internet drops, then we started experiencing them again, though not nearly as often.  Instead of every day, it was every other day or 2 days could go by before the next one.  This entire time, Xfinity Support had been communicating with me via direct messaging.  They confirmed that one of the drops had been an actual area outage (a short one), so that wasn't just me.  I still have open communications with Xfinity Support, in case we want to start renting their modem.  This would allow them to be able to do more in-depth troubleshooting.  So, I honestly don't know if the internet problem has been resolved.  It isn't happening as often and I haven't been disconnected from the online game that I play (that's the only way I had known when there was a problem).  My son has been disconnected from online games, but he thinks it might be the fault of the games (especially since I don't get disconnected).  In the past, we had both been disconnected (wired and WiFi).  Right now, we are monitoring things.  If the internet drops start happening more frequently or disrupt our gaming, I will probably try the Xfinity modem to see if the problem persists or goes away.  There are still some warnings on the event log (not as often though).  The tech had explained that just because there are warnings, it doesn't mean there is a problem.  These warnings do not match up with the timing of the drops, so they aren't helpful.  Our upstream power numbers had been running high (49-51 dBmV), until something had been done (possibly at the node before the tech had shown up).  After that, the upstream power numbers went back to normal (45-46 dBmV).  Since then, these upstream numbers have gotten higher again only one time (that I have noticed).  Sorry I couldn't be more helpful.  If we do end up renting the Xfinity modem and if the issue is identified (or if the problem goes away), I will update this message on the forum.  PS: We are on the schedule to have the cable line reburied, after the utilities have been marked on the ground.

Visitor

 • 

4 Messages

@user_ekosch​  Hello again.  This will be my final update, because the issue has been resolved. We were still experiencing internet drops, so we replaced the Motorola MG8702 with Xfinity's xFi modem.  The internet has not had any issues since the new modem was activated 3 weeks ago.  There has not been a single disconnection. Even though the Motorola router was an approved one and was compatible with Xfinity, we were experiencing intermittent internet drops. As a bonus, we are now saving $5/month by renting their modem with unlimited data (xFi Complete plan).  We were paying more for unlimited data when we were using our own modem.  The cable line has been reburied, so everything has been resolved.

forum icon

New to the Community?

Start Here