NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
N450/CG3000Dv2 WiFi drop and Interface Lockup
Last week Time Warner Cable pushed firmware V3.01.06 to my N450 modem/router. Since the update, i can't go more than 24 hours without having to pull the power because WiFi drops ALL devices. After the WiFi drop, the admin interface lags and locks up for ethernet connected devices. A power cycle is the only way to get normal operation restored.
I've called Time Warner, they blame Netgear
I've called Netgear, they want $80 just to talk to me about thier firmware update that broke my device which was previously working fine.
Somebody at Netgear needs to take ownership of this issue and address it ASAP. There are several reports all over this very discussion board citing the same exact problem. I've owned Netgear devices for 10+ years because of their quality. However, if this doesnt get addressed soon, i will never buy Netgear again.
NETGEAR - Please help! It's obvious that firmware v3.01.06 has a serious coding flaw.
I did a factory reset and have not been loosing connection for a few days. In the genie menu there is a place to backup your settings. After the reset you can restore the settings from the file you saved. The only thing it didn't restore was the user and password to access the router. The default is admin for user and password for password. Then you can sign in and change that. Still can't usb port to work.
77 Replies
MD585,
Could you please advise where you see such detailed messages.
I looked in the log using the web browser (Advanced tab, Administration -> Logs) and do not see much
except the messages saying when the modem was reset or when I log in to the web inteface.Still, with all due respect, why are we debugging this issue, this is a job for Netgear.
I think all the users should start putting pressure on Netgear and their ISP's.
Does anyone know how to reach Netgear's higher level support or some manager that can escalate this further. (any phone numbers ???)
These logs are under the "Event Logs" section under Administration.
"Logs" is for logging things like blocked sites, admin logins, and DDOS attacks.
All due respect taken, It does help NetGear to see these logs and see these complaints here from those who aren't under the 90 day "free" service. Personally I'm about to throw this thing out. I work from home and the 4 or 5 drops a day are not good, especially when on a webex conference call.
Did anyone else notice that IPv6 appears to be operating now with the 3.01.06 upgrade? I'm wondering if they intrroduced a bug with the dual stack operation, or worse, if the hardware is just incapable of actually running two IP stacks.
In any case, I'm pretty much doing a soft or hard reboot every day now. I guess it's time to look for a new modem, and it won't be a Netgear. I'm going to update my review on Amazon to warn folks away from this model.
MD585 - I completely agree with you under normal circumstances,
but it seems that neatgear is avoiding all the complaints, from the posts
I saw in this forum, I understand that this issue is going on for months
and they do NOTHING,
They blocked the option to change the firmware in the web interface
but it is probably still there, someone probably knows how to hack this thing,
and maybe has older v1 firmware, I'm sure once downgraded, this issue will go away.
People are starting to mention going to buy a different modem/router,
that is an option too, I would NEVER EVER buy netgear again after this experience
Also, maybe its time to involve some legal action, that might cause them to do something.
I am going to try submitting a support ticket at Netgear and see what comes of it. If the response is not what I'm looking for, I will be submitting a complaint to the FCC, a two-in-one for Netgear and TWC.
Bought my N450 in April. Also just got off the phone with Netgear support, and, like many others on this forum, first came the assurances that they could absolutely help me, if I'd only agree to pay $50. Not going to pay $50 for a $100 device which either they or TWC/Spectrum broke.
After a factory reset, the connectivity seems better, but my WiFi is about 1/4 the speed of wired Ethernet (yes, all devices, and have confirmed all settings).
I believe in California, the Attorney General takes these complaints, and I intend to make one.
N450 started to loose the connection right around summer month of 2016 due to the fact that it could not be configired for the accurate NTP time.
While the time on the connecting device would be accurate US Pacific Time, our device would how +8 hours. Staring 4:20 PM we would loose connection to most HTTPS - Google Doc, Dropbox, etc.
N450 is a malfunctioning device, NTP cannot ne configured, time cannot be configured. We suffered. Factory reset seemed to only help an every hour drop in wireless conections, every 4-5 PM was a droptime in most of HTTPS traffic.
I could not do my work at home. It was the majore hit.
The decesion was, after reading all this forum, is to go to Time Warner / Spectrum - since it is a leader in the area - and get another brand device. As of yesterday, we are no longer in the middle ages! Even in the developeing countries which I travelled for work I had a better connetcion than with this N450 Netgear devcie. I could not hack it, I could not get the proper support. I suffered. Our new device and the choice is to license at a monthly from the Time Warner / Spectrum - Ubee device, $10.00 a month. So far - righting this at 4:47 PM things are OK, first time in many weeks.
Never again with Netgear, so fed up.
I've been having the same problem for about the last week. I contacted TWC and they said all looked good from their end. I contacted Netgear and they wanted $159 to resolve the issue. It sounds like they know what the problem is but won't fix it without more $$$$$. I'm just waiting for ATT Directnow to become available and drop TWC and get another modem. Screw Netgear and TWC!!!
After being dumped to the menu in Destiny again not ten minute ago, I finally got fed up. I have filed a complaint with the FCC against Netgear and TWC. What really amped it up for me is when I saw the response on here that Netgear wanted to charge one of you $159 dollars to fix a problem THEY CREATED!!
Just found this on another forum.
going to try it
https://community.netgear.com/t5/Cable-Modems-Routers/Cg3000dv2-is-dropping-wifi/td-p/1157621
Tried that reset for now, but I don't know if it will *fully* solve the issue - I still believe there are faults in the latest firmware.
I did the factory reset this morning, looks good until now, I have some constant pings running and all have constant low latencies.
One thing though, if you have changed the configuration, then I suggest taking screen shots of the various windows/tabs in the web interface,
because after the factory reset, all is gone and has to be re-configured.
I saw that some of the configurations changed -like the names of the built in server (that allows you to plug in a usb drive and access it via the network),
I suspect that this was the issue all along.
Why hasn't netgear or even TWC have any page up sayings to factory reset this beyond me,
TWC are wasting technician time by sending them out, getting no results,
and Netgear greed, wanting charge top dollars to provide support for an issue they created, purposly avoiding to disclose important information
(these firmware changes are tested before roll out, so can't be naive and say, we didn't know)
This is the worst experience for a consumer, last time I buy anything from Netgear, and when I have a chance, I will get rid of TWC.
I know... Charging $159 to fix a problem with a $70 router is just insane.
Sounds like the same problem I've been having, only more severe. I posted about it here:
My connection is still usable and my WiFi still works, but takes several tries to log in to the web interface at 192.168.0.1, and every 15 to 20 seconds, I see a lag spike in which pings take 2000ms or more. I see it in the ping times on the LAN, no need to ping a site on the Internet. And I see all ping times get longer as the hours pass. Starts at 3ms after a fresh reboot, then decays to 16ms after 6 hours, 22ms after 12 hours, and 30ms after 24 hours of operation. Been going on for 2 to 3 weeks now. Interestingly, the diagnostics page, when I ping in the other direction from 192.168.0.1 to my PC, reports better ping times, but still not as good as they should be. This sure smells like a bug in the firmware, and I wanted to find out when it was last updated. My N450 is currently running 3.01.06.
I would revert to a previous version of the firmware if I could, but seems the N450 is programmed not to provide any means for the owner to do so. So far, I have not found any info on exactly when the firmware was last updated. That is totally unacceptable, Netgear. And charging us money, big money, for tech support? We're trying to help you guys figure out a problem you created. If anything, you should pay us!
I can work around the problem for now by rebooting the router every few hours, using the reboot button in Advanced Home in the web interface. Or if unable to log in, I can just power cycle the device. Takes me offline for half a minute, but restores ping times and performance to acceptable levels, for a few hours.
Here's the latest sample, pinging on a wire, after letting it stay up for 24 hours:
64 bytes from 192.168.0.1: icmp_seq=3 ttl=64 time=1021 ms
64 bytes from 192.168.0.1: icmp_seq=4 ttl=64 time=388 ms
64 bytes from 192.168.0.1: icmp_seq=5 ttl=64 time=237 ms
64 bytes from 192.168.0.1: icmp_seq=6 ttl=64 time=76.1 ms
64 bytes from 192.168.0.1: icmp_seq=7 ttl=64 time=35.5 ms
64 bytes from 192.168.0.1: icmp_seq=8 ttl=64 time=31.7 ms
64 bytes from 192.168.0.1: icmp_seq=9 ttl=64 time=378 ms
64 bytes from 192.168.0.1: icmp_seq=10 ttl=64 time=31.4 ms
64 bytes from 192.168.0.1: icmp_seq=11 ttl=64 time=227 ms
64 bytes from 192.168.0.1: icmp_seq=12 ttl=64 time=33.7 ms
64 bytes from 192.168.0.1: icmp_seq=13 ttl=64 time=387 ms
64 bytes from 192.168.0.1: icmp_seq=14 ttl=64 time=30.9 ms
64 bytes from 192.168.0.1: icmp_seq=15 ttl=64 time=31.4 ms
64 bytes from 192.168.0.1: icmp_seq=16 ttl=64 time=33.5 ms
64 bytes from 192.168.0.1: icmp_seq=17 ttl=64 time=71.5 ms
64 bytes from 192.168.0.1: icmp_seq=18 ttl=64 time=33.9 ms
64 bytes from 192.168.0.1: icmp_seq=19 ttl=64 time=5193 ms
64 bytes from 192.168.0.1: icmp_seq=20 ttl=64 time=4191 ms
64 bytes from 192.168.0.1: icmp_seq=21 ttl=64 time=3190 ms
64 bytes from 192.168.0.1: icmp_seq=22 ttl=64 time=2183 ms
64 bytes from 192.168.0.1: icmp_seq=23 ttl=64 time=1182 ms
64 bytes from 192.168.0.1: icmp_seq=24 ttl=64 time=183 ms
64 bytes from 192.168.0.1: icmp_seq=25 ttl=64 time=477 ms
64 bytes from 192.168.0.1: icmp_seq=26 ttl=64 time=131 ms
64 bytes from 192.168.0.1: icmp_seq=27 ttl=64 time=188 ms
64 bytes from 192.168.0.1: icmp_seq=28 ttl=64 time=33.1 ms
64 bytes from 192.168.0.1: icmp_seq=29 ttl=64 time=439 ms
64 bytes from 192.168.0.1: icmp_seq=30 ttl=64 time=99.7 ms
64 bytes from 192.168.0.1: icmp_seq=31 ttl=64 time=482 ms
64 bytes from 192.168.0.1: icmp_seq=32 ttl=64 time=31.6 ms
64 bytes from 192.168.0.1: icmp_seq=33 ttl=64 time=372 ms
64 bytes from 192.168.0.1: icmp_seq=34 ttl=64 time=31.7 ms
64 bytes from 192.168.0.1: icmp_seq=35 ttl=64 time=187 ms
64 bytes from 192.168.0.1: icmp_seq=36 ttl=64 time=62.5 ms
64 bytes from 192.168.0.1: icmp_seq=37 ttl=64 time=237 ms
64 bytes from 192.168.0.1: icmp_seq=38 ttl=64 time=81.8 ms
64 bytes from 192.168.0.1: icmp_seq=39 ttl=64 time=5344 ms
64 bytes from 192.168.0.1: icmp_seq=40 ttl=64 time=4648 ms
64 bytes from 192.168.0.1: icmp_seq=41 ttl=64 time=3655 ms
64 bytes from 192.168.0.1: icmp_seq=42 ttl=64 time=2665 ms
64 bytes from 192.168.0.1: icmp_seq=43 ttl=64 time=2043 ms
64 bytes from 192.168.0.1: icmp_seq=44 ttl=64 time=1051 ms
64 bytes from 192.168.0.1: icmp_seq=45 ttl=64 time=58.7 ms
64 bytes from 192.168.0.1: icmp_seq=46 ttl=64 time=243 ms
64 bytes from 192.168.0.1: icmp_seq=47 ttl=64 time=225 ms
64 bytes from 192.168.0.1: icmp_seq=48 ttl=64 time=30.9 ms
64 bytes from 192.168.0.1: icmp_seq=49 ttl=64 time=259 ms
64 bytes from 192.168.0.1: icmp_seq=50 ttl=64 time=43.4 ms
64 bytes from 192.168.0.1: icmp_seq=51 ttl=64 time=49.5 ms
64 bytes from 192.168.0.1: icmp_seq=52 ttl=64 time=38.9 ms
64 bytes from 192.168.0.1: icmp_seq=53 ttl=64 time=32.4 ms
64 bytes from 192.168.0.1: icmp_seq=54 ttl=64 time=46.7 ms
64 bytes from 192.168.0.1: icmp_seq=55 ttl=64 time=251 ms
64 bytes from 192.168.0.1: icmp_seq=56 ttl=64 time=33.6 ms
64 bytes from 192.168.0.1: icmp_seq=57 ttl=64 time=248 ms
64 bytes from 192.168.0.1: icmp_seq=58 ttl=64 time=31.9 ms
64 bytes from 192.168.0.1: icmp_seq=59 ttl=64 time=30.8 ms
64 bytes from 192.168.0.1: icmp_seq=60 ttl=64 time=5251 ms
64 bytes from 192.168.0.1: icmp_seq=61 ttl=64 time=4250 ms
64 bytes from 192.168.0.1: icmp_seq=62 ttl=64 time=3249 ms
64 bytes from 192.168.0.1: icmp_seq=63 ttl=64 time=2248 ms
64 bytes from 192.168.0.1: icmp_seq=64 ttl=64 time=1247 ms
64 bytes from 192.168.0.1: icmp_seq=65 ttl=64 time=246 ms
64 bytes from 192.168.0.1: icmp_seq=66 ttl=64 time=255 ms
64 bytes from 192.168.0.1: icmp_seq=67 ttl=64 time=154 ms
64 bytes from 192.168.0.1: icmp_seq=68 ttl=64 time=39.0 ms
64 bytes from 192.168.0.1: icmp_seq=69 ttl=64 time=97.3 ms
64 bytes from 192.168.0.1: icmp_seq=70 ttl=64 time=33.6 ms
64 bytes from 192.168.0.1: icmp_seq=71 ttl=64 time=72.9 ms
64 bytes from 192.168.0.1: icmp_seq=72 ttl=64 time=31.4 ms
64 bytes from 192.168.0.1: icmp_seq=73 ttl=64 time=149 ms
64 bytes from 192.168.0.1: icmp_seq=74 ttl=64 time=31.5 ms
64 bytes from 192.168.0.1: icmp_seq=75 ttl=64 time=50.8 ms
64 bytes from 192.168.0.1: icmp_seq=76 ttl=64 time=47.0 ms
64 bytes from 192.168.0.1: icmp_seq=77 ttl=64 time=205 ms
64 bytes from 192.168.0.1: icmp_seq=78 ttl=64 time=36.9 ms
64 bytes from 192.168.0.1: icmp_seq=79 ttl=64 time=93.2 ms
64 bytes from 192.168.0.1: icmp_seq=80 ttl=64 time=5740 ms
64 bytes from 192.168.0.1: icmp_seq=81 ttl=64 time=4740 ms
64 bytes from 192.168.0.1: icmp_seq=82 ttl=64 time=3741 ms
64 bytes from 192.168.0.1: icmp_seq=83 ttl=64 time=2745 ms
64 bytes from 192.168.0.1: icmp_seq=84 ttl=64 time=1744 ms
64 bytes from 192.168.0.1: icmp_seq=85 ttl=64 time=744 ms
64 bytes from 192.168.0.1: icmp_seq=86 ttl=64 time=679 ms
64 bytes from 192.168.0.1: icmp_seq=87 ttl=64 time=402 ms
^C
--- 192.168.0.1 ping statistics ---
87 packets transmitted, 85 received, 2% packet loss, time 86225ms
rtt min/avg/max/mdev = 30.845/957.651/5740.519/1556.881 ms, pipe 6Pinging 192.168.0.4 with 64 of data:[In progress]
Reply from 192.168.0.4: bytes = 64, time = 35 ms
Reply from 192.168.0.4: bytes = 64, time = 9 ms
Reply from 192.168.0.4: bytes = 64, time = 32 ms
Reply from 192.168.0.4: bytes = 64, time = 133 ms
Reply from 192.168.0.4: bytes = 64, time = 35 ms
Reply from 192.168.0.4: bytes = 64, time = 32 ms
Reply from 192.168.0.4: bytes = 64, time = 9 ms
Reply from 192.168.0.4: bytes = 64, time = 32 ms
Reply from 192.168.0.4: bytes = 64, time = 32 ms
Reply from 192.168.0.4: bytes = 64, time = 11 ms
Reply from 192.168.0.4: bytes = 64, time = 34 ms
Reply from 192.168.0.4: bytes = 64, time = 46 ms
Reply from 192.168.0.4: bytes = 64, time = 21 ms
Reply from 192.168.0.4: bytes = 64, time = 9 ms
- Just purchase a wireless router for $20 and hook up
It's been two days since I reset to factory defaults and reconfigured. So far my network connection to the CATV system has been stable as far as I can tell. (No outliers in pings to the Internet, speed seems normal, no connectivity issues I can trace to the modem.) My access to the GUI has worked consistently. I have never used the WIFI, so I turned it off as part of the reset/reconfigure process.
As far as pinging from the Genie diagnostics page goes, it is definitely buggy. If I ping a local PC, it reports no replies even though I can see the pings and replies on the PC in tcpdump. If I ping out to the Internet Genie reports timeouts but nothing shows up on the outside system. I can ping the outside system from the PC with no problems.
I am connected to TWC or whatever they call themselves these days.
- I too am having this problem. I spent about 2 hours one day dealing with TWC and trying various things. When I talked to the Level 2 tech from TWC I was informed that the firmware updates get pushed from the backbone down to the device. So if the engineers decide that the V3.01.06 firmware is what the backbone is going to run off of then there is no way around it. You can do a factory reset if you want but it will pull down V3.01.06 again. I pointed out to him that the V3.01.06 firmware is shown as the Comcast configuration for the N450 (http://kb.netgear.com/app/answers/detail/a_id/25477/~/current-firmware-version-for-netgear-cable-modem-routers) but it didn't make a difference. Unfortunately, the N450 doesn't have an option to do standalone firmware update. The tech I spoke with gave me the option to do a full replace or get a wireless router and attach it to my modem. Guess I will have to get another brand of modem...
Mine is still working since I did the factory reset and is using the v3.01.06 firmware. I'm impressed that you at least spoke with a tech at TWC that understood that they (not Netgear push the firmware out). The last person I spoke with did say that there is no more TWC and they are in the process of moving everyone over to Spectrum (which they already did with my account). Since someone else on the forum confirmed that Comcast and Spectrum also merged, I suspect that is why they are using the Comcast firmware, although I am still waiting for a response from them to confirm that. It seems they obviously didn't work out all the bugs before they merged or transferred systems, but anyway, mine has been reliable and with faster Spectrum speeds for 6 days now since the reset. I did also do this after I received and email from TWC stating that my account is now Spectrum and with faster speeds. If the resets hasn't worked for some, maybe they need to confirm that Spectrum has transferred everything from TWC in their area and on their account. Not sure how all that works though.
Met Too! Hard reset worked for me and my daughter. We both have the same modem.
About a day after I did the hard reset, it was back to its old tricks again. I had already scheduled a tech visit (Spectrum reached out to me after the FCC contacted them) for this Friday, so I just kept up with the power cycling. Tier 3 tech came out, checked *ALL* the connections (both inside, and out in the distribution box). He replaced my cheaper splitter with a much better one which helped to even out the TV signal a bit, and the internet signal some, but it still has the latency issue that is only resolved by power cycling at least once a day. TWC also confirmed that *THEY DO NOT PUSH THE FIRMWARE* , and that Netgear has a habit of pushing firmware without notifying TWC - at all. TWC had an issue about a year ago with Netgear C600 modems, but with that one when Netgear pushed the firmware they actually bricked the modems. Both that time and with this issue, TWC has contacted Netgear numerous times and has yet to hear back from them. Netgear is aware of this issue, and is sitting around with their thumb up their ass. I for one will most likely purchase a new modem/router from a *different* manufacturer as soon as I can afford it!
I reset to factory a week ago and had last power cycled the modem on Friday. This morning I cannot get into the GUI. In the past power cycling the modem fixed this. Not this time. Power cycled twice, cannot get in. Been trying variations on the password with no effect. It hasn't reset to factory again because my configured LAN IP is still there.
Maybe it's time to try using it as a modem only and go back to my old router. Will never buy Netgear again.
So while I was getting ready to put another router behind the N450, I kept trying to log in and finally discovered that Genie simply doesn't like Firefox. I can't log in with Firefox from Linux or Win 10. I can log in with Edge. Not sure why it's worse now, but I've been having problems ever since the upgrade.
So, that "turn NAT off" really does seem to turn the box into a bridge instead of a router. I have the public IP on the router behind the N450 now. I had to move some connections around so nothing else is connected to the N450, and afterwards some of my computers were a little slow, but resetting their network connections or rebooting got them to get their IP from the new DHCP server, which was probably the problem (my router has a pretty heavy-duty firewall built in, so that may have been the real issue).
Still wondering if I should buy another modem anyway...
I am also having this issue, I narrowed it down to that firmware as well before I found this thread. I have spoke to TWC about this issue they are not willing to do anything useful to help me.
Really frustrating as an IT guy who has been purchasing netgear products and recommending them to people for several years. Will not make that mistake again.