Connection Drops

22 Topics

Internet lag spikes daily
Looking for any cox tech that knows what they are talking about and can assist with a longstanding issue with my home internet. For months upon months I have been dealing with sporadic, daily inconsistent lag spikes. Connection will drop for any where between 10 secs to over a minute. This is becoming an ever increasing issue as my spouse and I work from home and interruptions like this cause all sorts of trouble for our work. Now before any misconceptions and hypothesis are formed let me go over what has been attempted thus far. I have gotten a new modem directly from cox as they claimed my previous modem was most likely the problem. The issue was back within hours of installation of the new modem. I have had techs come out to test for noise and ingress on the line. None were reported. I have had techs claim that they would escalate to the outside ground crews who are responsible for the nodes outside and have not heard back regarding any found issues. I have confirmed on the cox app that no service interrupts are occurring within my area. I have started keeping a log of disruptions which occur daily sometimes multiple occurrences in a day. I have been tracking the network with PingPlotter and have consistent errors at the following address 68.1.0.242 ( ashbbprj01-ae2.rd.as.cox.net ). I am convinced there is a greater issue occurring but I cannot seem to find the right person that can help or understands the issue. Is there anyone out there that have any feasible solutions?
ZeroTalon
4 days ago Place Internet
28Views
0likes
1Comment
Packet loss due to upstream channels dropping
I've been getting outages due to the upstream dropping out on my internet connection for more than 6 months now. Downloads, watching streams, podcasts, hearing and seeing people on voice/video calls and are fine if they've already started. Uploads drop, voice/video calls break up for listeners, website requests take forever, games get disconnected. Modem upstream during packet loss: Bottom row with red question marks is packet loss. Other rows are just hops which sometimes don't respond (`mtr one.one.one.one`): I can't even get a screenshot without packet loss over the past few hours. I've rebooted my modem. I have a new cable and connectors from the box outside directly to my modem 2 times over. I've upgraded my modem 2 times and now have one of the best (MG8702) if not the best one supported by Cox. I've had several techs out to troubleshoot the issue. Some of them have replaced the same cable or connector as previous techs have done. One tech actually worked on something up the street, which improved the connection dropping a little. Another of the techs said there wasn't really anything they could do to fix it and that the lines are over-saturated because everyone is working from home now. If this is actually a problem, it sounds like a case to expand infrastructure rather than telling me it's all used up. I've confirmed with the techs that have visited that there's an issue with the upstream signals somewhere between the box at the utility pole and further up the chain. It doesn't seem like this issue will every be fixed. I've burned a lot of my time (days and days), burned money upgrading hardware that was fine, talking with customer support, and waiting for techs. I've been having to use my phone as a mobile hot-spot to ensure a consistent connection for voice and video calls. If this keeps up I think I'm just going to stop wasting money on useless internet and dump Cox and switch to a mobile hot-spot, since I end doing that anyway.
Solved
A_Cox_Customer
4 years ago Place Internet
8KViews
0likes
31Comments
Disconnects Every 5m - 85615
https://drive.google.com/file/d/1W2-Yp__l8aZQr8X-OmnyaKSc_RN_33hl/view?usp=sharing Please see attached Connection Log. Something is wrong with my provisioning, or something with the way my modem is being programmed. I have traded out my modem THREE times. I have had Cox out to the house At least 3 times. I have spoken to an engineer. There is nothing wrong with the connection lines, there is nothing wrong with the modem. However, something is causing my modem to drop every 5 minutes, on the 1 and on the 6. It has been doing this for SIX WEEKS. If I have a computer plugged directly into the modem the network card had to reconnect to the modem as the connection completely drops every 5m. This is the THIRD Modem that does this. If I had any other options for High Speed Internet, I would be canceling my Internet and going with them. However, all the other options *** even more than Cox does. so I am stuck with a limp COX internet connection, in need to Internet Viagra. I have yet another tech coming out tomorrow, but all they are going to do is look at the lines, determine it's not a line problem, and then close the ticket. AGAIN. What does it take to get someone who has ownership of a problem and will see it through to the end?
ELF1024
5 years ago Place Internet
900Views
2likes
3Comments
Internet constantly dropping for the past week
Hello, My internet has been constantly dropping for the past couple of days, making it impossible for my parents to work from home and for my brother and I to connect to class zoom meetings for school. The problem started getting significantly worse a couple of days ago to the point where it is impossible to be connected for any reasonable amount of time. I decided to check the status and logs for my modem and it shows this. Any help is appreciated. Modem Model: ARRIS SURFboard SB8200 Status: Procedure Status Comment Acquire Downstream Channel 951000000 Hz Locked Connectivity State OK Operational Boot State OK Operational Configuration File OK Security Enabled BPI+ DOCSIS Network Access Enabled Allowed Downstream Bonded Channels Channel ID Lock Status Modulation Frequency Power SNR/MER Corrected Uncorrectables 29 Locked QAM256 951000000 Hz 6.4 dBmV 39.0 dB 105 382 1 Locked QAM256 783000000 Hz 6.1 dBmV 39.0 dB 200 591 2 Locked QAM256 789000000 Hz 6.2 dBmV 39.0 dB 159 655 3 Locked QAM256 795000000 Hz 6.2 dBmV 39.1 dB 191 516 4 Locked QAM256 801000000 Hz 5.9 dBmV 38.7 dB 182 570 5 Locked QAM256 807000000 Hz 5.6 dBmV 38.6 dB 149 468 6 Locked QAM256 813000000 Hz 5.3 dBmV 38.5 dB 195 553 7 Locked QAM256 819000000 Hz 4.8 dBmV 38.3 dB 194 498 8 Locked QAM256 825000000 Hz 5.0 dBmV 38.4 dB 206 521 9 Locked QAM256 831000000 Hz 5.2 dBmV 38.5 dB 185 521 10 Locked QAM256 837000000 Hz 5.5 dBmV 38.6 dB 184 503 11 Locked QAM256 843000000 Hz 5.4 dBmV 38.6 dB 194 417 12 Locked QAM256 849000000 Hz 5.4 dBmV 38.6 dB 149 399 13 Locked QAM256 855000000 Hz 5.6 dBmV 38.8 dB 198 454 14 Locked QAM256 861000000 Hz 5.8 dBmV 38.7 dB 164 399 15 Locked QAM256 867000000 Hz 5.6 dBmV 38.8 dB 118 444 16 Locked QAM256 873000000 Hz 6.0 dBmV 38.9 dB 171 418 17 Locked QAM256 879000000 Hz 6.1 dBmV 39.0 dB 116 419 18 Locked QAM256 885000000 Hz 6.3 dBmV 39.0 dB 116 477 19 Locked QAM256 891000000 Hz 6.2 dBmV 38.9 dB 120 401 20 Locked QAM256 897000000 Hz 6.4 dBmV 38.9 dB 164 503 21 Locked QAM256 903000000 Hz 6.4 dBmV 38.9 dB 112 387 22 Locked QAM256 909000000 Hz 6.5 dBmV 39.1 dB 114 425 23 Locked QAM256 915000000 Hz 6.2 dBmV 38.9 dB 71 390 24 Locked QAM256 921000000 Hz 6.4 dBmV 39.1 dB 100 422 25 Locked QAM256 927000000 Hz 6.3 dBmV 39.0 dB 94 384 26 Locked QAM256 933000000 Hz 6.6 dBmV 39.1 dB 99 402 27 Locked QAM256 939000000 Hz 6.7 dBmV 39.2 dB 86 370 28 Locked QAM256 945000000 Hz 6.8 dBmV 39.3 dB 117 413 30 Locked QAM256 957000000 Hz 6.1 dBmV 39.0 dB 80 447 31 Locked QAM256 963000000 Hz 6.0 dBmV 38.9 dB 91 386 32 Locked QAM256 969000000 Hz 5.8 dBmV 38.7 dB 111 442 159 Locked Other 300000000 Hz 10.5 dBmV 0.0 dB 376365871 4356 Upstream Bonded Channels Channel Channel ID Lock Status US Channel Type Frequency Width Power 1 6 Locked SC-QAM Upstream 14600000 Hz 3200000 Hz 37.0 dBmV 2 1 Locked SC-QAM Upstream 19400000 Hz 6400000 Hz 43.0 dBmV 3 2 Locked SC-QAM Upstream 25800000 Hz 6400000 Hz 37.0 dBmV 4 3 Locked SC-QAM Upstream 32200000 Hz 6400000 Hz 41.0 dBmV 5 4 Locked SC-QAM Upstream 38600000 Hz 6400000 Hz 38.0 dBmV Logs: Date Time Event ID Event Level Description 07/30/2020 22:25 2436694061 5 "Dynamic Range Window violation" 07/30/2020 22:25 82001100 5 "RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=18:9c:27:fb:50:21;CMTS-MAC=00:59:dc:79:0a:3c;CM-QOS=1.1;CM-VER=3.1;" 07/30/2020 22:05 2436694061 5 "Dynamic Range Window violation" 07/30/2020 22:05 82001100 5 "RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=18:9c:27:fb:50:21;CMTS-MAC=00:59:dc:79:0a:3c;CM-QOS=1.1;CM-VER=3.1;" 07/30/2020 22:05 2436694061 5 "Dynamic Range Window violation" 07/30/2020 22:05 82001100 5 "RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=18:9c:27:fb:50:21;CMTS-MAC=00:59:dc:79:0a:3c;CM-QOS=1.1;CM-VER=3.1;" 07/30/2020 22:04 2436694061 5 "Dynamic Range Window violation" 07/30/2020 22:04 82001200 5 "RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=18:9c:27:fb:50:21;CMTS-MAC=00:59:dc:79:0a:3c;CM-QOS=1.1;CM-VER=3.1;" 07/30/2020 22:04 2436694061 5 "Dynamic Range Window violation" 07/30/2020 22:04 82001200 5 "RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=18:9c:27:fb:50:21;CMTS-MAC=00:59:dc:79:0a:3c;CM-QOS=1.1;CM-VER=3.1;" 07/30/2020 22:04 2436694061 5 "Dynamic Range Window violation" 07/30/2020 22:04 82001200 5 "RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=18:9c:27:fb:50:21;CMTS-MAC=00:59:dc:79:0a:3c;CM-QOS=1.1;CM-VER=3.1;" 07/30/2020 22:04 2436694061 5 "Dynamic Range Window violation" 07/30/2020 22:04 82001200 5 "RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=18:9c:27:fb:50:21;CMTS-MAC=00:59:dc:79:0a:3c;CM-QOS=1.1;CM-VER=3.1;" 07/30/2020 22:03 74010100 6 "CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2.;CM-MAC=18:9c:27:fb:50:21;CMTS-MAC=00:59:dc:79:0a:3c;CM-QOS=1.1;CM-VER=3.1;" 07/30/2020 22:03 2436694061 5 "Dynamic Range Window violation" 07/30/2020 22:03 82001100 5 "RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=18:9c:27:fb:50:21;CMTS-MAC=00:59:dc:79:0a:3c;CM-QOS=1.1;CM-VER=3.1;" 07/30/2020 22:03 2436694061 5 "Dynamic Range Window violation" 07/30/2020 22:03 82001100 5 "RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=18:9c:27:fb:50:21;CMTS-MAC=00:59:dc:79:0a:3c;CM-QOS=1.1;CM-VER=3.1;" 07/30/2020 22:03 2436694061 5 "Dynamic Range Window violation" 07/30/2020 22:03 82001100 5 "RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=18:9c:27:fb:50:21;CMTS-MAC=00:59:dc:79:0a:3c;CM-QOS=1.1;CM-VER=3.1;" 07/30/2020 22:03 82000500 3 "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=18:9c:27:fb:50:21;CMTS-MAC=00:59:dc:79:0a:3c;CM-QOS=1.1;CM-VER=3.1;" 07/30/2020 22:02 74010100 6 "CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2.;CM-MAC=18:9c:27:fb:50:21;CMTS-MAC=00:59:dc:79:0a:3c;CM-QOS=1.1;CM-VER=3.1;" 07/30/2020 22:02 2436694061 5 "Dynamic Range Window violation" 07/30/2020 22:02 82001200 5 "RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=18:9c:27:fb:50:21;CMTS-MAC=00:59:dc:79:0a:3c;CM-QOS=1.1;CM-VER=3.1;" 07/30/2020 22:02 2436694061 5 "Dynamic Range Window violation" 07/30/2020 22:02 82001200 5 "RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=18:9c:27:fb:50:21;CMTS-MAC=00:59:dc:79:0a:3c;CM-QOS=1.1;CM-VER=3.1;" 07/30/2020 22:02 2436694061 5 "Dynamic Range Window violation" 07/30/2020 22:02 82001200 5 "RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=18:9c:27:fb:50:21;CMTS-MAC=00:59:dc:79:0a:3c;CM-QOS=1.1;CM-VER=3.1;" 07/30/2020 21:50 2436694061 5 "Dynamic Range Window violation" 07/30/2020 21:50 82001200 5 "RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=18:9c:27:fb:50:21;CMTS-MAC=00:59:dc:79:0a:3c;CM-QOS=1.1;CM-VER=3.1;" 07/30/2020 21:50 2436694061 5 "Dynamic Range Window violation" 07/30/2020 21:50 82001200 5 "RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=18:9c:27:fb:50:21;CMTS-MAC=00:59:dc:79:0a:3c;CM-QOS=1.1;CM-VER=3.1;" 07/30/2020 21:50 2436694061 5 "Dynamic Range Window violation" 07/30/2020 21:50 82001200 5 "RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=18:9c:27:fb:50:21;CMTS-MAC=00:59:dc:79:0a:3c;CM-QOS=1.1;CM-VER=3.1;" 07/30/2020 21:49 2436694061 5 "Dynamic Range Window violation" 07/30/2020 21:49 82001100 5 "RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=18:9c:27:fb:50:21;CMTS-MAC=00:59:dc:79:0a:3c;CM-QOS=1.1;CM-VER=3.1;" 07/30/2020 21:49 2436694061 5 "Dynamic Range Window violation" 07/30/2020 21:49 82001100 5 "RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=18:9c:27:fb:50:21;CMTS-MAC=00:59:dc:79:0a:3c;CM-QOS=1.1;CM-VER=3.1;" 07/30/2020 21:49 2436694061 5 "Dynamic Range Window violation" 07/30/2020 21:49 82001100 5 "RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=18:9c:27:fb:50:21;CMTS-MAC=00:59:dc:79:0a:3c;CM-QOS=1.1;CM-VER=3.1;" 07/30/2020 21:49 2436694061 5 "Dynamic Range Window violation" 07/30/2020 21:49 82001100 5 "RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=18:9c:27:fb:50:21;CMTS-MAC=00:59:dc:79:0a:3c;CM-QOS=1.1;CM-VER=3.1;" 07/30/2020 21:45 74010100 6 "CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=18:9c:27:fb:50:21;CMTS-MAC=00:59:dc:79:0a:3c;CM-QOS=1.1;CM-VER=3.1;" 07/30/2020 21:45 74010100 6 "CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=18:9c:27:fb:50:21;CMTS-MAC=00:59:dc:79:0a:3c;CM-QOS=1.1;CM-VER=3.1;" 07/30/2020 21:40 74010100 6 "CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=18:9c:27:fb:50:21;CMTS-MAC=00:59:dc:79:0a:3c;CM-QOS=1.1;CM-VER=3.1;" 07/30/2020 21:40 74010100 6 "CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=18:9c:27:fb:50:21;CMTS-MAC=00:59:dc:79:0a:3c;CM-QOS=1.1;CM-VER=3.1;" 07/30/2020 21:36 2436694061 5 "Dynamic Range Window violation" 07/30/2020 21:36 82001100 5 "RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=18:9c:27:fb:50:21;CMTS-MAC=00:59:dc:79:0a:3c;CM-QOS=1.1;CM-VER=3.1;" 07/30/2020 21:35 2436694061 5 "Dynamic Range Window violation" If anyone has any insights or solutions to this problem, it would be greatly appreciated. Sorry for the long post and thanks for reading.
Viole
5 years ago Place Internet
289Views
0likes
0Comments
Network disconnection
Almost daily there is a drop in both wired and wireless connections and this has been the “as per usual”from Cox with every single reply of “ It must be your equipment” and then they would claim firmware updates or that the line has feedback from another uncapped line outside my property. Has anyone else had this same issue? Each time I formally complain at the customer care . I have the gigablast and panoramic wifi
ChrisSony
6 years ago Place Internet
897Views
0likes
2Comments
Internet Connection Keeps Dropping/Resetting
Hello from the Phoenix Area, I've been fighting with support for over a month now to get my service stabilized. I'm expecting my 3rd Tech Visit tomorrow, which is supposed to be a Supervisor Technician. I've been calling and tracking the outages. I'm getting between 10-15 disconnects a day. Some lasting up to 2 hours. I've only had service for 7 weeks now with a brand new out of the box modem, which I've already replaced with another brand new out of the box modem. Both having the same issues. The cable has been tested and checked and new connectors put on the ends twice. We've moved the connection to a different node. Still getting dropped internet. This happens throughout the day. It doesn't seem to matter the time, amount of internet traffic, or possible other usage related issues. It'll drop at 2am or 2pm or any other time in between either way. I'm getting charged $75 for each tech visit to come in and "redo my cabling" (ie put new connectors on) and I'd gladly pay for the first tech trip if it would have fixed the issue. However, it hasn't and I'm on my 3rd tech trip now. My Meraki Router is showing outages coinciding with the critical errors in the event log with the record going all the way back to July 31st. During the busy hours (Evenings 5pm to Midnight) latency will jump 20-25ms to 35-50ms, dropped packets will go from 0-3% to varying between 10-50%. This is consistent every evening. I've had to contact support, insist on speaking to a manager (Which BTW none one wants to let you talk to), and demand escalated service because it's been weeks of "Reset you modem, check to make sure your connections are tight, look we reset your modem it's working now...." and getting nothing fixed. How does COX expect to retain customers if they can't provide the service that we are paying for? Hopefully we can bring this to a resolution before decide it's not work dealing with COX anymore and switch to a different ISP. Just know, if I switch at home, so to will I switch at work where we have over 60+ retail locations in the Metro Phoenix and surrounding areas. COX isn't the only ISP in town and customer service should remember that Business Users are made up of Home Users. Piss off the wrong home user and you lose a lot of business overnight. And yes I'm venting because I'm at the end of my patience. Anyways, here's the pertinent information below concerning my modem, router, errors, connection stats, etc. Current Hardware Arris SB6183 Modem Meraki MX64 Router Current Status Log Startup Procedure Procedure Status Comment Acquire Downstream Channel Locked Connectivity State OK Operational Boot State OK Operational Configuration File OK Security Enabled BPI+ DOCSIS Network Access Enabled Allowed Downstream Bonded Channels Channel Lock Status Modulation Channel ID Frequency Power SNR Corrected Uncorrectables 1 Locked QAM256 2 789000000 Hz -5.8 dBmV 37.6 dB 680 673 2 Locked QAM256 1 783000000 Hz -5.6 dBmV 37.6 dB 598 453 3 Locked QAM256 3 795000000 Hz -5.5 dBmV 37.7 dB 670 756 4 Locked QAM256 4 801000000 Hz -5.9 dBmV 37.5 dB 496 691 5 Locked QAM256 5 807000000 Hz -6.6 dBmV 37.2 dB 596 341 6 Locked QAM256 6 813000000 Hz -7.0 dBmV 37.1 dB 708 568 7 Locked QAM256 7 819000000 Hz -6.9 dBmV 37.1 dB 650 743 8 Locked QAM256 8 825000000 Hz -6.7 dBmV 37.2 dB 457 720 9 Locked QAM256 17 879000000 Hz -7.0 dBmV 37.1 dB 459 448 10 Locked QAM256 18 885000000 Hz -7.9 dBmV 36.6 dB 468 549 11 Locked QAM256 19 891000000 Hz -8.2 dBmV 36.4 dB 625 609 12 Locked QAM256 20 897000000 Hz -8.2 dBmV 36.5 dB 547 762 13 Locked QAM256 21 903000000 Hz -8.6 dBmV 36.4 dB 612 678 14 Locked QAM256 22 909000000 Hz -8.6 dBmV 36.3 dB 2783 640 15 Locked QAM256 23 915000000 Hz -8.4 dBmV 36.3 dB 3684 939 16 Locked QAM256 24 921000000 Hz -8.3 dBmV 36.3 dB 766 556 Upstream Bonded Channels Channel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power 1 Locked ATDMA 2 5120 Ksym/sec 23300000 Hz 44.0 dBmV 2 Locked ATDMA 1 2560 Ksym/sec 18400000 Hz 43.8 dBmV 3 Locked ATDMA 3 5120 Ksym/sec 29800000 Hz 47.0 dBmV 4 Locked ATDMA 4 5120 Ksym/sec 36300000 Hz 47.3 dBmV Current System Time: Mon Aug 06 19:23:08 2018 Current Modem Event Log Time Priority Description Mon Aug 06 14:40:02 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Mon Aug 06 13:15:01 2018 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Mon Aug 06 13:14:13 2018 Notice (6) TLV-11 - unrecognized OID;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Time Not Established Warning (5) DHCP WARNING - Non-critical field invalid in response ;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.0;CM-VER=3.0; Time Not Established Notice (6) Honoring MDD; IP provisioning mode = IPv4 Time Not Established Critical (3) No Ranging Response received - T3 time-out Mon Aug 06 13:13:25 2018 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Mon Aug 06 13:11:15 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Mon Aug 06 12:41:48 2018 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Time Not Established Critical (3) No Ranging Response received - T3 time-out Mon Aug 06 12:40:04 2018 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Mon Aug 06 12:37:56 2018 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Mon Aug 06 12:37:54 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Mon Aug 06 12:26:34 2018 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Time Not Established Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.0;CM-VER=3.0; Time Not Established Critical (3) No Ranging Response received - T3 time-out Mon Aug 06 12:24:55 2018 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Mon Aug 06 12:22:45 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Mon Aug 06 12:22:45 2018 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Mon Aug 06 12:22:44 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Mon Aug 06 11:12:47 2018 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Time Not Established Critical (3) No Ranging Response received - T3 time-out Mon Aug 06 11:10:31 2018 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Mon Aug 06 11:08:21 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Mon Aug 06 10:54:45 2018 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Time Not Established Critical (3) No Ranging Response received - T3 time-out Mon Aug 06 10:53:01 2018 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Mon Aug 06 10:50:50 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Mon Aug 06 04:53:55 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Mon Aug 06 04:08:31 2018 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Time Not Established Critical (3) No Ranging Response received - T3 time-out Mon Aug 06 04:06:43 2018 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Mon Aug 06 04:04:33 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Mon Aug 06 00:30:05 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Mon Aug 06 00:28:55 2018 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Mon Aug 06 00:28:55 2018 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Mon Aug 06 00:28:55 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Mon Aug 06 00:17:48 2018 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Time Not Established Critical (3) No Ranging Response received - T3 time-out Time Not Established Critical (3) No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.0;CM-VER=3.0; Time Not Established Critical (3) No Ranging Response received - T3 time-out Time Not Established Critical (3) No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.0;CM-VER=3.0; Time Not Established Critical (3) No Ranging Response received - T3 time-out Mon Aug 06 00:15:24 2018 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Mon Aug 06 00:13:14 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Sun Aug 05 23:46:29 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Sun Aug 05 21:58:50 2018 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Time Not Established Critical (3) No Ranging Response received - T3 time-out Sun Aug 05 21:56:58 2018 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Sun Aug 05 21:54:48 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Sun Aug 05 12:09:11 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Sun Aug 05 04:34:23 2018 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Time Not Established Critical (3) No Ranging Response received - T3 time-out Sun Aug 05 04:32:33 2018 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Sun Aug 05 04:30:23 2018 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Sun Aug 05 04:30:23 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Sun Aug 05 04:29:39 2018 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Sun Aug 05 00:21:47 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Sat Aug 04 23:51:02 2018 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Time Not Established Critical (3) No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.0;CM-VER=3.0; Time Not Established Critical (3) No Ranging Response received - T3 time-out Sat Aug 04 23:49:06 2018 Critical (3) Resetting the cable modem due to docsDevResetNow Sat Aug 04 23:42:46 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Sat Aug 04 23:37:26 2018 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Time Not Established Critical (3) No Ranging Response received - T3 time-out Time Not Established Critical (3) No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.0;CM-VER=3.0; Time Not Established Critical (3) No Ranging Response received - T3 time-out Sat Aug 04 23:35:13 2018 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Sat Aug 04 23:33:34 2018 Critical (3) SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Sat Aug 04 23:33:03 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Sat Aug 04 22:20:15 2018 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Time Not Established Critical (3) No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.0;CM-VER=3.0; Time Not Established Critical (3) No Ranging Response received - T3 time-out Sat Aug 04 22:18:20 2018 Critical (3) Resetting the cable modem due to docsDevResetNow Sat Aug 04 22:10:12 2018 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Time Not Established Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.0;CM-VER=3.0; Time Not Established Critical (3) No Ranging Response received - T3 time-out Sat Aug 04 22:08:18 2018 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Sat Aug 04 22:06:08 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Sat Aug 04 22:05:41 2018 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Sat Aug 04 22:05:41 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Sat Aug 04 21:51:53 2018 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Time Not Established Critical (3) No Ranging Response received - T3 time-out Sat Aug 04 21:50:07 2018 Critical (3) Resetting the cable modem due to docsDevResetNow Time Not Established Critical (3) No Ranging Response received - T3 time-out Sat Aug 04 21:48:32 2018 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Sat Aug 04 21:46:22 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Sat Aug 04 21:46:20 2018 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Sat Aug 04 21:46:19 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Sat Aug 04 21:45:59 2018 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Sat Aug 04 21:45:58 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Sat Aug 04 21:45:47 2018 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Sat Aug 04 21:45:30 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Sat Aug 04 21:45:26 2018 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Sat Aug 04 21:37:31 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Sat Aug 04 15:56:03 2018 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Time Not Established Critical (3) No Ranging Response received - T3 time-out Sat Aug 04 15:54:07 2018 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Sat Aug 04 15:51:57 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Sat Aug 04 15:16:36 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0;
Naulite
7 years ago Place Internet
2.4KViews
0likes
2Comments
Constant T3 time-outs & connection drops even after replaced gateway 3x
I am having constant connection drops, over the last several weeks, with constant T3 time-out errors in the gateway logs. I have replaced the modem/router twice (once with an older one that I still had on hand, and then with a brand new gateway Surfboard SBG6782-AC) for a total of 3 different gateways. The IPs have been reset multiple times, after disconnecting the gateway overnight, and after the equipment changes. I have also had the signal reset 4 or 5 times. The connection drops for anywhere from a few seconds, to 10 minutes or so at a time. Usually, it returns on its own, but sometimes, I have to restart the gateway to get it back. It is extremely disruptive to my productivity. When the connection is stable, I have excellent speed according to speedtesting (50+mps) but I do not feel the benefits of this because of the constant timing out. I am seeing the connection drop every few minutes, making it impossible to do anything online. I have connected the gateway to a cable outlet in a different room, to make sure that the problem was not with the individual connector. The problem actually seemed worse in the other room. I have no TVs connected to any cable outlets at all, as I am not paying for TV service. I still got constant T3 time-out errors in the gateway logs. I have a desktop connected to the gateway by ethernet, a laptop and ipad connected by wifi. I have tested disconnecting each of these devices and using one at a time, to see if I can isolate the problem to a particular device, but there is no change. The connection still drops constantly. Here is a a screenshot of my gateway connection results http://screencast.com/t/QjFjT2AMMkq Here is a screenshot with a sample of my most recent event log. http://screencast.com/t/xcGJah8Z2lk6 Any idea what could be going on here? I have googled this problem until my eyes bleed, but I can't find a solution. Do I need to have a technician out?
jdee
9 years ago Place Archives
1.4KViews
0likes
1Comment
Awful through-put
Is there a reason why my through-put drops to ZERO three or four times each hour? Is there a way for Cox to monitor and hopefully correct this?
Solved
skitchead
12 years ago Place Archives
4.7KViews
0likes
10Comments
terrible signal strength and loss of connection
I use a Motorola SB6121 for a cable modem and airport extreme for wireless router. The motorola is 5 months old. For about ten days we experienced wide variations in wireless connectivity, from .5 mps download to 30 mps. This was entirely new after 5 months of cox internet service working great. I spoke with COX and they checked signal strength on live, walked me through a series of reboots of modem and router. They checked the signal on their end. They said it was not a problem on their end. I spoke with motorola and they walked me through a series of diagnostics and resets of their modem. The signal via a direct Ethernet cable from the modem to the computer worked great at that time. I spoke with Apple and they ran me through diagnostics and finally replaced by airport extreme (it was under warranty). Results: 1. When I first hooked up the router and the cable modem after the router was replaced, I had a great signal -- 32 mps, which is as good as it gets here. 2. 4 hours later the connection dropped and then became very slow. 3. I plugged the cable modem directly into my computer and got a full signal. I left it oversight doing an offline backup. 4. The connection was lost during the night with a direct hookup to the cable modem. It seems the problem is clearly not the modem or the router but something in the cox system, as none of these pieces of equipment causes the problem. They are new equipment. What shall I do?
Solved
Mark_L_
12 years ago Place Archives
3.8KViews
0likes
2Comments
Internet shuts off at least 5 times a week
As stated our internet shuts off a lot, sometimes 5 times in a day. Once we restart the modem and router the connection reestablishes itself. We have a Motorola Surfboard SB6141 modem and a Medialink Wireless-N router. Thanks for any help.
aphendri
12 years ago Place Archives
5.9KViews
0likes
12Comments