Community Forum

"No Ranging Response received" and a number of other events on our SB8200 and Gigabit

New Poster

"No Ranging Response received" and a number of other events on our SB8200 and Gigabit

I have an external wired-only Ubiquiti EdgeRouter X router, connected to a Moto ARRIS SB8200.  Most of the network here in the house is wired with Cat5e. In general the network in the house seems well behaved.

Recently, I have seen the modem reset a number of times during the last couple of weeks. Internet has been interrupted for a minute or two periodically during the day, and it appears to be happening a lot. We so far have not seen a long outage.

I just watched being unable to access the modem from inside the home network. The lights on the modem appeared to be fine, and then the modem appeared to reset, judging from the changed state of the front panel LEDs. The events occuring as this happened are below.

The most recent events from the SB8200 event log. I have no idea what this stuff means:

 

 

 

 

09/03/2019 17:12

2436694061

5

Dynamic Range Window violation

09/03/2019 17:12

82001200

5

RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=b0:da:f9:16:49:c5;CMTS-MAC=00:56:2b:76:e7:23;CM-QOS=1.1;CM-VER=3.1;

09/03/2019 17:12

2436694061

5

Dynamic Range Window violation

09/03/2019 17:12

82001200

5

RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=b0:da:f9:16:49:c5;CMTS-MAC=00:56:2b:76:e7:23;CM-QOS=1.1;CM-VER=3.1;

09/03/2019 17:12

2436694061

5

Dynamic Range Window violation

09/03/2019 17:12

82001200

5

RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=b0:da:f9:16:49:c5;CMTS-MAC=00:56:2b:76:e7:23;CM-QOS=1.1;CM-VER=3.1;

09/03/2019 17:12

2436694061

5

Dynamic Range Window violation

09/03/2019 17:12

82001200

5

RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=b0:da:f9:16:49:c5;CMTS-MAC=00:56:2b:76:e7:23;CM-QOS=1.1;CM-VER=3.1;

09/03/2019 17:12

82000200

3

No Ranging Response received - T3 time-out;CM-MAC=b0:da:f9:16:49:c5;CMTS-MAC=00:56:2b:76:e7:23;CM-QOS=1.1;CM-VER=3.1;

09/03/2019 17:12

67061600

6

DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1.;CM-MAC=b0:da:f9:16:49:c5;CMTS-MAC=00:56:2b:76:e7:23;CM-QOS=1.1;CM-VER=3.1;

01/01/1970 00:00

2436694066

6

Honoring MDD; IP provisioning mode = IPv6

 

 

 

 

01/01/1970 00:00

84000100

3

SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=b0:da:f9:16:49:c5;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;

 

 

 

 

09/03/2019 17:11

82000400

3

Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:da:f9:16:49:c5;CMTS-MAC=00:56:2b:76:e7:23;CM-QOS=1.1;CM-VER=3.1;

09/03/2019 17:10

82000700

3

Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=b0:da:f9:16:49:c5;CMTS-MAC=00:56:2b:76:e7:23;CM-QOS=1.1;CM-VER=3.1;

09/03/2019 17:10

82000400

3

Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:da:f9:16:49:c5;CMTS-MAC=00:56:2b:76:e7:23;CM-QOS=1.1;CM-VER=3.1;

09/03/2019 17:10

82000700

3

Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=b0:da:f9:16:49:c5;CMTS-MAC=00:56:2b:76:e7:23;CM-QOS=1.1;CM-VER=3.1;

09/03/2019 17:10

82000400

3

Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:da:f9:16:49:c5;CMTS-MAC=00:56:2b:76:e7:23;CM-QOS=1.1;CM-VER=3.1;

09/03/2019 17:10

82000700

3

Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=b0:da:f9:16:49:c5;CMTS-MAC=00:56:2b:76:e7:23;CM-QOS=1.1;CM-VER=3.1;

09/03/2019 17:10

82000400

3

Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:da:f9:16:49:c5;CMTS-MAC=00:56:2b:76:e7:23;CM-QOS=1.1;CM-VER=3.1;

09/03/2019 17:10

82000700

3

Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=b0:da:f9:16:49:c5;CMTS-MAC=00:56:2b:76:e7:23;CM-QOS=1.1;CM-VER=3.1;

