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 ...
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.
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=247
EXACTLY 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.