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
Thanks for posting.
We are having the same problem
Netgear please provide assistance .
Agree. Having same issue all week. It is a ridiculous policy to charge for support on a product, expecially one that is still under warranty.
- I got the same issue with same n450 cable modem/router. Probably they want us to pay for tech support.
I am having the same prolems as far as cable connectivity since TWC pushed the 3.01.06 code. I can't answer to the WIFI issue because I use a different box for WIFI and have it turned off on the N450. But since the upgrade my perfectly stable cable connection some days kills my VOIP phone calls over and over, sometimes just drops the cable connection, and sometimes won't let me log in to check what is going on. The fix is always to power cycle the modem.
This firmware is buggy and Netgear needs to fix it.
I am having the same problems starting about 4-5 days ago. The first thing I did was contact TWC, they said everything looked good on their end but the sent me the firmware update, still having the same problem though.
Obviously there is something going on with the N450's as there are numerous posts about it on here, and they all started happening about the same time. Any suggestions? i have tried changing channels and power cycling the machine but nothing works :/
I have TWC and have had repeated internet connection drops since V3.01.06 firmware was pushed. TWC is clueless and NETGEAR either doesn't care or doesn't know what to do to correct the problem. It's unfortunate because I've been happy with the cable modem but will be switching back to Linksys.
I have the exact same issues as the rest of the posters in this thread! I at first thought it was the remote access client on my wife's laptop cache-flooding the modem that was causing it to need the power cycle, and was going to take troubleshooting steps with that (I work in Online Support at a bank, I troubleshoot all day). Turns out after a bit of poking about online, I don't need to do that. It boils down to exactly what I thought the issue to be to begin with: the F***ING firmware that was pushed to the modem. TWC swears up and down they only push bootfiles, and that NETGEAR flashes the firmware. Netgear needs to own up to their f***up and push an incremental update for the firmware that fixes whatever redundant code that is causing the cache flooding. I say cache flooding because the symptoms experienced with this are identical to being DDoS'ed. (I got DDoS'ed out of Destiny once by an opponent, first and last time I tried Lag of Osiris!).
I have the same problem exactly. Finally turned off the wireless and connected a cheap tp link router for wireless
Hello,
This issue is happening to me too, have N450 and I'm a TWC customer
This is affecting all conectivity in the modem (wired and wifi).
This happend after someone (TWC or Netgear) pushed firmware 3.01.06
and it started about 10 days ago
Try to reset the modem and initiate a constant ping 'ping XXX.XXX.XXX.XXX -t'
After reset you should see regular latency numbers, as time goes by you will notice
that every 16 packet, the latency is much higher, if you leave the modem without restarting
for more then a day you might see 3000+ ms latency for something that is usually 30+ ms
Here is a constant ping to one of the servers (about 8 hours after restarting the modem) :
Reply from 24.93.40.116: bytes=32 time=31ms TTL=247
Reply from 24.93.40.116: bytes=32 time=46ms TTL=247
Reply from 24.93.40.116: bytes=32 time=29ms TTL=247
Reply from 24.93.40.116: bytes=32 time=23ms TTL=247
Reply from 24.93.40.116: bytes=32 time=20ms TTL=247
Reply from 24.93.40.116: bytes=32 time=69ms TTL=247
Reply from 24.93.40.116: bytes=32 time=23ms TTL=247
Reply from 24.93.40.116: bytes=32 time=45ms TTL=247
Reply from 24.93.40.116: bytes=32 time=32ms TTL=247
Reply from 24.93.40.116: bytes=32 time=23ms TTL=247
Reply from 24.93.40.116: bytes=32 time=24ms TTL=247
Reply from 24.93.40.116: bytes=32 time=56ms TTL=247
Reply from 24.93.40.116: bytes=32 time=1361ms TTL=247
Reply from 24.93.40.116: bytes=32 time=26ms TTL=247
Reply from 24.93.40.116: bytes=32 time=22ms TTL=247
Reply from 24.93.40.116: bytes=32 time=31ms TTL=247
Reply from 24.93.40.116: bytes=32 time=23ms TTL=247
Reply from 24.93.40.116: bytes=32 time=21ms TTL=247
Reply from 24.93.40.116: bytes=32 time=22ms TTL=247
Reply from 24.93.40.116: bytes=32 time=23ms TTL=247
Reply from 24.93.40.116: bytes=32 time=31ms TTL=247
Reply from 24.93.40.116: bytes=32 time=20ms TTL=247
Reply from 24.93.40.116: bytes=32 time=19ms TTL=247
Reply from 24.93.40.116: bytes=32 time=23ms TTL=247
Reply from 24.93.40.116: bytes=32 time=25ms TTL=247
Reply from 24.93.40.116: bytes=32 time=40ms TTL=247
Reply from 24.93.40.116: bytes=32 time=24ms TTL=247
Reply from 24.93.40.116: bytes=32 time=29ms TTL=247
Reply from 24.93.40.116: bytes=32 time=1293ms TTL=247
Reply from 24.93.40.116: bytes=32 time=46ms TTL=247
Reply from 24.93.40.116: bytes=32 time=43ms TTL=247
Reply from 24.93.40.116: bytes=32 time=42ms TTL=247
Reply from 24.93.40.116: bytes=32 time=26ms TTL=247
Reply from 24.93.40.116: bytes=32 time=21ms TTL=247
Reply from 24.93.40.116: bytes=32 time=31ms TTL=247
Reply from 24.93.40.116: bytes=32 time=23ms TTL=247
Reply from 24.93.40.116: bytes=32 time=25ms TTL=247
Reply from 24.93.40.116: bytes=32 time=25ms TTL=247
Reply from 24.93.40.116: bytes=32 time=29ms TTL=247
Reply from 24.93.40.116: bytes=32 time=26ms TTL=247
Reply from 24.93.40.116: bytes=32 time=38ms TTL=247
Reply from 24.93.40.116: bytes=32 time=22ms TTL=247
Reply from 24.93.40.116: bytes=32 time=24ms TTL=247
Reply from 24.93.40.116: bytes=32 time=19ms TTL=247
Reply from 24.93.40.116: bytes=32 time=1304ms TTL=247
Reply from 24.93.40.116: bytes=32 time=22ms TTL=247
Reply from 24.93.40.116: bytes=32 time=23ms TTL=247
Reply from 24.93.40.116: bytes=32 time=24ms TTL=247
Reply from 24.93.40.116: bytes=32 time=24ms TTL=247
Reply from 24.93.40.116: bytes=32 time=21ms TTL=247
Reply from 24.93.40.116: bytes=32 time=52ms TTL=247
Reply from 24.93.40.116: bytes=32 time=43ms TTL=247
Reply from 24.93.40.116: bytes=32 time=29ms TTL=247
Reply from 24.93.40.116: bytes=32 time=25ms TTL=247
Reply from 24.93.40.116: bytes=32 time=17ms TTL=247
Reply from 24.93.40.116: bytes=32 time=44ms TTL=247
Reply from 24.93.40.116: bytes=32 time=25ms TTL=247
Reply from 24.93.40.116: bytes=32 time=25ms TTL=247
Reply from 24.93.40.116: bytes=32 time=19ms TTL=247
Reply from 24.93.40.116: bytes=32 time=20ms TTL=247
Reply from 24.93.40.116: bytes=32 time=1386ms TTL=247
Reply from 24.93.40.116: bytes=32 time=94ms TTL=247
Reply from 24.93.40.116: bytes=32 time=62ms TTL=247
Reply from 24.93.40.116: bytes=32 time=20ms TTL=247
Reply from 24.93.40.116: bytes=32 time=32ms TTL=247
Reply from 24.93.40.116: bytes=32 time=25ms TTL=247
Reply from 24.93.40.116: bytes=32 time=22ms TTL=247
Reply from 24.93.40.116: bytes=32 time=17ms TTL=247
Reply from 24.93.40.116: bytes=32 time=19ms TTL=247
Reply from 24.93.40.116: bytes=32 time=19ms TTL=247
Reply from 24.93.40.116: bytes=32 time=17ms TTL=247
Reply from 24.93.40.116: bytes=32 time=27ms TTL=247
Reply from 24.93.40.116: bytes=32 time=18ms TTL=247
Reply from 24.93.40.116: bytes=32 time=19ms TTL=247
Reply from 24.93.40.116: bytes=32 time=23ms TTL=247
Reply from 24.93.40.116: bytes=32 time=25ms TTL=247
Reply from 24.93.40.116: bytes=32 time=1570ms TTL=247
Reply from 24.93.40.116: bytes=32 time=38ms TTL=247
Reply from 24.93.40.116: bytes=32 time=20ms TTL=247
Reply from 24.93.40.116: bytes=32 time=24ms TTL=247
Reply from 24.93.40.116: bytes=32 time=20ms TTL=247
Reply from 24.93.40.116: bytes=32 time=26ms TTL=247
Reply from 24.93.40.116: bytes=32 time=19ms TTL=247
Reply from 24.93.40.116: bytes=32 time=20ms TTL=247
Reply from 24.93.40.116: bytes=32 time=27ms TTL=247
Reply from 24.93.40.116: bytes=32 time=25ms TTL=247
Reply from 24.93.40.116: bytes=32 time=25ms TTL=247
Reply from 24.93.40.116: bytes=32 time=25ms TTL=247
Reply from 24.93.40.116: bytes=32 time=75ms TTL=247
Reply from 24.93.40.116: bytes=32 time=51ms TTL=247
Reply from 24.93.40.116: bytes=32 time=36ms TTL=247
Reply from 24.93.40.116: bytes=32 time=20ms TTL=247
Reply from 24.93.40.116: bytes=32 time=1383ms TTL=247
Reply from 24.93.40.116: bytes=32 time=28ms TTL=247
Reply from 24.93.40.116: bytes=32 time=41ms TTL=247
Reply from 24.93.40.116: bytes=32 time=30ms TTL=247
Reply from 24.93.40.116: bytes=32 time=23ms TTL=247
Reply from 24.93.40.116: bytes=32 time=18ms TTL=247
Reply from 24.93.40.116: bytes=32 time=28ms TTL=247
Reply from 24.93.40.116: bytes=32 time=70ms TTL=247
Reply from 24.93.40.116: bytes=32 time=22ms TTL=247
Reply from 24.93.40.116: bytes=32 time=17ms TTL=247
Reply from 24.93.40.116: bytes=32 time=21ms TTL=247
Reply from 24.93.40.116: bytes=32 time=21ms TTL=247
Reply from 24.93.40.116: bytes=32 time=21ms TTL=247
Reply from 24.93.40.116: bytes=32 time=23ms TTL=247
Reply from 24.93.40.116: bytes=32 time=25ms TTL=247
Reply from 24.93.40.116: bytes=32 time=27ms TTL=247
Reply from 24.93.40.116: bytes=32 time=1562ms TTL=247
Reply from 24.93.40.116: bytes=32 time=21ms TTL=247
Reply from 24.93.40.116: bytes=32 time=27ms TTL=247
Reply from 24.93.40.116: bytes=32 time=24ms TTL=247
Reply from 24.93.40.116: bytes=32 time=25ms TTL=247
Reply from 24.93.40.116: bytes=32 time=19ms TTL=247
Reply from 24.93.40.116: bytes=32 time=19ms TTL=247EXACTLY every 16 packets there is a much bigger latency.
Smells like a software issue.
I started seeing messages about this at the end of last month, probably someone initiated
this push, but I see that this issue has been going on for months from the posts here.
TWC says they don't push firmware updates to customer modems, and Netgear says
only TWC can push the firmware
TWC and NETGEAR - stop blaiming each other, take responsibility and fix this issue !!!
Folks, I suggest that if you want this resolved, start making noise in both companies.
I, too, am having the same difficulties. I just bought the modem/router and TWC installed it when they installed my service. I thought it was just me, but after seeing this message board, I'm not the one who is the problem. Nothing but trouble. I'm going to return it since support is practically non-existant, and can I please speak to someone whose first language is English???
Same problem here. TWC must be flooded with calls on this issue, and yet they are totally unaware and just blame customer-owned equipment when called. Nice to see the problem with recent firmware update so well-documented here, but Netgear and TWC don't seem to be acknowledging the problem or doing anything about it.
same issue here. since about two weeks ago. dropping internet and wifi connection 2-3 times a day.
Me too! same issue here. since atleast two weeks ago. Dropping wifi connection 2-3 times a day. Ethernet works fine.
I would be happy if it could just be reflashed back to the old firmware. Never had problems before this.
I'm having the EXACT same issue. The only difference is it was happening BEFORE the upgrade to V3.01.06 2 weeks ago. But then it was just one day a week (throughout the whole day... but still)
Since the upgrade from v1.00.05 to V3.01.06 it happens multiple times a day, everyday.
My Event Logs get filled with this when it happens.
(I've cleared my MAC addresses for privacy)
2016-11-03, 08:26:33.0 Error (4) Missing BP Configuration Setting TLV Type: 17.9;CM-MAC=00:00:00:00:00:00;CMTS-MAC=00:01:00:01:00:01;CM-QOS=1.1;CM-VER=3.0; 2016-11-03, 08:26:32.0 Error (4) Missing BP Configuration Setting TLV Type: 17.8;CM-MAC=00:00:00:00:00:00;CMTS-MAC=00:01:00:01:00:01;CM-QOS=1.1;CM-VER=3.0; 2016-11-03, 04:36:15.0 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=00:00:00:00:00:00;CMTS-MAC=00:01:00:01:00:01;CM-QOS=1.1;CM-VER=3.0; 2016-11-03, 03:13:06.0 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:00:00:00:00:00;CMTS-MAC=00:01:00:01:00:01;CM-QOS=1.1;CM-VER=3.0; Time Not Established Warning (5) DHCP WARNING - Non-critical field invalid in response ;CM-MAC=00:00:00:00:00:00;CMTS-MAC=00:01:00:01:00:01;CM-QOS=1.0;CM-VER=3.0; Time Not Established Notice (6) Honoring MDD; IP provisioning mode = IPv4 Time Not Established Notice (6) WiFi Interface [wl0] set to Channel 11 (Side-Band Channel:N/A) - Reason:INIT I've talked to some corporate DNS/DHCP/Router folks I work with and they said "Check to see if you're NTP Time Server setting is messed up..."
Well, guess what? In V1.00.05 You could set the NTP Service, and in V3.01.06 you can't!
That missing BP line and the Timeout error looks like a borked preamble or announce line in the code.