NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
CM1000
16 TopicsUnable to connect after power outage
So to my knowledge, we had just recently had a brief thunderstorm last night while I was at work. When I returned home our wifi was out and did not return after multiple reboots. This morning I had done extensive searching to try and troubleshoot the issue, with multiple power cycles to our Netgear CM1000 modem and our Tp-Link Archer AX21 router. I have even tried to factory reset both the modem and router to no resolve of the issue. For now, the indicator lights on the modem are all static green for power, downstream, upstream and internet. No lights will turn on for the ethernet despite multiple different cables connected securely. The lights will however blink orange once during reboot. For the router only the power button is solid green, with the occasional rest of the lights flashing green except for the internet flashing orange. I have also done troubleshooting with Spectrum to which they stated there is no issue with the ISP and that it may be a router/modem issue.61Views0likes1CommentCM1000 Xfinity issues
I am quite frustrated at this point. I had a CM600 modem to support Comcast's Extreme 150 service. I've had it for a few years and was consistently getting 160 to 170mbps speed from it. About three weeks ago, I noticed a drop off and did a speed test and could not get more than 50mbps. Comcast reset the modem (I did the same thing). No change. They sent a tech out to the house and he swapped out my modem for one of theirs and lo and behold, 170mbps. He said I needed a new modem. I was a little suspicious of this, but wanting to eventually get gigabit service when it becomes available, I bought a CM1000. It provisioned fine, but I am seeing the same behavior. At the start of the speed test it spikes to over 100 but eventually averages out to 70 or 80. They came out again and re-trenched a new thicker line between the street and the house. Still the same behavior. The tech came out again today and installed a dedicated line directly from the outside box to the modem. Still the same behavior. The logs from the Modem are consistently showing: Time Priority Description 2017-12-03, 10:41:31 Notice (6) CM-STATUS message sent. Event Type Code: 4; Chan ID: 21 22 ; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=b0:39:56:4b:b8:68;CMTS-MAC=00:01:5c:a7:12:4e;CM-QOS=1.1;CM-VER=3.1; 2017-12-03, 10:41:17 Warning (5) MDD message timeout;CM-MAC=b0:39:56:4b:b8:68;CMTS-MAC=00:01:5c:a7:12:4e;CM-QOS=1.1;CM-VER=3.1; The Cable Connection page displays the following. Any thoughts on this issue? Frequency start Value This field below allows you to modify the frequency the cable modem start with its scan during initialization and registration. Enter the new start frequency and restart the cable modem for it to take effect. Starting Frequency <tabindex=-1>Startup Procedure Procedure Status Comment Acquire Downstream Channel 555000000 Hz Locked Connectivity State OK Operational Boot State OK Operational Security Enable BPI+ IP Provisioning Mode Honor MDD IPv6 only <tabindex=-1>Downstream Bonded Channels Channel Lock Status Modulation Channel ID Frequency Power SNR / MER Unerrored Codewords Correctable Codewords Uncorrectable Codewords 1 Locked QAM256 20 555000000 Hz 2.8 dBmV 36.8 dB 158493311 546 0 2 Locked QAM256 1 423000000 Hz 5.4 dBmV 38.7 dB 157105990 36 0 3 Locked QAM256 2 429000000 Hz 5.6 dBmV 38.9 dB 157114932 13 0 4 Locked QAM256 3 435000000 Hz 5.6 dBmV 39.0 dB 157125743 17 0 5 Locked QAM256 4 441000000 Hz 5.1 dBmV 38.7 dB 157134245 29 0 6 Locked QAM256 5 453000000 Hz 4.2 dBmV 38.5 dB 157143868 60 0 7 Locked QAM256 6 459000000 Hz 3.8 dBmV 38.3 dB 157153008 71 0 8 Locked QAM256 7 465000000 Hz 3.5 dBmV 38.3 dB 157162210 62 0 9 Locked QAM256 8 471000000 Hz 3.2 dBmV 38.2 dB 157171891 72 0 10 Locked QAM256 9 477000000 Hz 2.7 dBmV 38.0 dB 157181040 59 0 11 Locked QAM256 10 483000000 Hz 2.2 dBmV 37.5 dB 157190267 74 0 12 Locked QAM256 11 489000000 Hz 2.0 dBmV 37.4 dB 157199468 75 0 13 Locked QAM256 12 495000000 Hz 1.9 dBmV 37.4 dB 157208618 80 0 14 Locked QAM256 13 507000000 Hz 1.7 dBmV 37.3 dB 157218872 61 0 15 Locked QAM256 14 513000000 Hz 1.6 dBmV 37.3 dB 157227558 70 0 16 Locked QAM256 15 519000000 Hz 1.4 dBmV 37.3 dB 157237136 95 0 17 Locked QAM256 16 525000000 Hz 1.1 dBmV 37.1 dB 157246947 121 0 18 Locked QAM256 17 531000000 Hz 1.3 dBmV 37.4 dB 157255633 105 0 19 Locked QAM256 18 537000000 Hz 1.3 dBmV 37.1 dB 157264694 132 0 20 Locked QAM256 19 543000000 Hz 1.6 dBmV 37.1 dB 157275272 112 0 21 Locked QAM256 21 561000000 Hz 2.9 dBmV 32.3 dB 147085863 2537135 7646772 22 Locked QAM256 22 567000000 Hz 3.6 dBmV 27.2 dB 135579752 4471561 17201032 23 Locked QAM256 23 573000000 Hz 3.7 dBmV 35.5 dB 152906954 3458380 927827 24 Locked QAM256 24 579000000 Hz 3.1 dBmV 34.7 dB 157299415 177 0 25 Not Locked Unknown 0 0 Hz 0.0 dBmV 0.0 dB 0 0 0 26 Not Locked Unknown 0 0 Hz 0.0 dBmV 0.0 dB 0 0 0 27 Not Locked Unknown 0 0 Hz 0.0 dBmV 0.0 dB 0 0 0 28 Not Locked Unknown 0 0 Hz 0.0 dBmV 0.0 dB 0 0 0 29 Not Locked Unknown 0 0 Hz 0.0 dBmV 0.0 dB 0 0 0 30 Not Locked Unknown 0 0 Hz 0.0 dBmV 0.0 dB 0 0 0 31 Not Locked Unknown 0 0 Hz 0.0 dBmV 0.0 dB 0 0 0 32 Not Locked Unknown 0 0 Hz 0.0 dBmV 0.0 dB 0 0 0 <tabindex=-1>Upstream Bonded Channels Channel Lock Status Modulation Channel ID Frequency Power 1 Locked ATDMA 1 35600000 Hz 35.8 dBmV 2 Locked ATDMA 2 29200000 Hz 35.8 dBmV 3 Locked ATDMA 3 22800000 Hz 34.0 dBmV 4 Not Locked Unknown 0 0 Hz 0.0 dBmV 5 Not Locked Unknown 0 0 Hz 0.0 dBmV 6 Not Locked Unknown 0 0 Hz 0.0 dBmV 7 Not Locked Unknown 0 0 Hz 0.0 dBmV 8 Not Locked Unknown 0 0 Hz 0.0 dBmV <tabindex=-1>Downstream OFDM Channels Channel Lock Status Modulation / Profile ID Channel ID Frequency Power SNR / MER Active Subcarrier Number Range Unerrored Codewords Correctable Codewords Uncorrectable Codewords 1 Locked 0, 1 25 372000000 Hz 7.6 dBmV 38.3 dB 1108 ~ 2987 4381967 35743 0 2 Not Locked 0 0 0 Hz 7.2 dBmV 0.0 dB 0 ~ 4095 0 0 0 <tabindex=-1>Upstream OFDMA Channels Channel Lock Status Modulation / Profile ID Channel ID Frequency Power 1 Not Locked Unknown 0 0 Hz 0 dBmV 2 Not Locked Unknown 0 0 Hz 0 dBmV Any help or guidance I can give Xfinity would be greatly appreciated. I really want to own my own equipment and not pay $10 a month for their stuff. Warm regards, JoeSolved78KViews0likes78CommentsXR500 and cm1000
Hey all I just bought the xr500 its pretty cool so far ,But i am having a slight hicup . If i restart my cm1000 the light on the xr500 goes amber even when the modem gets full back up it stays amber . I am wondering if maybe I got a bad xr500 or if its a glitch When i got the webpage for the modem It will not detect my modem till I unplug the router and power it back up.Solved8.4KViews0likes19CommentsIntermittent connection problems
I am looking for help diagnosing intermittent connectivity issues with my CM1000 modem. I am not sure what clues I should be looking for and I have not been able to detect any patterns to indicate cause. Let me offer some details… I am an Xfinity customer in my home, and I have been using a Netgear CM1000 modem for around 6 months. Everything worked great for the first 5 months. However, the last month I have been getting hit with maddening intermittent connection problems. I lose all internet connectivity and cannot ping anything on the internet for short periods of time. These issues usually just last a minute or two, but sometimes as long as 5 minutes. Network connectivity eventually comes back without any intervention from me. Some days I have no connectivity issues, other days it happens several times (usually in the most in-opportune times!). I have not noticed any change in the modem lights when this occurs. When I call Xfinity/Comcast support their only suggestion is to reboot the modem. That usually causes the connection to be restored, but I don’t think that is really fixing anything – like I said the connection issues usually only last a minute or two anyways. The agent I talked to at Comcast said she cannot see anything else on her end. Since I own my own modem, she stated it will likely cost me money to have a tech come out and look at it. Before I break down and have someone come out, I wanted to search for some evidence that is or is not a modem problem. I’m not against buying a new modem either, but am going to be frustrated if I have the same problems. This behavior occurs on multiple computers - both wireless and wired – which leads me to believe it is a network issue. I swapped out my router for a few days just to see if it was possibly a router issue. The same issues occurred with the replacement router, so I think I can rule that out as well. I did chat with my good friend Google a bit and learned to check the power levels. The power levels seem ok as they fall between the -7 to 7 range for downstream and 38-48 for upstream. I haven’t touched any cables lately, but did double check the cables I had access to to make sure they were connected tightly. My Hardware version is 2.02 and firmware version is V3.01.04. I understand that Xfinifity/Comcast controls pushing out the firmware updates so there is not much I can really do about adjusting firmware. I do have an older (slower) modem I suppose I could go back to for a while and see if I have problems with that. Any thoughts/ideas would be appreciated.1.5KViews1like1CommentNot getting correct speed with Comcast
Hello all In November I saw that Comcast offered a higher tier internet service in my neighborhood. Speeds are advertised up to 986 Mbps. Since I signed up I’ve only seen 350-400 Mbps. I had a couple of online chats and phone calls with Comcast. I also had two techs come to the house to check the signal to the house. The second tech said that Comcast had to approve new firmware for my CM1000 modem (this was in December). He said that once Comcast approved the firmware then Netgear would push the upgrade to my modem directly. I called to try to get credit for billing since I wasn’t getting the correct speeds and I was forced to chat with Comcast tech support again. The tech sent me a link to the Nighthawk X6 router firmware page to update my CM1000 cable modem :| When I told them it was the wrong equipment they told me to contact Netgear directly to receive my firmware update. I sent this link to him. https://www.netgear.com/support/product/CM1000#download It says “Current Versions Firmware upgrades are pushed down by your ISP. For more information, please see our Knowledge Base .” He just told me to talk to Netgear :| Has anyone had any success getting advertised speeds with Comcast Gigabit Internet? Thanks for your time13KViews0likes6CommentsCM1000 + Orbi (RBK50) on Xfinity - Constant Disconnects
Hello there, I am having similar problems to ones on this board - Constant disconnects on the Orbi platform with a CM1000 modem on Xfinity. A Comcast tech has been by, checked the levels and left saying everything's fine with the incoming line. It works great when it does ( Blast tier - ~200 - 250 Mbps) but the disconnects are getting out of hand. They last a few seconds at a time to ~6 minutes at a time (most common) if left unattended - Rebooting the modem/router fixes it in a minute and a half (even that's not consistent of late). Details: CM1000 Hardware Version 2.02 Firmware Version V3.01.04 Orbi RBK50 Router Firmware Version V2.1.1.16 uPnP OFF,Daisy Chaining Disabled, MU-MIMO and Implicit Beamforming Enabled, Fast Roaming Disabled I am attaching logs and event logs from the modem and router if at all it helps nailing the problem(s). Please let me know what else I can do before returning either/both modem and router.1.2KViews0likes1CommentNetgear R7000 isn't up to speed on a gigabit connection through CM1000 modem
Hi, I recently got a Netgear CM1000 modem on my gigabit Xfinity connection. When I hook my laptop up to the modem directly I am getting close to a gigabit connection, at least above 900 Mbps consistently. But when I hook up (ethernet) through my R7000 with fully upgraded stock firmware I'm still just getting around 200 Mbps which is the speed I used to have before my connection was upgraded. What could the reason be for me not getting any speed increase when connecting through the router? As far as I can see the the router should be able to handle the speed.Solved16KViews0likes5CommentsCM1000 requiring rebooting several times a day (Comcast)
I recently purchased a Netgear CM1000 for use on Comcast and several times a day the internet just stops working despite all lights still showing green. When this happens I can't even log into the web management app. Turning the modem off and back on removes the problem, but this is really annoying to have to do multiple times a day! Any advice is welcomed. Here are some pertinent pieces of information: Hardware Version 2.02 Firmware Version V2.01.14 Acquire Downstream Channel 639000000 Hz Locked Connectivity State OK Operational Boot State OK Operational Security Enable BPI+ IP Provisioning Mode Honor MDD IPv6 only Downstream Bonded Channels Channel Lock Status Modulation Channel ID Frequency Power SNR Correctables Uncorrectables 1 Locked QAM256 17 639000000 Hz -1.7 dBmV 39.1 dB 1 0 2 Locked QAM256 1 543000000 Hz -1.3 dBmV 40.1 dB 0 0 3 Locked QAM256 2 549000000 Hz -1.2 dBmV 40.1 dB 2 0 4 Locked QAM256 3 555000000 Hz -1.3 dBmV 40.0 dB 1 0 5 Locked QAM256 4 561000000 Hz -1.4 dBmV 39.9 dB 2 0 6 Locked QAM256 5 567000000 Hz -1.3 dBmV 40.0 dB 0 0 7 Locked QAM256 6 573000000 Hz -1.5 dBmV 39.9 dB 3 0 8 Locked QAM256 7 579000000 Hz -1.4 dBmV 39.7 dB 2 0 9 Locked QAM256 8 585000000 Hz -1.5 dBmV 39.7 dB 2 0 10 Locked QAM256 9 591000000 Hz -1.5 dBmV 39.7 dB 4 0 11 Locked QAM256 10 597000000 Hz -1.7 dBmV 39.6 dB 7 0 12 Locked QAM256 11 603000000 Hz -2.0 dBmV 39.3 dB 3 0 13 Locked QAM256 12 609000000 Hz -2.5 dBmV 39.3 dB 5 0 14 Locked QAM256 13 615000000 Hz -2.0 dBmV 39.3 dB 6 0 15 Locked QAM256 14 621000000 Hz -1.7 dBmV 39.3 dB 4 0 16 Locked QAM256 15 627000000 Hz -1.7 dBmV 39.2 dB 2 0 17 Locked QAM256 16 633000000 Hz -1.7 dBmV 39.3 dB 1 0 18 Locked QAM256 18 645000000 Hz -1.8 dBmV 39.3 dB 2 0 19 Locked QAM256 19 651000000 Hz -1.7 dBmV 39.1 dB 3 0 20 Locked QAM256 20 657000000 Hz -1.7 dBmV 39.2 dB 3 0 21 Locked QAM256 21 663000000 Hz -1.6 dBmV 39.1 dB 3 0 22 Locked QAM256 22 669000000 Hz -1.6 dBmV 39.1 dB 1 0 23 Locked QAM256 23 675000000 Hz -1.5 dBmV 39.1 dB 0 0 24 Locked QAM256 24 681000000 Hz -1.5 dBmV 39.0 dB 0 0 ... Upstream Bonded Channels Channel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power 1 Locked ATDMA 1 5120 Ksym/sec 30100000 Hz 45.5 dBmV 2 Locked ATDMA 2 5120 Ksym/sec 36500000 Hz 45.5 dBmV 3 Locked ATDMA 3 5120 Ksym/sec 17300000 Hz 43.5 dBmV 4 Locked ATDMA 4 5120 Ksym/sec 23700000 Hz 45.5 dBmV ... Time Priority Description 2017-01-22, 21:03:53 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:1d:45:70:69:60;CM-QOS=1.1;CM-VER=3.1; 2017-01-22, 21:03:58 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:1d:45:70:69:60;CM-QOS=1.1;CM-VER=3.1; 2017-01-22, 21:04:05 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:1d:45:70:69:60;CM-QOS=1.1;CM-VER=3.1; 2017-01-22, 21:04:49 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:1d:45:70:69:60;CM-QOS=1.1;CM-VER=3.1; 2017-01-22, 21:04:49 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:1d:45:70:69:60;CM-QOS=1.1;CM-VER=3.1; 2017-01-22, 21:05:09 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:1d:45:70:69:60;CM-QOS=1.1;CM-VER=3.1; 2017-01-22, 21:05:10 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:1d:45:70:69:60;CM-QOS=1.1;CM-VER=3.1; 2017-01-22, 21:05:28 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:1d:45:70:69:60;CM-QOS=1.1;CM-VER=3.1; 2017-01-22, 21:05:29 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:1d:45:70:69:60;CM-QOS=1.1;CM-VER=3.1; 2017-01-22, 21:05:48 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:1d:45:70:69:60;CM-QOS=1.1;CM-VER=3.1; Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; Time Not Established Critical (3) No Ranging Response received - T3 time-out;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:1d:45:70:69:60;CM-QOS=1.1;CM-VER=3.1; Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; 2017-01-24, 19:26:40 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:1d:45:70:69:60;CM-QOS=1.1;CM-VER=3.1; 2017-01-24, 21:01:18 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:1d:45:70:69:60;CM-QOS=1.1;CM-VER=3.1; 2017-01-24, 21:01:21 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:1d:45:70:69:60;CM-QOS=1.1;CM-VER=3.1; 2017-01-24, 21:01:27 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:1d:45:70:69:60;CM-QOS=1.1;CM-VER=3.1; 2017-01-24, 21:02:09 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:1d:45:70:69:60;CM-QOS=1.1;CM-VER=3.1; 2017-01-24, 21:02:09 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:1d:45:70:69:60;CM-QOS=1.1;CM-VER=3.1; 2017-01-24, 21:02:29 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:1d:45:70:69:60;CM-QOS=1.1;CM-VER=3.1; 2017-01-24, 21:02:30 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:1d:45:70:69:60;CM-QOS=1.1;CM-VER=3.1; 2017-01-24, 21:02:49 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:1d:45:70:69:60;CM-QOS=1.1;CM-VER=3.1; 2017-01-24, 21:02:50 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:1d:45:70:69:60;CM-QOS=1.1;CM-VER=3.1; 2017-01-24, 21:03:09 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:1d:45:70:69:60;CM-QOS=1.1;CM-VER=3.1; Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; 2017-01-24, 22:53:14 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:1d:45:70:69:60;CM-QOS=1.1;CM-VER=3.1; 2017-01-24, 23:00:30 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:1d:45:70:69:60;CM-QOS=1.1;CM-VER=3.1; 2017-01-24, 23:00:35 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:1d:45:70:69:60;CM-QOS=1.1;CM-VER=3.1; 2017-01-24, 23:00:41 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:1d:45:70:69:60;CM-QOS=1.1;CM-VER=3.1; 2017-01-24, 23:01:11 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:1d:45:70:69:60;CM-QOS=1.1;CM-VER=3.1; 2017-01-24, 23:01:12 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:1d:45:70:69:60;CM-QOS=1.1;CM-VER=3.1; 2017-01-24, 23:01:32 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:1d:45:70:69:60;CM-QOS=1.1;CM-VER=3.1; 2017-01-24, 23:01:32 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:1d:45:70:69:60;CM-QOS=1.1;CM-VER=3.1; 2017-01-24, 23:01:53 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:1d:45:70:69:60;CM-QOS=1.1;CM-VER=3.1; 2017-01-24, 23:01:54 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:1d:45:70:69:60;CM-QOS=1.1;CM-VER=3.1; 2017-01-24, 23:02:12 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:1d:45:70:69:60;CM-QOS=1.1;CM-VER=3.1; Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; Time Not Established Critical (3) No Ranging Response received - T3 time-out;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:1d:45:70:69:60;CM-QOS=1.1;CM-VER=3.1; Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; Time Not Established Notice (6) Honoring MDD; IP provisioning mode = IPv6 This event log comes shortly after I had to restart my modem for the second time in the last 2 hours!Solved35KViews0likes66CommentsOrbi WiFi System (RBK53) AC3000
I am considering purchasing the Orbi WiFi System (RBK53) AC3000 system along with the Netgear CM1000 docsis 3.1 cable modem. Is anyone running this setup? If so, have you experienced the random network drops that some have mentioned? Also, is there a limit to how many satellites can be added before a reduction in speed occurs? I want the router and 3 satellites provided that the addition of the 3rd satellite won't cause a performance drop. Thanks in advance for your help!Solved