09/03/2019 17:10

82000400

3

Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:da:f9:16:49:c5;CMTS-MAC=00:56:2b:76:e7:23;CM-QOS=1.1;CM-VER=3.1;

09/03/2019 17:10

82000700

3

Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=b0:da:f9:16:49:c5;CMTS-MAC=00:56:2b:76:e7:23;CM-QOS=1.1;CM-VER=3.1;

09/03/2019 17:10

82000400

3

Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:da:f9:16:49:c5;CMTS-MAC=00:56:2b:76:e7:23;CM-QOS=1.1;CM-VER=3.1;

 

 

 

 

09/03/2019 16:03

82000200

3

No Ranging Response received - T3 time-out;CM-MAC=b0:da:f9:16:49:c5;CMTS-MAC=00:56:2b:76:e7:23;CM-QOS=1.1;CM-VER=3.1;

09/03/2019 16:03

82000200

3

No Ranging Response received - T3 time-out;CM-MAC=b0:da:f9:16:49:c5;CMTS-MAC=00:56:2b:76:e7:23;CM-QOS=1.1;CM-VER=3.1;

01/01/1970 00:00

84000100

3

SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=b0:da:f9:16:49:c5;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;

09/03/2019 16:02

82000700

3

Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=b0:da:f9:16:49:c5;CMTS-MAC=00:56:2b:76:e7:23;CM-QOS=1.1;CM-VER=3.1;

09/03/2019 16:02

82000700

3

Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=b0:da:f9:16:49:c5;CMTS-MAC=00:56:2b:76:e7:23;CM-QOS=1.1;CM-VER=3.1;

09/03/2019 16:02

82000400

3

Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:da:f9:16:49:c5;CMTS-MAC=00:56:2b:76:e7:23;CM-QOS=1.1;CM-VER=3.1;

09/03/2019 16:02

82000700

3

Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=b0:da:f9:16:49:c5;CMTS-MAC=00:56:2b:76:e7:23;CM-QOS=1.1;CM-VER=3.1;

09/03/2019 16:01

82000400

3

Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:da:f9:16:49:c5;CMTS-MAC=00:56:2b:76:e7:23;CM-QOS=1.1;CM-VER=3.1;

09/03/2019 16:01

84000500

3

SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=b0:da:f9:16:49:c5;CMTS-MAC=00:56:2b:76:e7:23;CM-QOS=1.1;CM-VER=3.1;

09/03/2019 16:01

82000700

3

Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=b0:da:f9:16:49:c5;CMTS-MAC=00:56:2b:76:e7:23;CM-QOS=1.1;CM-VER=3.1;

09/03/2019 16:01

82000400

3

Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:da:f9:16:49:c5;CMTS-MAC=00:56:2b:76:e7:23;CM-QOS=1.1;CM-VER=3.1;

09/03/2019 14:00

73000200

3

REG RSP not received;CM-MAC=b0:da:f9:16:49:c5;CMTS-MAC=00:56:2b:76:e7:23;CM-QOS=1.1;CM-VER=3.1;

09/03/2019 14:00

82000500

3

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:da:f9:16:49:c5;CMTS-MAC=00:56:2b:76:e7:23;CM-QOS=1.1;CM-VER=3.1;

09/03/2019 14:00

73000200

3

REG RSP not received;CM-MAC=b0:da:f9:16:49:c5;CMTS-MAC=00:56:2b:76:e7:23;CM-QOS=1.1;CM-VER=3.1;

 

 

 

 

01/01/1970 00:00

84000100

3

SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=b0:da:f9:16:49:c5;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;

 

 

 

 

09/03/2019 13:59

82000400

3

Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:da:f9:16:49:c5;CMTS-MAC=00:56:2b:76:e7:23;CM-QOS=1.1;CM-VER=3.1;

09/03/2019 13:59

82000700

3

Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=b0:da:f9:16:49:c5;CMTS-MAC=00:56:2b:76:e7:23;CM-QOS=1.1;CM-VER=3.1;

09/03/2019 13:59

82000400

3

Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:da:f9:16:49:c5;CMTS-MAC=00:56:2b:76:e7:23;CM-QOS=1.1;CM-VER=3.1;

