U

Monday, July 24th, 2023 11:42 PM

Closed

Connectivity Issue

I have been having connectivity issues for the last several weeks where my modem (Motorola MB7621) has been sporadically dropping the internet connection several times a day. I contacted Xfinity last week about it and they recommended that I reach out to Motorola. I did and they ultimately thought the issue was was Xfinity. Who should I contact to share what Motorola told me and have a technician come investigate the issue?

Expert

 • 

111.3K Messages

2 years ago

Please post the details of the problem that you are having right here.

7 Messages

2 years ago

After providing screenshots of the Connections screen and Error Log to Motorola, the person at Motorola stated:

“Based on the amount of errors you are getting on the Downstream Bonded Channel and the T3/4 timeouts in the Event Log, I do think its an issue with the signal coming in. Normally, the errors in the channels would be near 0 and you should have little to no timeouts either.
 
A tech from your ISP should be able to come out to look over any damaged lines and assess the signal and correct the issue for you.”

Expert

 • 

111.3K Messages

2 years ago

OK, let's start here if you wish. What do the modem's signal stats look like ? 

Please copy all of the text in its entirety of the *Downstream Power Levels*, the *SNR's* (Signal to Noise Ratios), and the *Upstream Power Level* numbers and paste them into your next post.

Please also post those modem RF error log entries in their entirety (copy and paste all of the text) but redact the CM and the CMTS MAC addresses for your privacy or else the forum bot will not allow your post to be seen publically.

7 Messages

2 years ago

Channel Lock Status Channel Type Channel ID Symb. Rate (Ksym/sec) Freq. (MHz) Pwr (dBmV)
1 Locked ATDMA 3 5120 22.8 51.5
2 Locked ATDMA 2 5120 29.2 50.7
3 Locked ATDMA 1 5120 35.6 50.4
4 Locked ATDMA 4 5120 16.4 52.2
5 Locked ATDMA 5 2560 40.4 50.5
6 Not Locked Unknown 0 0 0 0
7 Not Locked Unknown 0 0 0 0
8 Not Locked Unknown 0 0 0 0

7 Messages

2 years ago

Channel Lock Status Modulation Channel ID Freq. (MHz) Pwr (dBmV) SNR (dB) Corrected Uncorrected
1 Locked QAM256 28 573 -0.5 44 1759 2668
2 Locked QAM256 21 531 -0.8 43.8 2356 3003
3 Locked QAM256 22 537 -0.7 43.8 2043 2718
4 Locked QAM256 23 543 -0.6 43.9 2102 3071
5 Locked QAM256 24 549 -0.4 44.1 1960 2785
6 Locked QAM256 25 555 -0.3 44.1 1892 3005
7 Locked QAM256 26 561 -0.4 44.1 1667 2359
8 Locked QAM256 27 567 -0.4 44.1 1857 2062
9 Locked QAM256 29 579 -0.2 44.2 1563 2452
10 Locked QAM256 30 585 -0.2 44.3 1413 2283
11 Locked QAM256 31 591 0 44.4 1499 2017
12 Locked QAM256 32 597 0 44.5 1360 1814
13 Locked QAM256 33 603 -0.2 44.3 1384 1915
14 Locked QAM256 34 609 -0.4 44.1 1291 1811
15 Locked QAM256 35 615 -0.6 43.9 1293 1824
16 Locked QAM256 36 621 -0.6 43.9 1138 1336
17 Locked QAM256 37 627 -0.4 45.4 1171 2476
18 Locked QAM256 38 633 0 45.7 1110 2211
19 Locked QAM256 39 639 0.2 46 1029 2056
20 Locked QAM256 40 645 0.3 46 985 2008
21 Locked QAM256 41 651 0.2 45.8 879 1877
22 Locked QAM256 42 657 0.1 46 989 1816
23 Locked QAM256 43 663 0 46 910 1831
24 Locked QAM256 44 669 0.2 45.5 970 1812
Total 34620 53210

7 Messages

2 years ago

