Cox Not Allowing 3rd Modem to Connect?
Hello, I recently just started with Cox and for some reason my modem has not been able to connect to their service. At first I was using a Netgear CM700 that would signal having the upstream and downstream just fine but would be denied connection to the internet. A tech came out and we figured maybe something went wrong with my modem since the Cox Panoramic Gateway worked just fine. He recommended getting an Arris, so I did. I got the Arris SB6190, fresh from the box and the same exact issue occurred again. I have talked with support and they said everything is activated and it should be working, yet when I go onto my account it still lists the Panoramic Gateway as my modem device and I cannot add another modem to my account. There is another tech coming to try to figure it out, but largely I am wondering if anyone else has had this problem with Cox or is this some new scummy practice by them to force people into renting their modems? Does anyone have any advice in getting the modem to work? I've tried power cycle, switching coax cables, etc. Nothing has worked as again all I get are two solid blue lights for the upstream and downstream and a solid white light for the internet.Solved2KViews0likes58Comments
Intermittent modem connectivity issues
I had a tech out on July 17 and was advised that he found such horrible signals on the line for our TV service (we cancelled it a few months ago) that it was bleeding through to the line for our internet; he disconnected the television cable completely. Our internet service worked fine up until July 23rd and the issue has returned. I called tech support and the first person I spoke with simply said "you need a new modem". I called again a little later and was transferred to a tier two tech who checked the poller signals in their system; that tech said there's nothing wrong. I verified that my modem (Motorola SBG6580) has the latest firmware version of SBG6580-3.5.8.4-GA-00-505-NOSH. So right now my modem keeps rebooting itself. So I have verified the correct firmware version, Cox says the signals are fine and I have been told to get a new modem. I am still having a tough time believing this is a modem issue to be honest. My modem is slightly warm to the touch but does not feeling like it is getting too hot. I previously worked for an ISP so I have some knowledge about how all of this stuff works. We had a system called fastpoller which allowed us to actively see a modems signals and exactly what the modem was doing. We could see what the download and upload were doing as well. I helped a guy that couldn't figure out why his companies internet was so slow. When I looked at fastpoller I found the problem immediately; I saw that the upstream was completely maxed out and it was slowing everything else down. It turned out that the owner was having all of the store camera's broadcast, through their internet service, directly to his home. So I do have half a clue here....... Can anyone tell me what all these Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0 mean? I know the CMTS is on the service providers end and the CM is my cable modem. I just want to get the issue fixed because I am one of these crazy "cable cutters" and have two Google Chromcast's that are worthless with my internet constantly going out. Current signal levels: Downstream Bonded Channels Channel Lock Status Modulation Channel ID Frequency Power SNR Correctables Uncorrectables 1 Locked QAM256 33 849000000 Hz 4.8 dBmV 38.0 dB 338 0 2 Locked QAM256 34 855000000 Hz 5.2 dBmV 37.9 dB 253 0 3 Locked QAM256 35 861000000 Hz 5.0 dBmV 37.9 dB 353 0 4 Locked QAM256 36 867000000 Hz 4.6 dBmV 37.9 dB 478 0 5 Locked QAM256 37 873000000 Hz 4.7 dBmV 38.0 dB 376 0 6 Locked QAM256 38 879000000 Hz 5.4 dBmV 38.8 dB 394 0 7 Locked QAM256 39 885000000 Hz 5.3 dBmV 38.9 dB 457 0 8 Locked QAM256 40 891000000 Hz 5.0 dBmV 38.8 dB 392 0 Upstream Bonded Channels Channel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power 1 Locked ATDMA 3 5120 Ksym/sec 29800000 Hz 42.5 dBmV 2 Locked TDMA and ATDMA 1 2560 Ksym/sec 18400000 Hz 42.5 dBmV 3 Locked ATDMA 2 5120 Ksym/sec 23300000 Hz 42.5 dBmV 4 Locked ATDMA 4 5120 Ksym/sec 36300000 Hz 42.5 dBmV Here is an internal modem log from just today: Fri Jul 29 13:44:17 2016 Notice (6) TLV-11 - unrecognized OID;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; Time Not Established Warning (5) DHCP WARNING - Non-critical field invalid in response ;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.0;CM-VER=3.0; Time Not Established Critical (3) No Ranging Response received - T3 time-out Fri Jul 29 12:45:48 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; Fri Jul 29 12:44:27 2016 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; Fri Jul 29 12:44:25 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; Fri Jul 29 12:44:24 2016 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; Fri Jul 29 12:44:21 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; Fri Jul 29 12:44:20 2016 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; Fri Jul 29 12:44:20 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; Fri Jul 29 12:44:16 2016 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; Fri Jul 29 12:44:16 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; Fri Jul 29 12:44:13 2016 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; Fri Jul 29 12:44:08 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; Fri Jul 29 12:44:05 2016 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; Fri Jul 29 12:44:02 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; Fri Jul 29 12:44:01 2016 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; Fri Jul 29 12:43:58 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; Fri Jul 29 12:43:55 2016 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; Fri Jul 29 12:43:55 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; Fri Jul 29 12:43:52 2016 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; Fri Jul 29 12:43:47 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; Fri Jul 29 12:43:46 2016 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; Fri Jul 29 12:43:45 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; Fri Jul 29 12:43:41 2016 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; Fri Jul 29 12:43:41 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; Fri Jul 29 12:43:39 2016 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; Fri Jul 29 12:43:39 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; Fri Jul 29 12:43:36 2016 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; Fri Jul 29 12:43:33 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; Fri Jul 29 12:43:31 2016 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; Fri Jul 29 12:43:30 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; Fri Jul 29 12:43:30 2016 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; Fri Jul 29 12:43:30 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; Fri Jul 29 12:43:29 2016 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; Fri Jul 29 12:43:29 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; Fri Jul 29 12:43:26 2016 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; Fri Jul 29 12:43:24 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; Fri Jul 29 12:43:24 2016 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; Fri Jul 29 12:43:23 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; Fri Jul 29 12:43:21 2016 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; Fri Jul 29 12:43:19 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; Fri Jul 29 12:43:19 2016 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; Fri Jul 29 12:43:17 2016 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; Fri Jul 29 12:43:17 2016 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; Fri Jul 29 12:43:17 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; Fri Jul 29 12:43:17 2016 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; Fri Jul 29 12:43:17 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; Fri Jul 29 12:43:15 2016 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; Fri Jul 29 12:43:15 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; Fri Jul 29 12:43:14 2016 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; Fri Jul 29 12:43:14 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; Fri Jul 29 12:43:13 2016 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; Fri Jul 29 12:43:13 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; Fri Jul 29 12:43:12 2016 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; Fri Jul 29 12:43:12 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; Fri Jul 29 12:43:10 2016 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; Fri Jul 29 12:43:10 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; Fri Jul 29 12:43:09 2016 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; Fri Jul 29 12:43:07 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; Fri Jul 29 12:43:05 2016 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; Fri Jul 29 12:43:04 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; Fri Jul 29 12:43:03 2016 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; Fri Jul 29 12:43:01 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; Fri Jul 29 12:43:00 2016 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; Fri Jul 29 12:42:59 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; Fri Jul 29 12:42:58 2016 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; Fri Jul 29 12:42:58 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; Fri Jul 29 12:42:57 2016 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; Fri Jul 29 12:42:57 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; Fri Jul 29 12:42:56 2016 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; Fri Jul 29 12:42:53 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; Fri Jul 29 12:42:52 2016 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; Fri Jul 29 12:42:48 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; Fri Jul 29 12:42:47 2016 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; Fri Jul 29 12:42:44 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; Fri Jul 29 12:42:44 2016 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; Fri Jul 29 12:42:40 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; Fri Jul 29 12:42:40 2016 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; Fri Jul 29 12:42:36 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; Fri Jul 29 12:42:35 2016 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; Fri Jul 29 12:42:33 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; Fri Jul 29 12:42:32 2016 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; Fri Jul 29 12:42:28 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; Fri Jul 29 12:42:28 2016 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; Fri Jul 29 12:42:26 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; Fri Jul 29 12:42:23 2016 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0; Fri Jul 29 12:42:19 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:56:12:1c:d9:cd;CMTS-MAC=00:12:d9:54:5c:2b;CM-QOS=1.1;CM-VER=3.0;1.9KViews0likes3Comments
ARRIS SB8200 Modem levels too low. Internet Speed to Slow for Gigablast Plan I'm paying for
I been talking in circles with the cox customer support for days they say everything is fine on their end. I called ARRIS today and they said my signal levels were low on the modem and that's why I'm not getting the speed I'm paying for. I finally convinced them to send a technician out after they in multiple attempts tried to convince me something was wrong with my network equipment and tried to sell me their router that doesn't even support my plan. They said I should be getting 40 or more on all channels.814Views0likes1Comment
ARRIS SB8200 Modem levels too low. Internet Speed to Slow for Gigablast Plan I'm paying for
I been talking in circles with the cox customer support for days they say everything is fine on their end. I called ARRIS today and they said my signal levels were low on the modem and that's why I'm not getting the speed I'm paying for. I finally convinced them to send a technician out after they in multiple attempts tried to convince me something was wrong with my network equipment and tried to sell me their router that doesn't even support my plan. They said I should be getting 40 or more on all channels.