NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
RSchwein
Mar 21, 2011Aspirant
WNDAP350's are constantly rebooting
WNDAP350 significant problems I have 5 of these on various network segments over a large geographical area. All are using different wiring, different network switches, nothing in common with any o...
JimiSweden
Oct 25, 2011Aspirant
This is my version of the story. (fw 2.0.9)
I have got 5 pieces of those WNDAP350 and also a manager, WMS5316.
The price and specification is attractive but I would never recommend them until the firmware is stable (I actually would never recommend Netgear stuff to a business that can afford Cisco stuff, but switches works good enough for low capacity networks). The configuration via GUI is slow and not always logical.
Problems so far:
When upgraded to latest firmware on WMS (2.1.2) and APs (2.0.27) New APs could not be added to WMS.
Downgrade of all units solved this problem. (WMS 2.0.3, AP 2.0.9)
All five (5) units have had problems with losing the connectivity to the LAN, WLANs are up but Internet Access is lost. When connectivity from AP to internet is lost I cannot ping the LAN interface.
I also have statistics from Cacti showing that the problem most often appear during business hours, but not always.
First I thought that my POE switch (dlink 1316 poe) didn’t provide enough output power but after removing 4 of the APs from the POE switch and putting them in to different switches on both access and distribution layers I still have the same issues. Even when turning of the G-band and running only on A-band the Aps are having problems.
(I realize now that I haven’t turned off the A band on all Aps, next step..)
Next step is to upgrade the APs again and run them without the WMS
Why? Because the WMS will not be able to find the APs unless they are factory reset and in the default network 192.168.0.0 /24.
I have got 5 pieces of those WNDAP350 and also a manager, WMS5316.
The price and specification is attractive but I would never recommend them until the firmware is stable (I actually would never recommend Netgear stuff to a business that can afford Cisco stuff, but switches works good enough for low capacity networks). The configuration via GUI is slow and not always logical.
Problems so far:
When upgraded to latest firmware on WMS (2.1.2) and APs (2.0.27) New APs could not be added to WMS.
Downgrade of all units solved this problem. (WMS 2.0.3, AP 2.0.9)
All five (5) units have had problems with losing the connectivity to the LAN, WLANs are up but Internet Access is lost. When connectivity from AP to internet is lost I cannot ping the LAN interface.
I also have statistics from Cacti showing that the problem most often appear during business hours, but not always.
First I thought that my POE switch (dlink 1316 poe) didn’t provide enough output power but after removing 4 of the APs from the POE switch and putting them in to different switches on both access and distribution layers I still have the same issues. Even when turning of the G-band and running only on A-band the Aps are having problems.
(I realize now that I haven’t turned off the A band on all Aps, next step..)
Next step is to upgrade the APs again and run them without the WMS
Why? Because the WMS will not be able to find the APs unless they are factory reset and in the default network 192.168.0.0 /24.