09/03/2019 13:57

82000500

3

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:da:f9:16:49:c5;CMTS-MAC=00:56:2b:76:e7:23;CM-QOS=1.1;CM-VER=3.1;

09/03/2019 13:57

82000500

3

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:da:f9:16:49:c5;CMTS-MAC=00:56:2b:76:e7:23;CM-QOS=1.1;CM-VER=3.1;

09/03/2019 13:57

82000500

3

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:da:f9:16:49:c5;CMTS-MAC=00:56:2b:76:e7:23;CM-QOS=1.1;CM-VER=3.1;

09/03/2019 13:57

82000500

3

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:da:f9:16:49:c5;CMTS-MAC=00:56:2b:76:e7:23;CM-QOS=1.1;CM-VER=3.1;

09/03/2019 13:57

82000500

3

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:da:f9:16:49:c5;CMTS-MAC=00:56:2b:76:e7:23;CM-QOS=1.1;CM-VER=3.1;

09/03/2019 13:57

82000500

3

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:da:f9:16:49:c5;CMTS-MAC=00:56:2b:76:e7:23;CM-QOS=1.1;CM-VER=3.1;

09/03/2019 13:57

82000500

3

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:da:f9:16:49:c5;CMTS-MAC=00:56:2b:76:e7:23;CM-QOS=1.1;CM-VER=3.1;

09/03/2019 13:57

82000500

3

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:da:f9:16:49:c5;CMTS-MAC=00:56:2b:76:e7:23;CM-QOS=1.1;CM-VER=3.1;

09/03/2019 13:56

82000500

3

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:da:f9:16:49:c5;CMTS-MAC=00:56:2b:76:e7:23;CM-QOS=1.1;CM-VER=3.1;

 

 

 

 

01/01/1970 00:00

84000100

3

SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=b0:da:f9:16:49:c5;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;

 

 

 

 

09/03/2019 13:51

82000400

3

Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:da:f9:16:49:c5;CMTS-MAC=00:56:2b:76:e7:23;CM-QOS=1.1;CM-VER=3.1;

09/03/2019 13:51

82000700

3

Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=b0:da:f9:16:49:c5;CMTS-MAC=00:56:2b:76:e7:23;CM-QOS=1.1;CM-VER=3.1;

09/03/2019 13:51

82000400

3

Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:da:f9:16:49:c5;CMTS-MAC=00:56:2b:76:e7:23;CM-QOS=1.1;CM-VER=3.1;

09/03/2019 13:51

82000700

3

Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=b0:da:f9:16:49:c5;CMTS-MAC=00:56:2b:76:e7:23;CM-QOS=1.1;CM-VER=3.1;

09/03/2019 13:51

82000400

3

Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:da:f9:16:49:c5;CMTS-MAC=00:56:2b:76:e7:23;CM-QOS=1.1;CM-VER=3.1;

09/03/2019 13:51

82000700

3

Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=b0:da:f9:16:49:c5;CMTS-MAC=00:56:2b:76:e7:23;CM-QOS=1.1;CM-VER=3.1;

09/03/2019 13:51

82000400

3

Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:da:f9:16:49:c5;CMTS-MAC=00:56:2b:76:e7:23;CM-QOS=1.1;CM-VER=3.1;

09/03/2019 13:51

84000500

3

SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=b0:da:f9:16:49:c5;CMTS-MAC=00:56:2b:76:e7:23;CM-QOS=1.1;CM-VER=3.1;

09/03/2019 13:51

82000700

3

Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=b0:da:f9:16:49:c5;CMTS-MAC=00:56:2b:76:e7:23;CM-QOS=1.1;CM-VER=3.1;

09/03/2019 13:50

82000400

3

Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:da:f9:16:49:c5;CMTS-MAC=00:56:2b:76:e7:23;CM-QOS=1.1;CM-VER=3.1;

09/03/2019 13:50

84000500

3

SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=b0:da:f9:16:49:c5;CMTS-MAC=00:56:2b:76:e7:23;CM-QOS=1.1;CM-VER=3.1;

09/03/2019 13:50

82000700

