Why is my Cox Gigabit Service CRAWLING???
I would sure appreciate some guidance here. I try to keep up but I can get over my head pretty quickly so please bear with me. My problem is that, for well over a year, I have been paying Cox for Gig...
Forum Discussion
Thanks for the update! I think you'll have a system that works well when you are done. As a reminder, my first gen units run about 500 mbps - 590 mbps point to point when hardwired. My understanding is the new Nest WiFi Pro is supposed to support wired backhaul and gigabit speeds, but I don't have any first hand experience. I think you'll find that you have plenty of capacity when you complete your planned changes. I will confirm that getting devices to connect as you want can be a challenge. My understanding, which could be wrong, is when you perform a network restart, most devices will connect to the first acceptable signal they get, which is often the primary since it comes up (effectively) first. If I see that on a device where I really want maximum speed, I wait until the network is fully up and then reboot my higher performance devices that aren't hardwired. Phones will hit 500 +, All of the better Google cameras/Nest consoles/Chromecast devices will do better than 250.
Hi Guys, Well, sadly, all of the changes I outlined above have failed to make any difference at all. After rerouting the incoming Cox coax to a VERY centrally located location in my 1900 sq ft townhouse, I'm still getting horrible performance and speed test results as low as 20mps while sitting in clear view of mesh points only 15' away. I did a factory reset on my Arris modem this morning and then copied the event log below after it completed the restart. I Googled the results and several folks claim this is an indication that the signal coming in from the street is bad. Any further thoughts? I should mention that part of my recent troubleshooting efforts included replacing my Google mesh with my old D-Link DIR 880L and the performance got worse if anything.
Event Log
The table below contains the log of events that the SB8200 has detected. This log can be important to the service provider to help diagnose and correct problems, if any should occur.
| Date Time | Event ID | Event Level | Description |
|---|---|---|---|
| 04/10/2023 07:42 | 67061601 | 6 | "US profile assignment change. US Chan ID: 8; Previous Profile: 13; New Profile: 9 13.;CM-MAC=f8:79:0a:93:f6:b9;CMTS-MAC=00:29:c2:01:ee:3f;CM-QOS=1.1;CM-VER=3.1;" |
| 04/10/2023 07:42 | 2436694061 | 5 | "Dynamic Range Window violation" |
| 04/10/2023 07:42 | 82001200 | 5 | "RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=f8:79:0a:93:f6:b9;CMTS-MAC=00:29:c2:01:ee:3f;CM-QOS=1.1;CM-VER=3.1;" |
| 04/10/2023 07:42 | 2436694061 | 5 | "Dynamic Range Window violation" |
| 04/10/2023 07:42 | 82001200 | 5 | "RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=f8:79:0a:93:f6:b9;CMTS-MAC=00:29:c2:01:ee:3f;CM-QOS=1.1;CM-VER=3.1;" |
| 04/10/2023 07:42 | 2436694061 | 5 | "Dynamic Range Window violation" |
| 04/10/2023 07:42 | 82001200 | 5 | "RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=f8:79:0a:93:f6:b9;CMTS-MAC=00:29:c2:01:ee:3f;CM-QOS=1.1;CM-VER=3.1;" |
| 04/10/2023 07:42 | 67061600 | 6 | "DS profile assignment change. DS Chan ID: 33; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=f8:79:0a:93:f6:b9;CMTS-MAC=00:29:c2:01:ee:3f;CM-QOS=1.1;CM-VER=3.1;" |
| 04/10/2023 07:42 | 67061600 | 6 | "DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=f8:79:0a:93:f6:b9;CMTS-MAC=00:29:c2:01:ee:3f;CM-QOS=1.1;CM-VER=3.1;" |
| 04/10/2023 07:41 | 73040100 | 6 | "TLV-11 - unrecognized OID;CM-MAC=f8:79:0a:93:f6:b9;CMTS-MAC=00:29:c2:01:ee:3f;CM-QOS=1.1;CM-VER=3.1;" |
| 04/10/2023 07:41 | 68000300 | 5 | "DHCP WARNING - Non-critical field invalid in response ;CM-MAC=f8:79:0a:93:f6:b9;CMTS-MAC=00:29:c2:01:ee:3f;CM-QOS=1.1;CM-VER=3.1;" |
| 01/01/1970 00:02 | 2436694066 | 6 | "Honoring MDD; IP provisioning mode = IPv4" |
| 01/01/1970 00:01 | 85000200 | 3 | "UCD invalid or channel unusable;CM-MAC=f8:79:0a:93:f6:b9;CMTS-MAC=00:29:c2:01:ee:3f;CM-QOS=1.1;CM-VER=3.1;" |
| 01/01/1970 00:01 | 84000100 | 3 | "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=f8:79:0a:93:f6:b9;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;" |
| 01/01/1970 00:01 | 84020200 | 5 | "Lost MDD Timeout;CM-MAC=f8:79:0a:93:f6:b9;CMTS-MAC=00:00:00:00:00:00;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=f8:79:0a:93:f6:b9;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;" |
