NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
ezicefield
Jan 27, 2016Follower
C7000-100NAS randomly drops internet connection
Hello,
My C7000-100NAS modem seems to randomly drop it's Comcast connection. This happen on 2.4 ghz, 5 ghz, and wired connections. There is no pattern, however the dropped connection usually lasts 2-5 minutes. When this happens, using the Netgear Genie is useless, it just stalls when trying to connect. Connecting to the IP of the modem works fine to reach the admin page. When the connection drops, the cable connection report on the C7000-100NAS shows the connection is good, 20x4 bonding. Other times, it reports the connection is offline.
I've been on the phone with Comcast, and they are not seeing anything wrong with the line, and no firmware updates are needed or available.
I see there are many reports of this same behavior with this model. The Amazon page is littered with them. I wish I had seen these reports before buying this pricey peice of equipment. I am hoping Netgear has a resolution. Of course the compimentary support period ended like 10 days ago, which is another source of frustration with this product.
Any help would be appreciated. Thanks.
119 Replies
- tomsdiner39Initiate
I got Netgear to replace my router after 2 phone calls, has been up for 12 days now with no reboots. I was resetting the router on a daily basis, somethimes 2 or 3 times a day when it would lock up, now it is ok, so far no reboots needed. Very fustrating process.
Went through a lot of time and expense having Comast out 6 times trying to fix, and it turns out all along it looks like it was the router.
- RreckrAspirant
Having the same problems here and it is getting very frustrating.
- DarrenMSr. NETGEAR Moderator
Hello Rreckr
When do you seem to have the most drop outs is it at a certain time of day?
DarrenM
- bronzelincolnsAspirant
i will no longer be dealing with the company and it's products. i've been out of a intenet connection for the last 3 days. in these 3 days i've had access to the web for 10 minutes only for it to go out again.
i've already sent for another modem/router from another company and will be taking this one back as i'm well within the return window.
i won't mention the abysmal CS.
lesson learned. don't deal with netgear.
- RreckrAspirantDarrenM
There doesn't seem to be a time of day that the problem is worse. It will randomly drop out when accessing the NAS from the Blu-ray or using the wired desktop PC. Ive been calling Gear head tech support every morning for the last few days. This morning they decided that the problem is the modem. They required a copy of my sales receipt because there was a problem with the serial number. So I emailed what they needed in order to work on a replacing the modem. Hope to hear back from them within a day or two. But when I have issue again in the morning I plan on calling again to check.- DarrenMSr. NETGEAR Moderator
Hello Rreckr
When you are having these issues can you copy the modems logs and post them here you can get the logs in the modems settings then click Advanced-Administration-Logs.
DarrenM
DarrenM, I am having very similar issues. My ISP is Cox cable, currently my router is running Version V1.01.18. The Netgear website states for this service provider I should only be running Version V1.01.15. Whats up with that, who is right? Is there anyway for me to download and install this older version? Cox claims they can't push it and I can't find it in the download section of the Genie or website.
- dc2012Guide
So I have been having the same problems as everyone else. Started about a month after I got the modem. I just RMA'd the thing after living with it for 5 months. New one has the same problems. BTW, Netgear made me pay to ship their faulty product back to them. My current workaround is putting the Netgear router into bridged mode to act as a modem only, then using my old asus router to do all the routing. Works A LOT better. I don't know how much longer this will last, but I'll update if it starts going back to crap. I think the Netgear router has a HUGE buffer in it to make up for lack of hardware. This is causing MAJOR ping Spikes. I was having an average of 500 to 1000ms hops on a trace route before. Now I'm back to under 30 on most hops. I'm hoping this continues to work out, but if I wasn't going to be using a combo modem I would have stuck with my existing and slower setup. I'm on time warner. My lines and connections have been checked by a two pros (one who was an independent) and are good. The fact that my old docsis 2.0 modem runs faster right now says way too much. Disappointed, and Pissed at the wasted money. NETGEAR please replace this POS with something else, make a firmware that works, or give us a CHEAP upgrade path.
- dc2012Guide
So I just had a third phone call with Netgear and this one was BY FAR the worst one. THe lady insisted on me going through all her stupid scripted crap, even though I had already been through it. Then she insists it takes 12 hours for the settings changes to work. 12 hours???? BS They are just trying to cycle the phones. Half an hour wait just to talk to her. CLUELESS. I told her about the traceroute pings and the connection dropping and I might as well have been talking french because she didn't know how to respond, so she went back to her script!
POOR SERVICE FOR A POOR PRODUCT.
They need to give me a working one or give me my $240 back.
C7000 started dropping connection yesterday. Comcast does not appear to be the issue. Logs on the router make it hard to pinpoint what really is going on. I am suspecting the router and if that is the case I will set the thing on fire and never buy another NG prodiuct. The event logs do have some really odd date stamps.
Time Priority Description 2016-12-15, 01:58:51 Critical (3) TFTP Request Retries exceeded, CM unable to register 2016-12-15, 01:58:54 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=a0:04:60:f5:19:a8;CMTS-MAC=00:24:c4:27:b9:39;CM-QOS=1.0;CM-VER=3.0; 2016-12-15, 02:00:28 Critical (3) TFTP failed - Request sent - No Response;CM-MAC=a0:04:60:f5:19:a8;CMTS-MAC=00:24:c4:27:b9:39;CM-QOS=1.0;CM-VER=3.0; 2016-12-15, 02:00:28 Critical (3) TFTP Request Retries exceeded, CM unable to register 2016-12-15, 02:00:33 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=a0:04:60:f5:19:a8;CMTS-MAC=00:24:c4:27:b9:39;CM-QOS=1.0;CM-VER=3.0; 2016-12-15, 02:01:29 Critical (3) DHCP failed - DHCP Solicit sent, No DHCP Advertise received;CM-MAC=a0:04:60:f5:19:a8;CMTS-MAC=00:24:c4:27:b9:39;CM-QOS=1.0;CM-VER=3.0; 2016-12-15, 02:01:32 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=a0:04:60:f5:19:a8;CMTS-MAC=00:24:c4:27:b9:39;CM-QOS=1.0;CM-VER=3.0; 2016-12-15, 02:01:51 Critical (3) No UCDs Received - Timeout;;CM-MAC=a0:04:60:f5:19:a8;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; 2016-12-15, 02:01:55 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=a0:04:60:f5:19:a8;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; 2016-12-15, 02:04:29 Critical (3) TFTP failed - Request sent - No Response;CM-MAC=a0:04:60:f5:19:a8;CMTS-MAC=00:24:c4:27:b9:39;CM-QOS=1.0;CM-VER=3.0; 2016-12-15, 02:04:29 Critical (3) TFTP Request Retries exceeded, CM unable to register 2016-12-15, 02:04:34 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=a0:04:60:f5:19:a8;CMTS-MAC=00:24:c4:27:b9:39;CM-QOS=1.0;CM-VER=3.0; 2016-12-15, 02:04:57 Critical (3) No UCDs Received - Timeout;;CM-MAC=a0:04:60:f5:19:a8;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; 2016-12-15, 02:05:01 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=a0:04:60:f5:19:a8;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; 2017-1-8, 12:33:56 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=a0:04:60:f5:19:a8;CMTS-MAC=00:24:c4:27:b9:39;CM-QOS=1.1;CM-VER=3.0; 2017-1-8, 12:34:32 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=a0:04:60:f5:19:a8;CMTS-MAC=00:24:c4:27:b9:39;CM-QOS=1.1;CM-VER=3.0; 2017-1-14, 18:19:38 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=a0:04:60:f5:19:a8;CMTS-MAC=00:24:c4:27:b9:39;CM-QOS=1.1;CM-VER=3.0; 1970-1-1, 00:00:37 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=a0:04:60:f5:19:a8;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; 1970-1-1, 00:00:44 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=a0:04:60:f5:19:a8;CMTS-MAC=00:24:c4:27:b9:39;CM-QOS=1.0;CM-VER=3.0; 2017-1-29, 15:34:59 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=a0:04:60:f5:19:a8;CMTS-MAC=00:24:c4:27:b9:39;CM-QOS=1.1;CM-VER=3.0; 1970-1-1, 00:00:37 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=a0:04:60:f5:19:a8;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; 1970-1-1, 00:00:41 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=a0:04:60:f5:19:a8;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; 1970-1-1, 00:01:11 Critical (3) No UCDs Received - Timeout;;CM-MAC=a0:04:60:f5:19:a8;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; 2017-3-11, 13:59:04 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=a0:04:60:f5:19:a8;CMTS-MAC=00:24:c4:27:b9:39;CM-QOS=1.1;CM-VER=3.0; 2017-3-11, 13:59:10 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=a0:04:60:f5:19:a8;CMTS-MAC=00:24:c4:27:b9:39;CM-QOS=1.1;CM-VER=3.0; 2017-3-11, 13:59:11 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a0:04:60:f5:19:a8;CMTS-MAC=00:24:c4:27:b9:39;CM-QOS=1.1;CM-VER=3.0; 1970-1-1, 00:00:37 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=a0:04:60:f5:19:a8;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; 1970-1-1, 00:00:41 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=a0:04:60:f5:19:a8;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; 1970-1-1, 00:02:55 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a0:04:60:f5:19:a8;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; 1970-1-1, 00:02:57 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=a0:04:60:f5:19:a8;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; 2017-3-11, 14:14:40 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=a0:04:60:f5:19:a8;CMTS-MAC=00:24:c4:27:b9:39;CM-QOS=1.1;CM-VER=3.0; 1970-1-1, 00:00:37 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=a0:04:60:f5:19:a8;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; 1970-1-1, 00:00:42 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=a0:04:60:f5:19:a8;CMTS-MAC=00:24:c4:27:b9:39;CM-QOS=1.0;CM-VER=3.0; 1970-1-1, 00:00:37 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=a0:04:60:f5:19:a8;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; 2017-3-28, 17:00:30 Critical (3) Resetting the cable modem due to docsDevResetNow 1970-1-1, 00:00:38 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=a0:04:60:f5:19:a8;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; 1970-1-1, 00:00:40 Notice (6) WiFi Interface [wl0] set to Channel 8 (Side-Band Channel:N/A) - Reason:INIT 1970-1-1, 00:00:40 Notice (6) WiFi Interface [wl1] set to Channel 149 (Side-Band Channel:N/A) - Reason:INIT 1970-1-1, 00:00:45 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=a0:04:60:f5:19:a8;CMTS-MAC=00:24:c4:27:b9:39;CM-QOS=1.0;CM-VER=3.0; 1970-1-1, 00:00:51 Notice (6) Honoring MDD; IP provisioning mode = IPv6 As mentioned in an earlier post - try a "hard reset" to re-establish the default settings and possibly correct some hidden fault that is affecting the operation.
The "hard reset" will also re-establish the MAC addresses for the Cable Modem (default on the nameplate), plus the MAC addresses for the LAN port and the INTERNET port. The later are sequental (in last 2 numbers) to the default Cable Modem MAC address. After the hard-reset, change the "default" login username and password for the Cable Modem (for security), and reset the Internet password(s) to those previoulsy used - this should allow all previously "attached devices" to connect. Leave all other settings alone until you can determine if the problem is corrected.
That isnt a fix. its a bandaide. root cause needs to be determined and addressed.
- junfitzGuide
Random Dropouts keep happening on my Netgear C7000. Has this been fixed yet? Looks like this problem has been happening for quite some time now. Did Netgear finally release a fix for this? For an expensive modem/router, we expect so much more from this.
- 8th_DayAspirant
Comcast has been on this for the last several weeks/months and can't find anything. However, their smallest test time is 5 minutes increments. But I may have stumbled on the issues. These statistics are for direct connect cable - computer to Router.
https://www.voipreview.org/speedtest
This site tests more than just upload and download speed. i tests for Latency/Ping
We use MagicJack. When we connect to a call, we loose the incoming voice for anywhere from 6 to 30 seconds. We just keep talking, though that is hard to do when it is an answering machine or robo menu. The tests explain what is happening. But I don't know where to go with this. Can't get to the right people at Comcast or Netgear.
When I ran this test the numbers in the beginning of the test were all over. It looked like an EKG and then it is steady. Something is happening at the beginning of the connection not only on the phone, but also when we go to other websites.
This was 7 PM
This was 7:15 PM
This was 7:15 PM This explains my MagicJack Phone issues
7:30 PM IP Phone and Skype are OK
is "UPnP" turned ON for both MagicJack and the Router?
Do MagicJack's settings allow selecting Incoming Ports? More than one?
These serttings will affect the performance of MagicJack, as well as other programs (Skype, etc.).
Skype's "Tools" include these types of settings. See "Tools/Options/Advanced/Connections".
- junfitzGuide
Seems like this problem hasn't been resolved. Yesterday, I called Netgear support and the person I spoke with, was confident that he could fix this problem. He said, some configurations in the settings need to be done and he's already done it for multiple people and fixed their problem. But the Catch is, i have to pay $49.99 for him to be able to tell me the correct configurations since I'm more than 90 days past the purchase date. Also, their 1 year warranty only covers Hardware Issues. I don't know about you but to me, if the product does not work, I consider it a hardware issue and should be taken care of by the company. We consumers deserve better support than your company policy offers.
Maybe Corporate needs to hear from FTC.gov first before they change their policy for resolving consumer's problems. It's ridiculous how Netgear policy would not allow their Tech Support to configure a $200 modem/router past 90 days from purchase date without having to pay an extra $49.99.
These random drops almost cost me my job. I was working from home one day, and i was working on moving a doctor's file from a VPN drive to another. Half way through the transfer, I lost internet connection for 5 minutes. Guess what happened to that file? Corrupted. Incomplete. Error. I'm glad I had a backup copy of that file because if I didn't, I would've lost my job and lawsuits against Netgear will be filed.
From "www.techrepublic.com":
Users successfully establish a VPN connection, but the connection periodically drops
There are a number of places you can check to try to nail down this problem. First, verify that your computer did not go into standby mode, hibernate, and that a screen saver did not pop up. Standby and hibernation can interrupt your network connection when the VPN client expects a constant link to a VPN server. You may also have configured your machine to shut down a network adapter after a certain amount of time in order to save power.
If wireless is in use, you may have wandered to a location with a low (or no) wireless signal (not the case here), and the VPN might have dropped as a result. Further, you might have a bad network cable, problem with their router or Internet connection, or any number of other physical connection problems.
Other Comments: Can you determine if the "disconnect" was from the PC to the wireless router, or was it from the internet source (cable) to the Modem? This would confirm whether the disconnect is an ISP problem or a Cable Modem/Router problem. The Unit's internal software (version number, etc.), can only be changed by the Manufacturer or the ISP provider. However, I suspect the the Customer Service person can only change the settings that are available to the end-user. You might have a setting that is not the best for a VPN connection - and this setting can be either on the Cable Modem/Router or the PC's WiFi Adpater. You may need to review these settings and "experiment". Again, before "experimenting", see if you can confirm where the disconnect occurs - at the modem or between the Router and PC. If you have a HardDrive connected to the Router and can access the HD but not the internet - then the problem is with the ISP and/or the Cable connection.
- mlawaljr1InitiateSo I've read most of the post on here because I was having the come problem as most of you. (Dropped service). I tried just about everything from changing dns settings to coming coaxial cables to troubleshooting with tech support to no avail. Finally I decided to go to my local Comcast and get a Comcast modem. Talked to the customer service representative for about 10mins and I discovered a few things with my specific problem. So he advised me to try and running the line from the pole directly to my modem (c7000). As I did what he suggested.......it worked!!! But that's not where my modem normally resides. So I went to Best buy and bought 25ft worth of coaxial cable and got to work. To make this story shorter..... My internet is back up and running again with normal speeds. What I think happened: when my internet was installed they used 2 splitters on the internet line. I moved the modem upstairs and I needed more line but didn't have long enough line. So I used more splitters without realizing they already had a few on that specific line. At first I didn't have any dropped signals then a month later everything went crazy. So I took all the splitters off and ran a direct line from pole to the modem. I reset my modem and then had Comcast resend a signal and now I don't have any more problems whatsoever. Like I said this is my personal experience but hopefully someone will benefit from my experience.
- drpnntgearAspirant
I have the same issue, and had them send me a brand new replacement, wich took 2 months of hoops and bull**bleep** to get, only to have the brand new device do the same. I didn't find this page until now, and they told me they had never had issues with this modem/router connecting or having t3 t4 t5 t6 errors and blammed it on my isp. I had the isp out 4 times checking my lines, and spectrum couldn't explain why it was happening. The artemis they gave me works and doesn't time out. So A) why would they claim not knowing about issues with this product since it has had issues dating back to 2016 with this exact problem, and why am I still trying to use it. We ALL should be reimbursed the $198.00 that we spent on this device, as it clearly does not work. They will be calling me back tomorrow, and I will let them know I have found this page and see what they say. I doubt I will see any money from this, sad cause I have used netgear products for well over 8 years. DONT BUY THIS DEVICE!
- drpnntgearAspirant
I have the same issue, and had them send me a brand new replacement, wich took 2 months of hoops to get, only to have the brand new device do the same. I didn't find this page until now, and they told me they had never had issues with this modem/router connecting or having t3 t4 t5 t6 errors and blammed it on my isp. I had the isp out 4 times checking my lines, and spectrum couldn't explain why it was happening. The artemis they gave me works and doesn't time out. So A) why would they claim not knowing about issues with this product since it has had issues dating back to 2016 with this exact problem, and why am I still trying to use it. We ALL should be reimbursed the $198.00 that we spent on this device, as it clearly does not work. They will be calling me back tomorrow, and I will let them know I have found this page and see what they say. I doubt I will see any money from this, sad cause I have used netgear products for well over 8 years. DONT BUY THIS DEVICE!
Certainly a frustrating problem. I had the same for several months, and needed to reboot to regain the connection and "contract speed" with the ISP. One reliable fix was to reboot the cable-modem. I decided that the issue was with the "modem" part of the C7000, and the fact that the ISP provider is in charge of updating the software (it does need to be compatible with the ISP's hardware). The current firmware version is v1.1.29, and this version works fine. I suspect that the cable feed gets corrupted from time to time as well - another source of connection issues. So, a reboot does help to restore the cable connection, identify the subscriber and establish the permitted speed, functionality, etc. I have 14 devices connected, 3 hardwire, 11 wi-fi; and use NeGear Genie to "control access" to the system. The combined "cable-modem" device sounds great, but separate units may be easier to troubleshoot and update (router in particular). However, in the past and using a separate modem unit, I did have problems with the ISP provider's firmware updates - and they did have to return to the a prior version for all endusers on the system. In conclusion - it's probably the modem part of the device (ISP and connection reliability, maybe the firmware version, etc.); and the only solution appears to be a reboot (automate with a timer) or get separate units to better isolate and solve the problem.