3

Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=b0:da:f9:16:49:c5;CMTS-MAC=00:56:2b:76:e7:23;CM-QOS=1.1;CM-VER=3.1;

09/03/2019 13:50

82000400

3

Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:da:f9:16:49:c5;CMTS-MAC=00:56:2b:76:e7:23;CM-QOS=1.1;CM-VER=3.1;

09/02/2019 20:12

82000700

3

Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=b0:da:f9:16:49:c5;CMTS-MAC=00:56:2b:76:e7:23;CM-QOS=1.1;CM-VER=3.1;

09/02/2019 20:12

84000500

3

SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=b0:da:f9:16:49:c5;CMTS-MAC=00:56:2b:76:e7:23;CM-QOS=1.1;CM-VER=3.1;

09/02/2019 20:08

84000100

3

SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=b0:da:f9:16:49:c5;CMTS-MAC=00:56:2b:76:e7:23;CM-QOS=1.1;CM-VER=3.1;

09/02/2019 07:42

82000500

3

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:da:f9:16:49:c5;CMTS-MAC=00:56:2b:76:e7:23;CM-QOS=1.1;CM-VER=3.1;



New Poster

Re: "No Ranging Response received" and a number of other events on our SB8200 and Gigabit

Procedure Status Comment
Acquire Downstream Channel 663000000 Hz Locked
Connectivity State OK Operational
Boot State OK Operational
Configuration File OK  
Security Enabled BPI+
DOCSIS Network Access Enabled Allowed
New Poster

Re: "No Ranging Response received" and a number of other events on our SB8200 and Gigabit

Channel ID Lock Status Modulation Frequency Power SNR/MER Corrected Uncorrectables
29 Locked QAM256 663000000 Hz 4.8 dBmV 38.5 dB 1 0
1 Locked QAM256 483000000 Hz 5.0 dBmV 39.2 dB 0 0
2 Locked QAM256 489000000 Hz 5.1 dBmV 39.0 dB 0 0
3 Locked QAM256 495000000 Hz 5.1 dBmV 39.0 dB 0 0
4 Locked QAM256 507000000 Hz 5.4 dBmV 39.1 dB 0 0
5 Locked QAM256 513000000 Hz 5.5 dBmV 39.1 dB 0 0
6 Locked QAM256 519000000 Hz 5.5 dBmV 39.0 dB 0 0
7 Locked QAM256 525000000 Hz 5.8 dBmV 39.2 dB 0 0
8 Locked QAM256 531000000 Hz 5.5 dBmV 39.0 dB 0 0
9 Locked QAM256 543000000 Hz 5.4 dBmV 39.1 dB 0 0
10 Locked QAM256 549000000 Hz 5.4 dBmV 39.1 dB 0 0
11 Locked QAM256 555000000 Hz 5.2 dBmV 39.0 dB 0 0
12 Locked QAM256 561000000 Hz 5.6 dBmV 39.2 dB 0 0
13 Locked QAM256 567000000 Hz 5.6 dBmV 39.1 dB 0 0
14 Locked QAM256 573000000 Hz 5.8 dBmV 39.0 dB 0 0
15 Locked QAM256 579000000 Hz 5.8 dBmV 39.1 dB 0 0
16 Locked QAM256 585000000 Hz 5.6 dBmV 39.1 dB 0 0
17 Locked QAM256 591000000 Hz 5.6 dBmV 39.1 dB 0 0
18 Locked QAM256 597000000 Hz 5.5 dBmV 39.1 dB 0 0
19 Locked QAM256 603000000 Hz 6.1 dBmV 39.3 dB 0 0
20 Locked QAM256 609000000 Hz 5.8 dBmV 39.1 dB 0 0
21 Locked QAM256 615000000 Hz 6.1 dBmV 39.2 dB 0 0
22 Locked QAM256 621000000 Hz 6.0 dBmV 39.0 dB 0 0
23 Locked QAM256 627000000 Hz 5.7 dBmV 39.0 dB 0 0
24 Locked QAM256 633000000 Hz 5.1 dBmV 38.9 dB 0 0
25 Locked QAM256 639000000 Hz 4.7 dBmV 38.7 dB 0 0
26 Locked QAM256 645000000 Hz 4.6 dBmV 38.5 dB 0 0
27 Locked QAM256 651000000 Hz 4.5 dBmV 38.6 dB 0 0
28 Locked QAM256 657000000 Hz 4.8 dBmV 38.8 dB 0 0
30 Locked QAM256 669000000 Hz 5.3 dBmV 38.7 dB 0 0
31 Locked QAM256 675000000 Hz 4.9 dBmV 38.5 dB 0 0
32 Locked QAM256 681000000 Hz 4.9 dBmV 38.8 dB 0 0
159 Locked Other 722000000 Hz 6.7 dBmV 37.8 dB 12437250 0


 

 
Upstream Bonded Channels
Channel Channel ID Lock Status US Channel Type Frequency Width Power
1 1 Locked SC-QAM Upstream 30100000 Hz 6400000 Hz 50.0 dBmV
2 2 Locked SC-QAM Upstream 36500000 Hz 6400000 Hz 49.0 dBmV
3 3 Locked SC-QAM Upstream 17300000 Hz 6400000 Hz 52.0 dBmV
4 4 Locked SC-QAM Upstream 23700000 Hz 6400000 Hz 51.0 dBmV
New Poster

