T3 and T4 Timeouts from an ex-field technician
Starting in September of 2013, I noticed my connection becoming intermittent at best. Voice conferencing and gaming would literally go from 23 ms to over 10k ms and then obviously I would disconnect from the server. About a week after this first started happening, it started to randomly disconnect while I was simply browsing the internet. I found the modem was cycling itself. At the time I had an extremely old but trusty Motorola Surfboard SB5100. Despite having this modem throughout the DOCSIS 3.0 updates, and despite it having worked fine through it all hither to the point in time, I figured it may be the modem (after a 12 year run, I wasn't complaining...) I accessed the modem diagnostic page at 192.168.100.1 and saw that in the logs there were massive amounts of T3 timeouts. Being an ex-field technician for Cox, I knew this could have gone one of two ways. It was either the modem or it was something in the node (most likely an amplifier in the trunk line) that was to blame. I called Cox for the heck of it just to see if they could see anything on their end, and as usual, no. Everything on their end was fine, but again, having been a field tech for 5 years, I know that phone based customer service is very limited, they're not at the house, they don't have a meter and they're sure as heck not taking level readings. Ok, fair enough. I purchased a Motorola Surfboard SB6141 to replace the 5100 and finally upgrade to DOCSIS 3.0. I called them, had the modem provisioned, went to the diagnostics page, was "wowed" by 8 downstream and 4 upstream channels, wondering why I had not upgraded the modem sooner, but alas, not 2 hours after provisioning, there was a T3 timeout. Now I know it's not the modem, time to get on the phone and make things happen. I called, they said they would send a tech out. The tech (CONTRACTOR) came out and I explained the whole situation to him. I showed him the modem diagnostics, I explained what I knew about everything, and he agreed with me. He did NOT check levels, he did NOT check the tap at the pole (I have a 340 foot drop from the pole to the house, it's RG-11. A new install was done less than a year ago, including the drop and inside lines, and I told him this, so he probably "assumed" things were good up there...). He scheduled a 5C, which is the "internal" code name for "get a maintenance (plant) technician out to the pole to see what's up". I got a call from my old lead technician about a week later. He told me that the maintenance tech found water in the drop and cut it back to where the "stinger" (copper in the connector) wasn't black from water damage, and that another tech would be out in the next day or two in order to run a new drop. Two days later ANOTHER CONTRACTOR comes to the house to run the new drop. I saw his spool of RG-11 and I knew he didn't have enough left to get from the pole to the house. He removed the drop at the sub pole, and due to not wanting to bother him, I came back inside. 20 minutes later I went back out and he was gone. He never replaced the drop. He probably figured he didn't have enough cable to do it after removing the drop at the sub pole, rehung it, and left. This pissed me off. In the meantime I contacted my old lead and asked him what the deal was, explaining that not only were these T3's still happening, but they were getting worse, and they were leading into T4's. He scheduled for the drop to be re-run AGAIN the next week and made sure it would be an in house guy arriving, NOT a contractor. Sure enough, another lead technician and a field tech came to the house and ran a new drop. They didn't have enough RG-11 so they ran half RG-11, then installed a ground block at the sub pole and ran RG-6 the rest of the way. He said he would be back (this was a month ago and it still hasn't happened) to replace the RG-6 half of the drop with RG-11. He gave me his cell number to contact directly if this kept going on. It kept going on. The T3's were getting worse. I asked him on the phone to set up a 5C, he said he would but this was a week and a half after he replaced the drop and hadn't been out to finish the RG-11, so my faith in relying on him was null. I therefore called customer service. I explained that, despite having JUST bought a new modem, FIOS was a phone call away if this wasn't resolved. Per usual, they went RIGHT back to square one and wanted to send out a tech. I told them to stop reading the script from their screen and focus on their keyboard in order to LISTEN AND UNDERSTAND exactly what I had JUST explained to them. For over a month I was implying that this was a plant issue, no one wanted to listen. The phone techs didn't want to listen, the lead techs did not want to listen, the lead techs kept coming back with 50 other excuses as to what could be causing it. I questioned them as to why they would do this when they knew I used to be a tech and I wasn't an idiot. The final call was made to customer service. Again, they said they had to send a tech out, despite two months of this **, in order to get a 5C scheduled. Ok, last time I am playing this game. The tech came out and I caught him on my way home from work. He was an in house guy and I caught him as he was at the pole taking levels. He told me that every port from the tap was bonkers, he replaced the tap and the levels were STILL bonkers, and that he did not understand how two lead techs and four field techs didn't realize this was a plant issue from day one. I concurred. He took down every piece of information I gave him about the new drop, the new modem, signal levels at the modem, etc, etc, and made a detailed log for the maintenance techs who came out. He also told me that there are only SIX HOUSES ON MY NODE, LITERALLY. This means that the trunk line feeding my house only feeds a total of 6 houses. Do you know how easy that is for plant (maintenance) to troubleshoot? There is one amplifier that is literally humping my tap, if here's an inch of trunk line from the amplifier into the tap then it's a lot. I suspected that amplifier from the get go, but even if it wasn't, there would only be at most ONE MORE amplifier in that node, so yeah, one amp checked out good, guess which one's bad? Real easy stuff here people, real easy. So, the tech scheduled the 5C (the second one that had to happen in this whole fiasco), and the maintenance tech came out. I don't know if it was the same or a different one, but this time around (after TWO MONTHS OF THIS **) the problem was resolved. It has been two weeks and I have not seen a single T3 or T4 in my log. I see where it lost connection due to the maintenance guy doing what he had to do and of course the service gets interrupted during this, but honestly, after the modem cycle, there is not ONE added entry to the log, nothing; whereas every other "visit" would result in a T3 less than 10 minutes later. These T3 (and later T4's due to the issue getting progressively worse) were happening every ten to twenty minutes on some days, other days every hour or so. I use VOIP for telephone. Imagine not having 911 access for the whole day because your ISP can't get it's act together. I held out having FIOS reinstalled (it was installed here when it first came out) because I honestly can't stand those hacks. Having said that, had that last tech not been so thorough, had the second maintenance tech not done his job and resolved the issue, Verizon was seriously the next phone call. I didn't go into a whole lot of detail about levels and diagnostics here because I did enough of that with customer service and all the techs that visited. I wanted to make a point here to Cox. Not all customers are complete idiots. Not all customers have zero clue about how information travels from their house to the MTC. Maybe instead of treating everyone equally as morons, you should start treating them all equally as intelligent folk. Imagine how many folks out there were never field techs, imagine how many would have switched back to Verizon within the first week, let alone sticking it out for two months. I was a field tech, I have working knowledge of the system, I was treated like a complete idiot, how do you think that makes me feel? It actually makes me feel pretty damned good right about now knowing I was right the whole damned time about the issue being a plant related occurrence, but I can tell you right now when these people tell you over the phone and face to face that you're "wrong", and that they need to go through steps that, again as an ex-tech, you KNOW they don't need to go through, all the while the internet that we pay for monthly and (in some cases) our phone service (through another provider in my instance) has fallen to complete useless garbage, labeling it as "infuriating" somehow undermines the true nature of it. I know that not every single problem faced is one of a plant issue, this is obvious. Red flags should be raised, however, after every single other step has been taken and fails, instead of attempting to loop the same damned process all over again; that is simply ridiculous. What is also ridiculous is the fact that contractors are being sent in place of in house technicians and basically this leads to repeat trouble calls. This is something that is completely unacceptable, especially when one has to take time out of their day (or out of work) every time a call has to be rescheduled. I know not every contractor is a bad contractor, but out of the entire bunch, I can name 3 that I would have work at my house, that's about it. To make it relative to the in house technicians, I can list about 20 off the top of my head that I would let work at my house from start to finish with a cable job any day of the year. I hope this type of issue, or at least the steps to the resolution of this type of problem does not happen again. I will definitely be more prone to calling Verizon early on if an issue is not resolved in a suitable amount of time, not TWO MONTHS AFTER.46KViews4likes2Comments
Configuring modem/router to modem only
I am hoping someone can help point me in the right direction. I have a Netgear C3700 DOCSIS 3.0 Wi-Fi modem/router which I currently have configured to provide my home access to the Internet. However I've recently purchased a new router (D-Link DIR-837) to use to hopefully improve/extend my Wi-Fi and Internet capabilities. I tried setting up the new router per the instructions but am getting no internet connection. Reading the modem/router manual I noticed it suggested disabling the router (NAT) mode to enable bridging however once that setting was enabled I lost all Internet connectivity through my Netgear C3700. Is there a setting/step I'm missing here that would allow me to use a separate router and my Netgear C3700 as the modem only? Any help/suggestions are greatly appreciated.15KViews0likes3Comments
Bursts of Packet Loss at night.
So lately, since school has ended, I have been staying up late and starting yesterday night, I seem to be incuring bursts of packet loss at night. It starts around 8ish 9ish at night and I really don't know when it stops. I woke up at 11:00 today and the issue was resolved. But alas tonight it was back at it. pingtest.net doesn't show any packet loss, but there is a test that is located here:http://netalyzr.icsi.berkeley.edu/ and here are the results: http://n1.netalyzr.icsi.berkeley.edu/summary/id=369839a0-1631-fa163b10-fab2-48d9-9aed#latency Whats this affecting? My game, I play a MOBA named League of Legends, and randomly in fights I my champion would continue to do what I have told it to do before the lag spike, and I can see everyone moving live, the only thing I can't do is input commands. Its like a burst of upload packet loss. It's really annoying and the only response I got from calling cox was "Hey man, if it isn't fixed by the morning, I guess it's time to find a new game". Here is the network logs parsed into a graph from the game.http://logsoflag.com/#YEYavpgkVEq My friends have also noted that my voice cuts out in skype when the packet loss occurs, but there voices are still clear. What have I tried? Disabled the wifi on the modem in case it was someone watching netflix or something. Restarted modem/router/wifi box all-in-one MULTIPLE times. Checked the wire all the way to the wall. Tried multiple computers. Others with cox in the area not experiencing (within 10 miles of me). This issue appears to only occur at night, I surely hope this problem can be resolved and I won't be ignored :( Signal Test: Pinging 8.8.8.8 for 4 minutes Now Pingtest is showing packet loss: And now its not.. I don't understand whats going on : Even when I am getting an A from Pingtest, I am still getting dropped packets in-game. And here it is at 2:00AM with minimum packet loss. Its so random... Ugh :(http://logsoflag.com/#fV2fqFwFGeA 4:00AM here are game logs:http://logsoflag.com/#Jm0ow9OQB7j I can't reliably play my game anymore, idk if I am going to have packet loss or not.14KViews0likes24CommentsPacket loss correlating with massive jump of Uncorrectable codewords
This issue started about a week ago. I noticed weird dropouts/lag bursts and then saw a crazy high number of uncorrectable codewords in the SB6183 (modem) status page. So I beganactivelymonitoring to document the issue (screenshots below). Should I schedule a technician now or ride out the storm? I am currently on the Ultimate internet plan with theCox Service Protection Plan. Before After Packet Loss13KViews0likes28Comments
High downstream and upstream power levels
I have seen post about high downstream and high upstream power levels but not at the same time. It seems to always be that only one of the levels is high and the other is low. I am having both high at the same time. Here are my normal readings. Downstream is normally around 8 to 9 dBmV Upstream is normally around 53 to 54 dBmV What could case both to be high at the same time? I am asking because I am having problems with online gaming. Server kicks, lag, ect. Thanks12KViews0likes8Comments
New Construction Install Request
How can I get someone out to my address to verify that the equipment in my yard is in fact a Cox pedestal so we can get service at our new home? I've been trying for weeks to get someone out here but everyone that I have spoken with acts dumbfounded. I was in the industry for 12 years in Kansas City and when someone had the same situation that I currently have, I would have a technician out at that address to look at it and 9 times out of 10 we had them built in the billing system and services installed in less than 24 hours. Since I've started this process, I have been forced to go with Dish (shame on you Cox) and we are using our phones as hotspots for connectivity.Solved11KViews0likes1Comment
Loss of connectivity, IPv6 only (no IPv4) and DOCSIS T3/T4 errors
Our two Win10 computers go from disconnected, IPv6 access only, IPv4 and IPv6 full access, everything ok and back again. This has been happening for several weeks. I have swapped out cable modem (NETGEAR C6300BD), NIC cards and switch in the house without impact. The ethernet interface often says: IPv4 Connectivity: No network access IPv6 Connectivity: Internet You can also see this in online forums as "only google works" as all IPv6 sites work - but there aren't many. When running diagnostics the error is "Ethernet" does not have a valid IP configuration" Not fixed. Also noticed teredo tunneling was being used to do IPv6 over IPv4 and that this is one of the least prefered methods. After reviewing cable modem event logs there are several T4 errors and some T3 errors. Therefore I believe this problem is between cable modem and Cox. NETGEAR C6300BD Event Log T4 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=10:da:43:28:33:90;CMTS-MAC=00:13:5f:05:c1:b1;CM-QOS=1.1;CM-VER=3.0;11KViews0likes21Comments
Slow real time upload speed - conflicting speed test results
I'm experiencing slow real time upload speeds. The speed test on Cox website have conflicting results. I've had 8 techs out to my house over the last 4 months and the issue has not been resolved. I am experiencing the same exact issues as usernoah82. We are both in Arizona. Here is his thread.http://forums.cox.com/forum_home/internet_forum/f/5/t/13025.aspx9.3KViews0likes34Comments
Packet Loss and Latency Spikes
This is not the first time this is happened (it happens periodically), but I am having issues with packet loss and disconnects between my modem and the ISP (hop 2). They are intermittent and very annoying. I pay $75 a month for fast internet, and I am the only person who uses it, yet I have constant problems. I had these issues with the old Cox-issed Cisco modem and my current Surfboard SB6183. Same issues with three different routers as well (Apple AirPort Extreme, Netgear Nighthawk X6, Linksys WRT1900AC). It has to be on Cox's end, but I get zero help when I call in and talk to support. They always ask me stupid questions (have you reset the modem, have you checked your router, have you tried connecting directly to the modem via ethernet, etc.) and say everything looks fine on their end. I had a tech out last month and he pulled a filter/splitter off and replaced it and said things were fixed. I was at work when he came and my housemate said that he was here for about 10 minutes. Below is a screenshot of Pingplotter, the status page of my modem, and the event log of my modem. http://i.imgur.com/1Gnp1a5.png 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 73 813000000 Hz 8.7 dBmV 40.2 dB 9 65 2 Locked QAM256 74 819000000 Hz 9.1 dBmV 40.3 dB 23 48 3 Locked QAM256 75 825000000 Hz 8.9 dBmV 40.3 dB 17 56 4 Locked QAM256 76 831000000 Hz 9.1 dBmV 40.2 dB 43 133 5 Locked QAM256 77 837000000 Hz 9.4 dBmV 40.3 dB 15 84 6 Locked QAM256 78 843000000 Hz 9.8 dBmV 40.1 dB 11 67 7 Locked QAM256 79 849000000 Hz 9.7 dBmV 40.5 dB 13 60 8 Locked QAM256 80 855000000 Hz 9.6 dBmV 40.3 dB 18 69 9 Locked QAM256 89 909000000 Hz 8.8 dBmV 40.3 dB 15 55 10 Locked QAM256 90 915000000 Hz 8.7 dBmV 40.3 dB 38 61 11 Locked QAM256 91 921000000 Hz 8.7 dBmV 40.3 dB 24 98 12 Locked QAM256 92 927000000 Hz 9.2 dBmV 40.5 dB 38 31 13 Locked QAM256 93 933000000 Hz 8.8 dBmV 40.3 dB 22 81 14 Locked QAM256 94 939000000 Hz 8.2 dBmV 40.1 dB 49 107 15 Locked QAM256 95 945000000 Hz 7.7 dBmV 39.9 dB 18 57 16 Locked QAM256 96 951000000 Hz 8.2 dBmV 40.0 dB 12 69 Upstream Bonded Channels Channel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power 1 Locked ATDMA 4 5120 Ksym/sec 37300000 Hz 36.9 dBmV 2 Locked ATDMA 1 2560 Ksym/sec 19400000 Hz 34.8 dBmV 3 Locked ATDMA 2 5120 Ksym/sec 24300000 Hz 35.3 dBmV 4 Locked ATDMA 3 5120 Ksym/sec 30800000 Hz 36.0 dBmV Current System Time:Mon Jan 02 20:18:17 2017 Time Priority Description Mon Jan 02 20:02:24 2017 Warning (5) Dynamic Range Window violation Mon Jan 02 19:45:13 2017 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Mon Jan 02 19:44:45 2017 Warning (5) Dynamic Range Window violation Mon Jan 02 19:44:44 2017 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Mon Jan 02 19:43:15 2017 Warning (5) Dynamic Range Window violation Mon Jan 02 19:40:31 2017 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Mon Jan 02 19:39:48 2017 Notice (6) TLV-11 - unrecognized OID;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Time Not Established Warning (5) DHCP WARNING - Non-critical field invalid in response ;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;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 Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.0;CM-VER=3.0; Time Not Established Critical (3) No Ranging Response received - T3 time-out Mon Jan 02 19:38:47 2017 Critical (3) Resetting the cable modem due to docsDevResetNow Mon Jan 02 19:14:32 2017 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Mon Jan 02 14:49:12 2017 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Time Not Established Critical (3) No Ranging Response received - T3 time-out Sun Jan 01 12:18:24 2017 Critical (3) Resetting the cable modem due to docsDevResetNow Sun Jan 01 12:06:25 2017 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sun Jan 01 10:18:08 2017 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sun Jan 01 10:18:04 2017 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sun Jan 01 07:45:18 2017 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sun Jan 01 04:12:00 2017 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sun Jan 01 02:49:36 2017 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sun Jan 01 02:49:26 2017 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sun Jan 01 01:04:25 2017 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sun Jan 01 00:34:59 2017 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sat Dec 31 22:08:29 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sat Dec 31 21:16:38 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sat Dec 31 21:16:10 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sat Dec 31 19:37:00 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sat Dec 31 19:36:57 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sat Dec 31 19:36:44 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sat Dec 31 19:29:30 2016 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sat Dec 31 19:21:46 2016 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sat Dec 31 19:04:05 2016 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sat Dec 31 18:26:28 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sat Dec 31 17:06:43 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sat Dec 31 14:38:58 2016 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sat Dec 31 10:22:19 2016 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sat Dec 31 10:20:20 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sat Dec 31 09:14:17 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Fri Dec 30 20:11:54 2016 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Fri Dec 30 19:32:03 2016 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Fri Dec 30 19:31:47 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Fri Dec 30 14:19:22 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Fri Dec 30 12:53:38 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Fri Dec 30 12:32:27 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Fri Dec 30 12:06:47 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Fri Dec 30 11:44:52 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Fri Dec 30 11:16:42 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Fri Dec 30 09:43:45 2016 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Fri Dec 30 08:47:55 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Thu Dec 29 23:01:39 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Thu Dec 29 17:40:27 2016 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 0;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Thu Dec 29 17:40:27 2016 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Thu Dec 29 17:40:27 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Thu Dec 29 17:37:28 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Thu Dec 29 15:10:05 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Thu Dec 29 15:09:58 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Thu Dec 29 13:05:10 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Thu Dec 29 13:04:38 2016 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Thu Dec 29 12:16:33 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Thu Dec 29 10:44:07 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Thu Dec 29 04:02:33 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Thu Dec 29 02:35:07 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Thu Dec 29 02:34:58 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Thu Dec 29 02:34:46 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Thu Dec 29 01:28:56 2016 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 0;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Thu Dec 29 01:28:56 2016 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Thu Dec 29 01:28:56 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Wed Dec 28 20:58:38 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Wed Dec 28 14:04:29 2016 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Wed Dec 28 12:26:04 2016 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Wed Dec 28 12:25:50 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Wed Dec 28 10:26:12 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Wed Dec 28 10:24:58 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Wed Dec 28 10:23:40 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Wed Dec 28 10:23:38 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Wed Dec 28 10:23:36 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Wed Dec 28 10:18:33 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Tue Dec 27 18:29:10 2016 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Tue Dec 27 18:27:38 2016 Critical (3) Resetting the cable modem due to docsDevResetNow Tue Dec 27 14:13:19 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Tue Dec 27 14:06:05 2016 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Tue Dec 27 13:57:24 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Tue Dec 27 12:15:27 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Tue Dec 27 11:34:07 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Tue Dec 27 09:26:31 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Mon Dec 26 17:42:40 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Mon Dec 26 04:52:59 2016 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Mon Dec 26 04:52:45 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sun Dec 25 14:20:37 2016 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sun Dec 25 13:40:15 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sun Dec 25 09:58:00 2016 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 0;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sun Dec 25 09:58:00 2016 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sun Dec 25 09:58:00 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sun Dec 25 09:39:19 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sun Dec 25 04:37:19 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sun Dec 25 00:05:00 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sat Dec 24 14:36:22 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sat Dec 24 09:44:20 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0;8.6KViews0likes24CommentsUnresolved Internet Issues
Alright so so here is the story. About a month ago I started having internet issues. My modem would lose connection and begin to reset . To fix this I would need to unplug it and plug it back in. After about a week I called tech support. The lady on the other end told me to replace my modem and I did. The issue was still present so I called them back and the lady looked at my modem and saw that it was resetting like crazy. She had me plug my computer in directly to the modem instead of my router and she still saw the same disconnects. She redirected me to level 2 support and they scheduled a technician.The tech came on 10/10, replaced a splitter that was replaced less than a year ago, and added an amplifier. For the rest of the day the internet was fine. The next morning I woke up to see that the modem was resetting. I called tech support again and they said a tech would be sent on 10/13. He came and brought a device to measure the signal strength I'm presuming. He said that he would bypass the splitter outside the bedroom door. So he drilled a hole directly in my room and ran a new cable to the modem. The setup is now this: From the box outside the apartment complex 3 cables come out one for us,one for a neighbor, and one for another neighbor. The cable going to our home is then split 3 ways: living room tv, cable to a 2 way splitter for tvs in 2 bedrooms, and the modem(he also added an arcom filter). It's been a little better but just today I disconnected about 3 times in a span of less than an hour. I have become irritated because I was charged $60(on top of the usual bill) and it did not resolve the problem. In 12+ years I have never had a problem this big with cox. I would like to stay with Cox however we have school work to do online and one of us has school entirely online. Cox is leaving me with less options and I'm considering moving to another provider. Here are the singal and logs as of today. The filter did bring down the downstream level to a better range.8.4KViews0likes20Comments
Unresolved Internet Issues
Alright so so here is the story. About a month ago I started having internet issues. My modem would lose connection and begin to reset . To fix this I would need to unplug it and plug it back in. After about a week I called tech support. The lady on the other end told me to replace my modem and I did. The issue was still present so I called them back and the lady looked at my modem and saw that it was resetting like crazy. She had me plug my computer in directly to the modem instead of my router and she still saw the same disconnects. She redirected me to level 2 support and they scheduled a technician.The tech came on 10/10, replaced a splitter that was replaced less than a year ago, and added an amplifier. For the rest of the day the internet was fine. The next morning I woke up to see that the modem was resetting. I called tech support again and they said a tech would be sent on 10/13. He came and brought a device to measure the signal strength I'm presuming. He said that he would bypass the splitter outside the bedroom door. So he drilled a hole directly in my room and ran a new cable to the modem. The setup is now this: From the box outside the apartment complex 3 cables come out one for us,one for a neighbor, and one for another neighbor. The cable going to our home is then split 3 ways: living room tv, cable to a 2 way splitter for tvs in 2 bedrooms, and the modem(he also added an arcom filter). It's been a little better but just today I disconnected about 3 times in a span of less than an hour. I have become irritated because I was charged $60(on top of the usual bill) and it did not resolve the problem. In 12+ years I have never had a problem this big with cox. I would like to stay with Cox however we have school work to do online and one of us has school entirely online. Cox is leaving me with less options and I'm considering moving to another provider. Here are the singal and logs as of today. The filter did bring down the downstream level to a better range.
