NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
bramschats1
Apr 22, 2011Aspirant
[WNAP210] fail to access after a while
Hello, I have a WNAP210 access point and it is working very well, except for one strange thing. I usually have 1 or 2 clients connected to the access point but every three weeks i have to reboot...
boatbodger
Oct 16, 2013Tutor
I too have a WNAP210 and it was working fine for 8 or 9 months. I too have been using firmware 2.0.27 as 2.1.1 has a problem with web pages.
Then - after a power outage - I found all Windows clients were saying "Attempting to authenticate". The device is PoE powered, and the LAN switch was not damaged by the outage, and neither were any other electrical items in the house.
Simply rebooting the device did not clear the problem.
I then did a factory reset (which was hard - you have to hold the button in for nearly a minute - not the 5 seconds the user manual suggests), then reconfigured it from scratch, after which it worked fine.
Until we had another outage - the same symptoms have reappeared.
I've tried changing the authentication method, including changing the passphrase (in case that was somehow corrupted in memory) - no luck.
Just upgraded to 2.1.1. I made sure there was a valid DNS configured, and this seems to have sped up the config web pages. And the unit is now talking to clients again.
Given that this unit is supposedl "top end", it still seems very buggy.
Then - after a power outage - I found all Windows clients were saying "Attempting to authenticate". The device is PoE powered, and the LAN switch was not damaged by the outage, and neither were any other electrical items in the house.
Simply rebooting the device did not clear the problem.
I then did a factory reset (which was hard - you have to hold the button in for nearly a minute - not the 5 seconds the user manual suggests), then reconfigured it from scratch, after which it worked fine.
Until we had another outage - the same symptoms have reappeared.
I've tried changing the authentication method, including changing the passphrase (in case that was somehow corrupted in memory) - no luck.
Just upgraded to 2.1.1. I made sure there was a valid DNS configured, and this seems to have sped up the config web pages. And the unit is now talking to clients again.
Given that this unit is supposedl "top end", it still seems very buggy.