Re: "No Ranging Response received" and a number of other events on our SB8200 and Gigabit

Tech support on the phone indicated that the signal appeared to be just fine, but the log indicated to her that the last reset happened several hours prior two the ones that had just happened, so I guess it takes a while for Comcast logging to catch up.

Contributor

Re: "No Ranging Response received" and a number of other events on our SB8200 and Gigabit

I would reccomend asking them to ensure that your lines from pole to modem are checked. I'm dealing with a similar issue, and that's what we've done at this point. New lines, mulitple modems, and the issue is still occuring. I was wondering if log timing could be an issue, but I learned today that some CMTS doesn't observe DST, so the date/time is always off anyway. They do this to avoid time inconsistencies with regions that don't support or have DST. So if that's how Comcast runs thing, support sounds like they don't understand that either. Any error you get right now will show it happened an hour ago as a result. That's what my logs look like as well. I have also heard some companies be concerned when time is off, so without knowing what the Comcast network expects for time I can't say if it's potentially related or not.  Like I said though, ask for a tech to at least ensure from pole to modem is good, and then they can escalate to the network ops team from there if the issues don't correct. That's the step I'm at right now. Good luck!

Expert

Re: "No Ranging Response received" and a number of other events on our SB8200 and Gigabit

The upstream power is on the high side and it may be intermittently fluctuating even higher to out of spec levels. That can cause random disconnects, spontaneous re-booting of the modem, speed, packet loss, and latency problems.

In a self troubleshooting 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-1002 MHz, bi-directional, and no gold colored garbage types like GE, RadioShack, RCA, Philips, Leviton, Magnavox, and Rocketfish from big box stores like Home Depot, Lowes, Target, Wal-Mart etc. Splitters should be swapped with known to be good / new ones to test

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.



I am not a Comcast Employee.
I am a Customer Expert volunteering my time to help other customers here in the Forums.
We ask that you post publicly so people with similar questions may benefit from the conversation.
Was your question answered? Mark the post as Best Answer!
New Poster

Re: "No Ranging Response received" and a number of other events on our SB8200 and Gigabit

There's a splitter inside the house next to the modem. It is an Extreme Broadband Engineering BDS102H 5-1002 MHz / EMI -130dB with two -3.5dB OUT. I had been using Comcast Business internet service when I had the XFINITY Gigabit service installed, and had them both running during the shakedown cruise with the gigabit service. I assumed that was the reason for the splitter. Comcast Business service was shut down here a while ago, but I didn't need to mess with the coax side.

You're suggesting then, among other things, that I can probably go ahead and remove the splitter entirely, since all it's doing is getting in the way, splitting for no good reason?

Expert

Re: "No Ranging Response received" and a number of other events on our SB8200 and Gigabit

Yup. If it's not needed, that's a step in the right direction.


I am not a Comcast Employee.
I am a Customer Expert volunteering my time to help other customers here in the Forums.
We ask that you post publicly so people with similar questions may benefit from the conversation.
Was your question answered? Mark the post as Best Answer!