Time Priority Description
Mon Jul 24 14:44:45 2023 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;
Mon Jul 24 14:44:46 2023 Warning (5) Dynamic Range Window violation
Mon Jul 24 14:44:49 2023 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;
Mon Jul 24 14:45:42 2023 Warning (5) Dynamic Range Window violation
Mon Jul 24 14:45:54 2023 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;
Mon Jul 24 14:46:52 2023 Warning (5) Dynamic Range Window violation
Mon Jul 24 14:46:59 2023 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;
Mon Jul 24 14:47:48 2023 Warning (5) Dynamic Range Window violation
Mon Jul 24 14:48:01 2023 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;
Mon Jul 24 14:48:02 2023 Warning (5) Dynamic Range Window violation
Mon Jul 24 14:48:04 2023 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;
Mon Jul 24 14:48:58 2023 Warning (5) Dynamic Range Window violation
Mon Jul 24 14:49:09 2023 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;
Mon Jul 24 14:49:50 2023 Warning (5) Dynamic Range Window violation
Mon Jul 24 14:49:50 2023 Warning (5) DBC-REQ denied - confirmation code 210: reject-dynamic-range-windowviolation;
Mon Jul 24 14:50:14 2023 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;
Mon Jul 24 16:35:35 2023 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;
Mon Jul 24 16:36:40 2023 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;
Mon Jul 24 16:36:51 2023 Notice (6) Honoring MDD; IP provisioning mode = IPv6
Mon Jul 24 16:37:01 2023 Warning (5) Dynamic Range Window violation
Tue Jul 25 06:48:58 2023 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;
Tue Jul 25 06:59:30 2023 Critical (3) No Ranging Response received - T3 time-out;
Tue Jul 25 07:14:47 2023 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;
Tue Jul 25 07:25:17 2023 Critical (3) No Ranging Response received - T3 time-out;
Tue Jul 25 08:21:10 2023 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;
Tue Jul 25 08:21:29 2023 Warning (5) Dynamic Range Window violation
Tue Jul 25 17:34:48 2023 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;
Tue Jul 25 17:34:51 2023 Error (4) DBC-ACK not received;
Tue Jul 25 17:35:53 2023 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;
Tue Jul 25 17:37:23 2023 Critical (3) No Ranging Response received - T3 time-out;
Tue Jul 25 17:37:59 2023 Notice (6) Honoring MDD; IP provisioning mode = IPv6
Tue Jul 25 18:00:12 2023 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;

Expert

 • 

111.3K Messages

2 years ago

The upstream power is too high and it may be intermittently fluctuating even farther out-of-spec. 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 Home Depot, Target, Wal-Mart, 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, abrasions, 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 !

7 Messages

2 years ago

I don’t have any splitters in my home and my wires appear in good shape. What is the easiest avenue to book a tech to come investigate and correct the issue?

Expert

 • 

111.3K Messages

2 years ago

I'm going to refer your issue to the Comcast corporate employees (The Digital Care Team) who are available to these boards. They will be able to arrange a tech appointment for you. Good luck ! Please post back here with how things turn out.

7 Messages

2 years ago

Thank you for referring me. I have not heard from the Digital Care Team yet. Will they connect with me on this board or some other channel? 

Official Employee

 • 

2K Messages

Hello and thank you for reaching out to us for help @uer_f3c0f0 we would love to investigate the best resolution with you in our Direct Messages. Here is how you can send us a DM with your full name and address: 

(Full credit to @BruceW for this excellent explanation!) 



"Search for Xfinity Support" won't work. To send a "Direct Messaging" message to Xfinity Support:



  • Click "Sign In" if necessary





  • 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



See https://forums.xfinity.com/conversations/email/cant-create-a-new-email-address/605e52b726aa974d63032d02?commentId=606107ea738c7f46a02b830e for an example.

I am an Official Xfinity Employee.
Official Employees are from multiple teams within Xfinity: CARE, Product, Leadership.
We ask that you post publicly so people with similar questions may benefit from the conversation.
Was your question answered? Please, mark a reply as the Accepted Answer.tick
forum icon

New to the Community?

Start Here