no ranging response

7 Topics

SYNC Timing Synchronization failure - Loss of Sync - Slow Speeds, Drops, etc
Hello, I have the "Ultimate" Internet tier and over the last few days, my service has been atrociously bad. There are times when I get close to the speeds I am paying for and other times not even close. I was wondering if my power levels on my modem were in-spec? Also, seeing quite a few of the following log messages in my modem: SYNC Timing Synchronization failure - Loss of Sync Started Unicast Maintenance Ranging - No Response received - T3 time-out MDD message timeout Downstream Bonded Channels Channel Lock Status Modulation Channel ID Frequency Power SNR Corrected Uncorrectables 1 Locked QAM256 22 909000000 Hz 8.7 dBmV 39.0 dB 164583 338195 2 Locked QAM256 1 783000000 Hz 10.2 dBmV 39.9 dB 0 0 3 Locked QAM256 2 789000000 Hz 10.2 dBmV 39.8 dB 0 0 4 Locked QAM256 3 795000000 Hz 10.0 dBmV 39.7 dB 0 0 5 Locked QAM256 4 801000000 Hz 10.1 dBmV 39.8 dB 0 0 6 Locked QAM256 5 807000000 Hz 10.0 dBmV 39.8 dB 0 0 7 Locked QAM256 6 813000000 Hz 9.9 dBmV 39.8 dB 0 0 8 Locked QAM256 7 819000000 Hz 9.9 dBmV 39.8 dB 0 0 9 Locked QAM256 8 825000000 Hz 10.0 dBmV 39.9 dB 0 0 10 Locked QAM256 17 879000000 Hz 9.5 dBmV 39.5 dB 4 0 11 Locked QAM256 18 885000000 Hz 9.4 dBmV 39.4 dB 1 0 12 Locked QAM256 19 891000000 Hz 9.2 dBmV 39.3 dB 3 0 13 Locked QAM256 20 897000000 Hz 9.2 dBmV 39.3 dB 2 0 14 Locked QAM256 21 903000000 Hz 8.4 dBmV 39.0 dB 182726 774664 15 Locked QAM256 23 915000000 Hz 9.0 dBmV 39.0 dB 201227 812336 16 Locked QAM256 24 921000000 Hz 8.9 dBmV 38.8 dB 612277 1054773 Upstream Bonded Channels Channel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power 1 Locked ATDMA 2 5120 Ksym/sec 23300000 Hz 37.7 dBmV 2 Locked TDMA and ATDMA 1 2560 Ksym/sec 18400000 Hz 38.3 dBmV 3 Locked ATDMA 3 5120 Ksym/sec 29800000 Hz 39.8 dBmV 4 Locked ATDMA 4 5120 Ksym/sec 36300000 Hz 41.3 dBmV Current System Time:Sat Oct 14 11:56:41 2017
2URGSE
8 years ago Place Archives
2.2KViews
0likes
1Comment
Frequent bursts of internet outages. 5 - 10 second outages. Using the Arris Panoramic.
So Ive been having issues with the new Panoramic that was just installed. My internet just keeps dropping service and I have no idea why. I checked the event log and this is what it saw. Can anyone tell me what this means? 10/4/2017 9:29 73040100 6 TLV-11 - unrecognized OID;CM-MAC=18:b8:1f:06:42:19;CMTS-MAC=00:38:df:9a:5a:41;CM-QOS=1.1;CM-VER=3.0; 10/4/2017 14:06 84000700 5 RCS Partial Service;CM-MAC=18:b8:1f:06:42:19;CMTS-MAC=00:38:df:9a:5a:41;CM-QOS=1.1;CM-VER=3.0; 10/4/2017 17:41 82000200 3 No Ranging Response received - T3 time-out;CM-MAC=18:b8:1f:06:42:19;CMTS-MAC=00:38:df:9a:5a:41;CM-QOS=1.1;CM-VER=3.0;
Skyguy
8 years ago Place Archives
1.1KViews
0likes
1Comment
My internet keeps going down for 5-10 intervals and ive had 5 techs out here.
So starting on 9/28/17 my internet started having interments drops in connection. Ive had 5 techs out here since then and theyve replaced all my lines my router 3x's and run several speed tests. None of them have been able to figure out the issue and they refuse to check the node for corrosion or anything like that. Ive asked 3 times now for someone to check the node and I keep getting the run around. I cant stream or play video games because everytime i try my internet will go down several times during the hour. I had one technician tell me it was because of the website i use to watch videogame streams, which is twitch.tv. At this point im really thnking about switching because im getting so sick and tired of all the run around ive been getting. Also i checked some levels and logs while it was happening and unfortunately i cant ever check it while its happening because my internet isnt working but this is the most i could find. 10/3/2017 8:54 84000700 5 RCS Partial Service;CM-MAC=78:23:ae:21:a6:9d;CMTS-MAC=00:38:df:9a:5a:41;CM-QOS=1.1;CM-VER=3.0; 10/3/2017 8:54 84000500 3 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=78:23:ae:21:a6:9d;CMTS-MAC=00:38:df:9a:5a:41;CM-QOS=1.1;CM-VER=3.0; 10/3/2017 8:54 84020200 5 Lost MDD Timeout;CM-MAC=78:23:ae:21:a6:9d;CMTS-MAC=00:38:df:9a:5a:41;CM-QOS=1.1;CM-VER=3.0; 10/3/2017 8:54 84000700 5 RCS Partial Service;CM-MAC=78:23:ae:21:a6:9d;CMTS-MAC=00:38:df:9a:5a:41;CM-QOS=1.1;CM-VER=3.0; 10/3/2017 8:56 84000500 3 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=78:23:ae:21:a6:9d;CMTS-MAC=00:38:df:9a:5a:41;CM-QOS=1.1;CM-VER=3.0; 10/3/2017 8:56 84000700 5 RCS Partial Service;CM-MAC=78:23:ae:21:a6:9d;CMTS-MAC=00:38:df:9a:5a:41;CM-QOS=1.1;CM-VER=3.0; 10/3/2017 8:56 84000500 3 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=78:23:ae:21:a6:9d;CMTS-MAC=00:38:df:9a:5a:41;CM-QOS=1.1;CM-VER=3.0; 10/3/2017 8:56 84020200 5 Lost MDD Timeout;CM-MAC=78:23:ae:21:a6:9d;CMTS-MAC=00:38:df:9a:5a:41;CM-QOS=1.1;CM-VER=3.0; 10/3/2017 8:57 82000400 3 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=78:23:ae:21:a6:9d;CMTS-MAC=00:38:df:9a:5a:41;CM-QOS=1.1;CM-VER=3.0; 10/3/2017 9:06 73040100 6 TLV-11 - unrecognized OID;CM-MAC=78:23:ae:21:a6:9d;CMTS-MAC=00:38:df:9a:5a:41;CM-QOS=1.1;CM-VER=3.0; 10/3/2017 9:08 84000700 5 RCS Partial Service;CM-MAC=78:23:ae:21:a6:9d;CMTS-MAC=00:38:df:9a:5a:41;CM-QOS=1.1;CM-VER=3.0; 10/3/2017 9:08 84000500 3 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=78:23:ae:21:a6:9d;CMTS-MAC=00:38:df:9a:5a:41;CM-QOS=1.1;CM-VER=3.0; 10/3/2017 9:08 84000700 5 RCS Partial Service;CM-MAC=78:23:ae:21:a6:9d;CMTS-MAC=00:38:df:9a:5a:41;CM-QOS=1.1;CM-VER=3.0; 10/3/2017 9:08 84000500 3 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=78:23:ae:21:a6:9d;CMTS-MAC=00:38:df:9a:5a:41;CM-QOS=1.1;CM-VER=3.0; 10/3/2017 9:08 84020200 5 Lost MDD Timeout;CM-MAC=78:23:ae:21:a6:9d;CMTS-MAC=00:38:df:9a:5a:41;CM-QOS=1.1;CM-VER=3.0; 10/3/2017 9:26 73040100 6 TLV-11 - unrecognized OID;CM-MAC=78:23:ae:21:a6:9d;CMTS-MAC=00:38:df:9a:5a:41;CM-QOS=1.1;CM-VER=3.0; 1/1/1970 0:01 82000200 3 No Ranging Response received - T3 time-out;CM-MAC=78:23:ae:21:a6:9d;CMTS-MAC=00:38:df:9a:5a:41;CM-QOS=1.1;CM-VER=3.0; 10/3/2017 9:55 73040100 6 TLV-11 - unrecognized OID;CM-MAC=78:23:ae:21:a6:9d;CMTS-MAC=00:38:df:9a:5a:41;CM-QOS=1.1;CM-VER=3.0; 10/3/2017 11:16 82000200 3 No Ranging Response received - T3 time-out;CM-MAC=78:23:ae:21:a6:9d;CMTS-MAC=00:38:df:9a:5a:41;CM-QOS=1.1;CM-VER=3.0; 10/3/2017 23:51 73040100 6 TLV-11 - unrecognized OID;CM-MAC=78:23:ae:21:a6:9d;CMTS-MAC=00:38:df:9a:5a:41;CM-QOS=1.1;CM-VER=3.0;
Skyguy
8 years ago Place Archives
2KViews
0likes
5Comments
modem goes up and down
I have had 3 cox tech visits. tested and rebuit connections from street and all splitters replaced by coxtech. Now scheduled for a 4th visit. Called support - they cant see returns from the modem. I'm told it is the modem. Im not sure - same happened on old modem. I replaced with Linksys CM3008 in Nov 16 and still happens. Router is an Orbi. I post recent summary and last 20 events from the modem log here. I think line level is 36 db? this is without countour in the chain - direct wall to modem. no splitter - although it is a tech provided splitter and last tech even built the coax cables himself to make sure they were good. I deas? I am not sure why the 4th service call will be better than last 3? Esp if no one looks at the logs. Not enjoying having to chose between countour or internet - want to have both at same time. 18 year Cox customer here! DOCSIS Overview Network Access Permitted IP Address 10.73.45.139 Subnet Mask 255.255.240.0 Gateway IP 10.73.32.1 DHCP Lease Time D: 07 H: 00 M: 00 S: 00 Downstream Overview Port ID Frequency (Hz) Modulation Signal strength (dBmV) Signal noise ratio (dB) Octets Correcteds Uncorrectables Channel ID 1 795000000 256QAM -0.847 37.093 2955993571 1597 621 3 2 783000000 256QAM -0.359 37.093 2955987673 197 642 1 3 789000000 256QAM -1.150 37.093 2956010846 235 609 2 4 801000000 256QAM -1.388 37.093 2956021960 955 606 4 5 807000000 256QAM -1.476 37.636 2955997473 271 703 5 6 813000000 256QAM -1.631 37.636 2955998789 126 654 6 7 819000000 256QAM -1.988 37.356 2956007829 211 632 7 8 825000000 256QAM -1.925 37.093 2956007015 223 764 8 Reset FEC Counters Upstream Overview Port ID Frequency (Hz) BandWidth (Hz) Modulation Type DOCSIS Mode Signal Strength (dBmV) Channel ID 1 10000000 6400000 64QAM ATDMA 57.000 --- 2 30400195 6400000 64QAM ATDMA 51.000 3
robr
8 years ago Place Archives
4.1KViews
0likes
9Comments
Multiple Errors on my Docsis 3.0 model with Cox
I have noticed some speed issues with my Cox Internet connection so I logged in to look at the logs on the modem and found the following errors which are repeating every day. Before I call support and get told nothing is wrong I was hoping for some expert direction from the collective within the forum. Apr 13 2017 07:17:29 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=d0:39:b3:f8:ed:dd;CMTS-MAC=00:1b:54:c9:87:c7;CM-QOS=1.1;CM-VER=3.0; Apr 13 2017 07:12:30 3-Critical R06.0 Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=d0:39:b3:f8:ed:dd;CMTS-MAC=00:1b:54:c9:87:c7;CM-QOS=1.1;CM-VER=3.0; Apr 13 2017 07:12:30 3-Critical R03.0 Ranging Request Retries exhausted;CM-MAC=d0:39:b3:f8:ed:dd;CMTS-MAC=00:1b:54:c9:87:c7;CM-QOS=1.1;CM-VER=3.0; Apr 13 2017 07:12:15 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=d0:39:b3:f8:ed:dd;CMTS-MAC=00:1b:54:c9:87:c7;CM-QOS=1.1;CM-VER=3.0; Apr 13 2017 07:11:45 3-Critical R06.0 Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=d0:39:b3:f8:ed:dd;CMTS-MAC=00:1b:54:c9:87:c7;CM-QOS=1.1;CM-VER=3.0; Apr 13 2017 07:11:45 3-Critical R03.0 Ranging Request Retries exhausted;CM-MAC=d0:39:b3:f8:ed:dd;CMTS-MAC=00:1b:54:c9:87:c7;CM-QOS=1.1;CM-VER=3.0; Apr 13 2017 07:11:30 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=d0:39:b3:f8:ed:dd;CMTS-MAC=00:1b:54:c9:87:c7;CM-QOS=1.1;CM-VER=3.0; Apr 13 2017 07:10:15 3-Critical R06.0 Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=d0:39:b3:f8:ed:dd;CMTS-MAC=00:1b:54:c9:87:c7;CM-QOS=1.1;CM-VER=3.0; Apr 13 2017 07:10:15 3-Critical R03.0 Ranging Request Retries exhausted;CM-MAC=d0:39:b3:f8:ed:dd;CMTS-MAC=00:1b:54:c9:87:c7;CM-QOS=1.1;CM-VER=3.0; Apr 13 2017 07:09:45 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=d0:39:b3:f8:ed:dd;CMTS-MAC=00:1b:54:c9:87:c7;CM-QOS=1.1;CM-VER=3.0; Apr 13 2017 06:56:33 3-Critical R06.0 Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=d0:39:b3:f8:ed:dd;CMTS-MAC=00:1b:54:c9:87:c7;CM-QOS=1.1;CM-VER=3.0; Apr 13 2017 06:56:33 3-Critical R03.0 Ranging Request Retries exhausted;CM-MAC=d0:39:b3:f8:ed:dd;CMTS-MAC=00:1b:54:c9:87:c7;CM-QOS=1.1;CM-VER=3.0; Apr 13 2017 06:56:18 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=d0:39:b3:f8:ed:dd;CMTS-MAC=00:1b:54:c9:87:c7;CM-QOS=1.1;CM-VER=3.0; Apr 13 2017 06:55:48 3-Critical R06.0 Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=d0:39:b3:f8:ed:dd;CMTS-MAC=00:1b:54:c9:87:c7;CM-QOS=1.1;CM-VER=3.0; Apr 13 2017 06:55:48 3-Critical R03.0 Ranging Request Retries exhausted;CM-MAC=d0:39:b3:f8:ed:dd;CMTS-MAC=00:1b:54:c9:87:c7;CM-QOS=1.1;CM-VER=3.0; Apr 13 2017 06:55:33 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=d0:39:b3:f8:ed:dd;CMTS-MAC=00:1b:54:c9:87:c7;CM-QOS=1.1;CM-VER=3.0; Apr 13 2017 06:54:18 3-Critical R06.0 Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=d0:39:b3:f8:ed:dd;CMTS-MAC=00:1b:54:c9:87:c7;CM-QOS=1.1;CM-VER=3.0; Apr 13 2017 06:54:18 3-Critical R03.0 Ranging Request Retries exhausted;CM-MAC=d0:39:b3:f8:ed:dd;CMTS-MAC=00:1b:54:c9:87:c7;CM-QOS=1.1;CM-VER=3.0; Apr 13 2017 06:53:48 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=d0:39:b3:f8:ed:dd;CMTS-MAC=00:1b:54:c9:87:c7;CM-QOS=1.1;CM-VER=3.0; Apr 13 2017 06:40:36 3-Critical R06.0 Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=d0:39:b3:f8:ed:dd;CMTS-MAC=00:1b:54:c9:87:c7;CM-QOS=1.1;CM-VER=3.0;
AZ_Internet_Use
8 years ago Place Archives
1.3KViews
0likes
1Comment
Modem Losing Channels, and dropping Internet
Hello, A friend and I would get major lag spikes on our modem. We have a technician coming out tomorrow to check on our setup, but just wondering if anyone else had a similar problem. We'd lose channel's 1 & 2 specifically. Currently running a line with splitter to modem and cable box. I'm wondering if the splitter is not the correct one - we purchased an Ideal 85-332 5mhz-2.3ghz. The setup has worked for 3-4 weeks with a stable connection. Great with the doubling of speeds but for the last week, these errors pop up. Signals seem alright just weird. Many Thanks, AQM Our Modem: Model Name: SB6141 Vendor Name: Motorola Firmware Name: SB_KOMODO-1.0.6.12-SCM00-NOSH Boot Version: PSPU-Boot(25CLK) 1.0.12.18m3 Hardware Version: 7.0 Serial Number: 348781312822624709020001 Firmware Build Time: Mar 12 2013 17:48:19 Time Priority Code Message Nov 03 2014 17:19:46 6-Notice I401.0 TLV-11 - unrecognized OID;CM-MAC=e8:6d:52:70:72:04;CMTS-MAC=64:00:f1:40:1d:75;CM-QOS=1.1;CM-VER=3.0; Nov 03 2014 17:19:46 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=e8:6d:52:70:72:04;CMTS-MAC=64:00:f1:40:1d:75;CM-QOS=1.1;CM-VER=3.0; Jan 01 1970 00:00:21 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=e8:6d:52:70:72:04;CMTS-MAC=64:00:f1:40:1d:75;CM-QOS=1.1;CM-VER=3.0; Jan 01 1970 00:00:15 6-Notice N/A Cable Modem Reboot from GUI/Configuration page ;CM-MAC=e8:6d:52:70:72:04;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0; Nov 03 2014 17:17:07 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=e8:6d:52:70:72:04;CMTS-MAC=64:00:f1:40:1d:75;CM-QOS=1.1;CM-VER=3.0; Nov 03 2014 17:17:07 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=e8:6d:52:70:72:04;CMTS-MAC=64:00:f1:40:1d:75;CM-QOS=1.1;CM-VER=3.0; Nov 03 2014 17:17:06 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=e8:6d:52:70:72:04;CMTS-MAC=64:00:f1:40:1d:75;CM-QOS=1.1;CM-VER=3.0; Nov 03 2014 17:17:06 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=e8:6d:52:70:72:04;CMTS-MAC=64:00:f1:40:1d:75;CM-QOS=1.1;CM-VER=3.0; Nov 03 2014 17:17:05 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=e8:6d:52:70:72:04;CMTS-MAC=64:00:f1:40:1d:75;CM-QOS=1.1;CM-VER=3.0; Nov 03 2014 17:17:05 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=e8:6d:52:70:72:04;CMTS-MAC=64:00:f1:40:1d:75;CM-QOS=1.1;CM-VER=3.0; Nov 03 2014 17:17:04 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=e8:6d:52:70:72:04;CMTS-MAC=64:00:f1:40:1d:75;CM-QOS=1.1;CM-VER=3.0; Nov 03 2014 17:17:04 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=e8:6d:52:70:72:04;CMTS-MAC=64:00:f1:40:1d:75;CM-QOS=1.1;CM-VER=3.0; Nov 03 2014 17:17:03 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=e8:6d:52:70:72:04;CMTS-MAC=64:00:f1:40:1d:75;CM-QOS=1.1;CM-VER=3.0; Nov 03 2014 17:17:03 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=e8:6d:52:70:72:04;CMTS-MAC=64:00:f1:40:1d:75;CM-QOS=1.1;CM-VER=3.0; Nov 03 2014 17:17:02 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=e8:6d:52:70:72:04;CMTS-MAC=64:00:f1:40:1d:75;CM-QOS=1.1;CM-VER=3.0; Nov 03 2014 17:17:02 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=e8:6d:52:70:72:04;CMTS-MAC=64:00:f1:40:1d:75;CM-QOS=1.1;CM-VER=3.0; Nov 03 2014 17:17:01 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=e8:6d:52:70:72:04;CMTS-MAC=64:00:f1:40:1d:75;CM-QOS=1.1;CM-VER=3.0; Nov 03 2014 17:17:01 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=e8:6d:52:70:72:04;CMTS-MAC=64:00:f1:40:1d:75;CM-QOS=1.1;CM-VER=3.0; Nov 03 2014 17:17:00 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=e8:6d:52:70:72:04;CMTS-MAC=64:00:f1:40:1d:75;CM-QOS=1.1;CM-VER=3.0; Nov 03 2014 17:17:00 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=e8:6d:52:70:72:04;CMTS-MAC=64:00:f1:40:1d:75;CM-QOS=1.1;CM-VER=3.0; Signal: Downstream Bonding Channel Value Channel ID 85 86 87 88 93 94 95 96 Frequency 801000000 Hz 807000000 Hz 813000000 Hz 819000000 Hz 849000000 Hz 855000000 Hz 861000000 Hz 867000000 Hz Signal to Noise Ratio 37 dB 37 dB 37 dB 37 dB 37 dB 38 dB 37 dB 37 dB Downstream Modulation QAM256 QAM256 QAM256 QAM256 QAM256 QAM256 QAM256 QAM256 Power Level -5 dBmV -5 dBmV -4 dBmV -5 dBmV -5 dBmV -5 dBmV -5 dBmV -5 dBmV Upstream Bonding Channel Value Channel ID 1 2 3 4 Frequency 37600000 Hz 31200000 Hz 25400000 Hz 22200000 Hz Ranging Service ID 51 51 51 51 Symbol Rate 5.120 Msym/sec 5.120 Msym/sec 2.560 Msym/sec 2.560 Msym/sec Power Level 47 dBmV 47 dBmV 45 dBmV 45 dBmV Upstream Modulation [3] 16QAM [3] 64QAM [3] 16QAM [3] 64QAM [3] QPSK [2] 16QAM [3] 64QAM [3] QPSK [2] 16QAM [3] 64QAM Ranging Status Success Success Success Success Signal Stats (Codewords) Bonding Channel Value Channel ID 85 86 87 88 93 94 95 96 Total Unerrored Codewords 59703871 58379022 58387743 58400024 58374229 58375495 58378802 58399947 Total Correctable Codewords 48 147 52 5 20 7 11 14 Total Uncorrectable Codewords 518 489 493 535 1526 1538 656 616
polychem124
11 years ago Place Archives
2.1KViews
0likes
1Comment
Internet Down - Modem Will Not Connect
I have a Motorola Surfboard (SBG6580) that is approximately one year old. Up until the last six months, it has worked perfectly. It has recently started dropping connections, causing problems with not only my personal life but my schooling as well. I've been unable to do anything online for three days and support hasn't been helpful. As I'm typing this, using my phone's tethered connection, my modem is attempting to connect. Normally, it's as simple as a quick call to Cox and a reset of the modem and I'm on my way. After the first two times, this has not been the case. I've hard reset it, performed a "30-30-30" reset, and also restored the router to factory settings via the user interface. All to no avail. I have noticed a few odd things in the logs though: Cox has grown increasingly frustrating over the last year or so and customer support's only advice is "get a new router". I refuse to believe that an immobile device with no moving parts just "dies". Especially with the problems I've had in the past with Cox. Any assistance is greatly appreciated.
Mikaela
11 years ago Place Archives
2.3KViews
0likes
0Comments