Cox ruining Fortnite and Live Streaming experience with PACKET LOSS
Okay I started getting packet losses two months ago, which is like a freaking cancer. I did everything from switching coax, hard wiring modem to pc, new ethernet cords, even buying a new modem and sending cox the one they rented me out (new modem is cox compatible Netgear Nighthawk c7000). spoke to probably more than 20 techs online who by the way all did the same thing, reset my modem and cleared the cache. I had two techs come out to look at my house and one changed the lines, which did absolutely nothing, probably made it worst. The next one came and connected my modem into his little device and he said that everything was good, and he left. Now i look like the boy who cried wolf, but i know for *** sure i'm not the only one having this stupid problem. It seems to always happen more at night than in the morning, network congestion or what? Why is there no cure to this cancer yet, seriously... what do we have to do, EVEN if i get another tech sent out to my house what will they do? look at the modem and say its good? they have no idea how to approach this situation. I have the ultimate package w/ the unlimited data plan bringing me the max amount of $ i could pay for internet with cox, I for *** sure know i'm getting ripped off, I'm probably better plugging my computer directly into a potato. Packet losses ranging from 10%-60% all night long, jittery gameplay, unable to live stream AT ALL download speeds are reading as it should, normally 200-300 mpbs... but upload, oh yes upload speeds are a whopping Less than 1mpbs...(paying for 30mbps btw) every night, tried every speed test site i could find, the meter stick doesn't even move, looks like its trying to go backwards if anything. I hate this city for only having cox as the main isp that offer high speeds lol. god this ** so bad, vent over. solution you wont find, i just wanted to complain and get this off my chest since cox doesn't do anything with reimbursing me from all this stress and frustration. Unplugging modem for 10 seconds and plugging it back in now for the 42,371,284th time...Solved56KViews2likes53Comments
Problems with New Cox Webmail interface
First, the new webmail loads EXTREMELY slow! I have tried from different computers at different locations, and it is always SLOW. If I use the new link "myemail.cox.net", some of my accounts do not load at all after I log-in )I just get three blinking circles). I am using Windows 7 and Internet Explorer 11. I found by accident that if I use "in-private browsing", then the other accounts will load (but still slow). How do I fix so I can just log-in normally? After getting logged in (If I get that far): 1 - Nowhere on the page does it tell me which account I am logged-in on. It used to say "log out Joe's email", for example. 2- All the messages are listed on one page. There is no way to Delete a specific message without opening it. If I click on it, it opens. There is no Check-Box like there used to be, so I can select and delete all the Spam at once. Only option is one-at-a-time, or "select all". Overall, I see absolutely no improvement with this new system. Please reinstate the old one that worked fine for years (except for the poor service between Feb and May of this year)24KViews0likes16Comments
Slow Speeds with Netgear R7000 Router - How We Fixed It - SOLVED
This is a post about slow internet speeds with the Netgear R7000 router and how we solved the problem.If you want to skip directly to our fix, goto the fourth paragraph from the bottom of the post.If youwant the background first, keep reading. Like others, we've been having slow internet download speed issues with our R7000 router. These slow speeds are when we are connected by cable to the router with the wifi off on the computer and the router or if connected by wifi to the router - it doesn't matter. Our internet connection is the Ultimate package rated at 300Mbps/30Mbps download/upload. When connecting through the router we would be lucky to get 120-160Mbps download but always 30Mbps up. When connecting directly through the cable modem (Motorola MB8600) we usually get our rated download speed and above. All speed test numbers have been tested using not only the speed test software housed at Cox, but also speed test sites on the internet. All speed tests confirm each other as they are within 10% of each other with, of course, the ISP's test showing the fastest. Regardless, the R7000 router always showed 120-160 down (sometimes even half that at times). There would naturally be slightly slower speeds during congested times during the evening, but the R7000 would always be about 50% slower than if we were connected directly through the modem, bypassing the router. Before getting to what we did with the router, here is everything else that was done to isolate any other potential problems. Cox came out to the house multiple times. Network cables from the computer to the router and router to the modem were fine, but we replaced them with brand new CAT-7 cables anyway. Interior house coax cabling was fine and barrel connector were fine but connector replaced anyway. From the house to the tap, the cabling was fine. The tap checked out OK, but since it was old they replaced it anyway. The cabling from the tap to the post where cabling comes out of the street was fine, but they rebuilt the post anyway. The cabling in the street had one section that indicated some slight signal loss, so they replaced the cabling in the street. Back in the house, their test equipment was attached to the line ahead of our modem and regularly showed 315-330Mbs down and 31Mbps up. They reprovisioned our line at the central office, installed their modem on the coax, directly attached their modem to our computer and regularly got 300 or above on multiple occassions. They reprovisioned the line again,installed our modem on the coax, directly attached our modem to our computer and regularly got 300 or above on multiple occassions. Computer settings were checked to make sure everything was configured correctly and all unnecesary computer processes were stopped to make sure nothing was interfering. So, everything is OK on the ISP side and also with the computer and its cables. After making sure everything else was OK, we shut everything off, connected the computer back to the router and the router back to the modem, let the modem boot up completely, then let the router boot up completely, then let the computer boot up completely. After making sure all unnecesary processes were stopped, new speed tests were run showing slow 120-160 download speeds. Multiple tests over the past month connected to the router, whether by direct cable with wifi off on the computer and router, or whether connected by wifi consistently showed the slower speeds from the ISP's speed test and multiple internet speed test sites. And multiple tests while bypassing the router and being directly connected to the modem regularly showed 300-350. So the router was definitely the issue. Have we reset the router back to factory defaults? Yes. Have we been sure to download and install the latest firmware when it came out? Always - and there is where the problem is. We dutifully upgraded all the firmware releases up through the most current v1.09.18 (as of January, 2018). After reading others' posts, a number of them have talked about downgrading the firmware. Some have said v1.09.06 worked for them (but their rated line speed was, if I recall, much less than our 300/30). Others have said they have downgraded to v1.03.24 that had solved their problems (in fact, one of those people had a line rated at 400/40). Still others said v1.07.12 solved their problem. Hmm, was this the answer? After looking through our old speed test results from October, 2017, we noticed that when we upgraded our line in October from Premier 100/15 to Ultimate 300/30, we also upgraded our R7000 firmware from the 1.07.xx series to the 1.09.xx series - and that 's when our problems began. All along we thought the issue came from the ISP, thinking they either had equipment problems or that they had mis-provisioned our line when we switched to the faster plan. It turns out it was the firmware on the R7000 router. FINALLY - HERE'S THE FIX.We factory reset the router once again, downloaded and installed the v1.07.12 firmware, then again factory reset the router, direct connected to the router before rebuilding all our old settings, kept wifi turned off - and now we are regularly getting 300-350Mbps download from the router. After rebuilding all our old settings, turning wifi back on and still staying connected directly to the router, we are still getting 300-350 downloads. Removing the direct cable connection to the router and using the wifi from the computer to the router, we are regularly getting +/- 300Mbps downloads (of course depending on how close we are to the router). So that's the simple fix. I suspect there is something lurking in the 1.09.xx series firmware that is not allowing the router to efficiently handle higher rated line speeds (if you are at 150Mbps rated download or below, I'm guessing you are OK). Some people might say our settings weren't correct in the router when using the v1.09.xx firmware releases. I don't think that's the case since we tried everything AND we also factory reset the router while still using the v1.09.18 firmware. Hope this helps. This post was written January 10, 2018. The most recent firmware as of this date was v1.09.18, which caused us to have slow download speeds on the R7000 (much slower than our 300/30 line). If you're reading this after January, 2018, and you have slow speed issues with the router, and if the most current firmware is in the 1.09.xx series, I would suggest downgrading back to v1.07.12. UPDATE as of January 22, 2018: This fix has continued to work reliably. I'm consistently getting download speeds in upper 300's to lower 400's - either connected directly to the router or using wifi.21KViews0likes2CommentsUpload Problems
Hi, So I've been having problems with my upload for awhile now. I have the Ultimate package which is 300 down 30 up, the problem is my upload is never consistent and this is a problem because I live stream. At first I never got anything above 2-3Mbps so I called cox and they sent a tech out and the tech said there was a lot of problems in the box on the street including a trap. He said he fixed the issues in the box andthat if I was still having problems to call them back out to run a new line from the outside of my house to the inside as the line that runs through the walls was old, he also told me the modem I was renting from Cox was known to have problems. So after he left my uploads were about the same but I wasn't getting the packet loss that I was getting before. I called Cox and scheduled a tech to come out and replace the line i also starting doing research on modems and found out about the Puma 6 problems so i ordered the Netgear CM600 which has the Broadcom chipset. Now here's where it's starts to get weird, after I set up the new modem and called Cox to activate it I ran some speed test and my results were awesome I was getting like 17-25Mbps on my upload, I was really happy and I thought the issue was fixed so I called up Cox to cancel the tech. About 2 hours later Inoticed I was starting to drop frames so I ran some upload test and my upload speed was dropping lower and lower after each test until it back down to 3-6Mbps so I rescheduledthe tech to come out but the following day when I woke up speeds were back up to 17-25 Mbps, then they dropped again. The tech came out replaced the lines and the speed went back up for about 5-6 hours but then they dropped again. I don't know what the problem but my brain is about to explode. I need to fix w/e is causing this, I cant stream with upload that's all over the place and never consistent. If anyone has any ideas or suggestions I would really appreciate it. I run all my speed test on Testmy.net and speedof.me and use the Twitch Bandwidth tool for connections quality. I'm also not wireless I'm hardwired.19KViews0likes1Comment
Cox Ultimate internet Package Speeds are very slow
Hi all, I have the Ultimate package and my internet speeds are very slow ~20-22 upload and download. Purchased a new modem which is listed on the Cox Certified Cable Modems page and had Cox cable run new cable from the pole to my house with very little change in my speeds when tested. All testing is performed by directly connecting to the router and not using the wifi. Other test I changed out the cat6 ethernet cable and retested with same results. Listed below are my specs on my setup. Just not sure if my connection issue goes beyond the pole or on my end. Any input would help. 1. Netgear - Model C6300 / DOCSIS 3.0 / 16x4 channel 2. Lenovo Thinkpad / win10 64 bit / 16 GB memory 3. New cable from pole to my house thanks, Abom13KViews0likes0Commentsis it possible to change the wifi channel on my panoramic wifi to one that is less crowded?
Hello, I'm reaching out to ask how I can change the wifi channel used by my panoramic gateway/router. I have been having a lot of internet stuttering and lag recently. I thought the problem might resolve itself after the scheduled outage for system work on 3/15/2022. it didn't, so i changed my plan to a higher tier thinking there were more neighbors paying more, and i was getting slower speeds to keep bandwidth available. that didn't change anything either. After doing more homework I was led to look at the channel my hardware uses for wifi. This seems like a likely cause for the problem. I am on a channel with 15 other users that show a strong connection. there are 5ghz that are unused and available. i found that i can get to an older java interface through a browser by pointing it to the gateway, but that app says channels are automaticallycontrolled. any advice would be appreciated. regards, chris9.7KViews0likes9Comments
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.3KViews0likes34CommentsPaying for 300 mbps, not even getting 20. What gives?
Hi forum, for the past 2 days I have been getting less than "optimal" speeds to say the least. It took me about 20 seconds to open up this page, so thats saying something. Anyways, Im paying for 300/30 speeds, but getting less than advertised Router is: ARRIS DG2460 I know its not my PC because A) Its wired, and B) My phone cant load anything when connected to WiFi and C) My smart TV refuses to connect due to a bad connection. I assure you my pc is 10/100/1000 Ethernetas well as my router. I have done nothing to the router except change the name and the passwords on the dual band networks. Ive reset my router by unplugging it for an hour, resetting though the direct ip connection, and evem through cox. If this keeps going, I might switch back to centurylink, because as unreliable as they are, at least they give me my speeds.9.2KViews0likes10Comments
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.6KViews0likes24Comments
is it possible to change the wifi channel on my panoramic wifi to one that is less crowded?
Hello, I'm reaching out to ask how I can change the wifi channel used by my panoramic gateway/router. I have been having a lot of internet stuttering and lag recently. I thought the problem might resolve itself after the scheduled outage for system work on 3/15/2022. it didn't, so i changed my plan to a higher tier thinking there were more neighbors paying more, and i was getting slower speeds to keep bandwidth available. that didn't change anything either. After doing more homework I was led to look at the channel my hardware uses for wifi. This seems like a likely cause for the problem. I am on a channel with 15 other users that show a strong connection. there are 5ghz that are unused and available. i found that i can get to an older java interface through a browser by pointing it to the gateway, but that app says channels are automaticallycontrolled. any advice would be appreciated. regards, chris
