N450 WiFi keeps disconnecting

[tomlyu]

Same issue here, I called TWC and they sent a technician to my house, made several phone calls, and said they didn't update my device... My N450 firmware version currently is v3.01.06, I got this update 3 days ago, after that my WIFI signal was crap

[rmctodd]

I faced this problem several months ago and I used a different router with this modem. Now I'm trying to debug this and I find the same issues described here.

- The wifi connection dies on almost all devices

- The wired connection is fine

- On changing the wifi channel (after connecting using wire), the wifi works for some time and usually within a few hours, it is down again.

Does netgear have a solution or a firmware upgrade planned? Will comcast deploy it?

I'm using the latest firmware version: 3.01.06

I've been using this for 2 years now (although I've had this problem for several months). I'm pretty disappointed that this hasn't been solved even though many people are reporting this issue.

[bakingsoda]

What is the second router you use to test with? 

I'm also having the same issue with my N450 with Time Warner.  Only started noticing the issue recently.  On TWC's site (Should I Lease or Buy a Modem page -> Download speeds up to 100Mbps section), the N450 is grayed out and listed as an "Internet Modem Only".  TWC is probably trying to force us to an upgrade and make it seem like there is an issue with our hardware.  Obviously this is not just an "Internet Modem Only".

https://www.timewarnercable.com/en/support/internet/topics/lease-or-buy-modem.html

[rmctodd]

Hi:

I used a Linksys WRT54G router which is an old router.

I should add that this one was working well for a year and I suspect that a firmware upgrade ruined it. This is not just a modem.

[tomlyu]

Called TWC several times today, they insisted that the firmware update was pushed out by Netgear, who we can trust?

[DarrenM]

Hello Tomlyu

All cable modem firmware is pushed out by the ISP we make the firmware then send it to the ISP they make any changes they feel necessary and then push out the firmware to the modems.

http://kb.netgear.com/app/answers/detail/a_id/25477?cid=wmt_netgear_organic

DarrenM

[tomlyu]

Hi Darren,
Thanks for replying.
I checked the link in your post, it suggests that the firmware version for my N450 should be v1.00.05 but the actual version is v3.01.06

Do you mean Netgear gave a wrong baseline firmware to TWC or TWC pushed out a wrong version of firmware?

[DarrenM]

Hello Tomlyu

Which firmware version is your modem on?

DarrenM

[tomlyu]

Hi Darren,

It's V3.01.06 now.

Thanks

[DarrenM]

The article must me wrong that is the latest firmware.

DarrenM

[tomlyu]

Hi Darren,

Let me understand what you're saying here:

1. Netgear provide original firmware source code to TWC, within the original firmware, the WIFI signal is set to "Strong" or "Normal";

2. TWC deliberately modified the firmware, and compiled the modified source code, then pushed the firmware binary file to customer's N450 device;

3. After the firmware update, the customer's device has really weak WIFI signal, and customer cannot change the signal strength settings, but Netgear has nothing to do with this issue.

Am I right?

Thanks

[DarrenM]

Hello tomlyu

What you said is a total possibility I will have to check and see if that has happened with this device on that firmware.

DarrenM

[bobbye]

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.

[tomlyu]

Totally agree with you, we need to make more noise to be heard...

Btw, here is the so called "tier 3" tech support number of TWC: 718-358-0900

One of their excuse was: if we pushed out wrong firmware we should have seen many complaints now...

[aniorange]

I came here looking for help because I have had the same issue. We have had the N450 just over a year and it worked fine until about a month ago. Then the wireless started becoming a problem. Computers were connected but had no internet and the only solution was to restart the N450. This happeded every few days. The past 3 days, the speed has been horrible. The disconects are getting worse. I see that this is a issue for many others and the blame is being tossed around. I chose Netgear because I have been satisfied with Netgear products in the past, but it looks like it's time to abandon Netagear and look elsewhere. One of my roomates works from home and this just will not do. We need a solution.

[craigwf]

After installing the third N450, it has now gone six months without losing wifi connectivity.  I suspect a major batch came out with hardware faults and sympathize with those of you whose problem didn't occur until after the warranty expired.  If you are one of those, I suggest you try a new and different model if you can afford it.  Until you get one without the fault, the problem recurrs despite all other efforts on yours, Netgear tech support or your isp's part to fix it.  If my modem/router starts doing it again, I will not hesitate to shop for a new one, not an N450.

[bobbye]

craigwf - from what I read you're on Comcast,is that correct ?

Also, from other responses about this issue, I understnd that the ISP's have ccess to the firmware source code,

I thought that maybe TWC has some bug, but if this is happening also with Comcast,

then I suspect the bug is in the Netgear code.

I just can't beleive that Netgear has avoided this issue for months, and now that TWC has pushed the faulty vrsion

(althoguh they will not admit it), they also, have to be responsible for fixing this.

THIS IS A NETGEAR FORUM, WHEE IS THE NETGEAR REPRESANTATIVE ????

PLEASE ADVISE AS TO WHAT IS DONE ABOUT THIS SERIOUS ISSUE

[aniorange]

I neglected to mention I am also a TWC subscriber. I am thinking that perhaps I should pick up a seperate modem and router, that way any firmware upgrades do not impat the wireless protion. I am also thinking of puchasing one that I know they use. Before I moved I rented a Surfboard modem router combo that worked great except for the occasional hiccup. It would occasional drop signal but right itself after a minute. The Netgear has to be unplugged.

[aniorange]

I should also add that we have one computer hooked in directly. It can still connect when these issues occur, but it slows down.

[invalidation]

I'm also having this problem - it started when TWC Pushed the firmware to v3

Wifi appears to "lock" daily - it gets slow then fails to operate. The v1 firmware worked without issue.

[rakstemp]

Just adding to the forum, having the same issue...

WHERE ARE THE NETGEAR REPS THERE HAVE BEEN NO ANSWERS!!!

I really feel netgear is just avoiding the issue..

I'm postive there are tons of customer with the same issue that just have not posted to the fourm..

[player1]

I have the exact same problem! Just made an account so I can reply here.. Ping jumps on all my devices also internet gets slower the longer my router is turned on. Turning it on and off solves all these problems until 1-2 hours later i start noticing it getting slower again. After 1 day I usually cant even use it anymore(250mbps download speed goes down to 1mbps...).

Guess I have to get a new router.

[bobbye]

Has any of the folks here contacted TWC or Netgear and managed to make some progress ?

Also, I see that it is not recommended to buy a device that is both modem and router as the N450,

any one has any advice which modems and routers might be decent replacments (of course not Netgear) ?

[invalidation]

Yeah, I think I've learned my lesson on this one.  Between TWC / Spectrum and Netgear, I don't expect this to be resolved in any reasonable time -- even if Netgear has a fix, they'll have to convince TWC to implement and push it.

Why the wireless firmware wasn't decoupled from the cable modem in this package is beyond me.

I'll see if I can just disable the wireless on this and buy a separate access point for the wireless.  At least the switch and cable modem in this aren't broken (yet).

[invalidation]

player1: test the speeds across the wired switch.  If we're having the same problem, chances are you're getting full speed there, even after the wireless completely stops working.  Seems to just be the wireless set in the device.  May be possible to salvage some part of it buy just disabling the interal AP, and buying a separate wireless device.