Trouble Firmware WMS5316

Or you can do like me.

Downgrade your AP to the V2.0.9 version
have your wsm5316 in V2.0.3 version were you can configure the MAC address.

The English support could inform the french support.
It could be best to not ask to the customer to RMA the netgear product !!
I am not happy to pay the RMA transport to get the same non working product at the end.

We are resellers for Netgear and have a case open with them. It is with there level 3 engineers now!! But i have been sent a workaround. You have 2 options:-

1. You can either reset all your Access Points to factory default and then run auto discovery and it will find them all and let you add them

Auto Discovery apparently Only scans the default subnet of 192.168.0.0/24

2. IP Discovery: Must be used for any other subnet, can only scan 24 maximum at a time.When scanned, the found Access Point don’t show up, you have to click the Access Point Discovery they should show up under the Auto Discovery tab

Personally i did the first option and factory reset them all and it worked like a charm. List all access point and gives you the option to fill in the new IP address for them all!!
If i hear anything else i will pass it on

Thanks
David

Why not take over this thread with yet another post :)

I am still 100% convinced there is a firmware bug, the Discover feature sometimes disappears, has randomly found my devices, but more often than not left me stranded.


But in hopes of getting things running I did the following.
Downgraded back to 2.0.2 and added the mac addresses for my units.

Discover feature was working no problem except of course for the firmware conflict.

Upgraded to 2.1.2, verified Discover feature wasn't finding any of my devices yet again. At this point I noticed that when I downgraded to 2.0.2 I jacked up the config on the one access point that I had somehow got configured on the WMS5316. So I reset it to the default, and bamm, now it was discovered using the Auto Search.

So it seems the unit will find units that are freshly factory reset, but not units who have been modified. I am not sure if the only reason this worked was because I added the mac address while in the 2.0.2 config, or if it will work with others. So one by one I reset each access point and have added them to my WMS5316... The process wasn't perfect for me as I had random times where I had to reset a device more than once for everything to come up and show in sync. Def a pain in the ass, but at least I am not stuck waiting for a firmware update.

broadld wrote:

We are resellers for Netgear and have a case open with them. It is with there level 3 engineers now!! But i have been sent a workaround. You have 2 options:- 1. You can either reset all your Access Points to factory default and then run auto discovery and it will find them all and let you add them Auto Discovery apparently Only scans the default subnet of 192.168.0.0/24 2. IP Discovery: Must be used for any other subnet, can only scan 24 maximum at a time.When scanned, the found Access Point don’t show up, you have to click the Access Point Discovery they should show up under the Auto Discovery tab Personally i did the first option and factory reset them all and it worked like a charm. List all access point and gives you the option to fill in the new IP address for them all!! If i hear anything else i will pass it on Thanks David

Dope wish I would have read this before making my post, I had started typing my message before you replied and I never went back to fresh the posts. For whatever reason Resetting each access point works, but it was a PITA, and sometimes I had to reset things more than once. Oh well, I'm all set for now so I can consider this project done despite the firmware bug.

I have a similar configuration: 1x WMS5316 -- 1x GS724TP -- 8x WNDAP350

With FW 2.0.3 on controller, I can find all AP (FW 2.0.1, 2.0.9 or 2.0.27) but only after adding OUI A0:21:B7. Anyway, the controller have authentication failure when it tries to access to AP with FW 2.0.27. AP with FW 2.0.1 et 2.0.9 synchronize successfully.

If I upgrade the controller to FW 2.1.2, I have no more the OUI menu, all AP that was synchronized stay OK, but I cannot discover/add others. If I decide to unmanage some AP, it will be no more possible to manage them after because they will no more be discovered.

In the documentation, is written that the minimal FW for WNDAP350 is 2.0.27 if the FW for controller is 2.1.2 but is never discovered.

In conclusion, [highlight]the combo that works is[/highlight]:

Hope this will help you

So after almost a month or so of no problems with my RMA replacement unit, and 2.1.2, it randomly started rebooting and eventually downgraded itself.

This is the same problem I had with my original unit where it no longer runs stable with 2.1.2. I have to believe this is a firmware issue, but I guess I could just be dealing with 2 failed units. Loosing faith in my network configuration right now that is for sure.

I noted a bug in the WMS firmware v2.0.3 when using IE 9 and https

When trying to discover accesspoints in "Configuration > Access Point Discovery" the main window was empty, so I tried to change to http and then I could use the "Access Point Discovery" as supposed.

In Firefox 7.0.1 both https and http works.

The same happened in both IE and Firefox when using fw 2.1.2 but I´m not 100% sure if I tried to log in with http in any of the browsers (although I am pretty sure :) )

//Jimi

Any update on this problem?

I just bought a WMS5316 with WNDAP350 accesspoints, and i get the same problem.

CFT wrote:
Any update on this problem? I just bought a WMS5316 with WNDAP350 accesspoints, and i get the same problem.

+1 for an update...

I'm in the same situation and need to get a WMS5316 & a few WNDAP350's installed for a client.

-Randy

Hi Guys,
I've only recently joined and already wish I read these posts before agreeing to a quote for 1 x wms5316 and 8 x wndap350's, now I look after these beasts at a local school.
I fell for the mistake of upgrading the AP firmware to 2.0.27(to cure odd rebooting issue), and the settings reverting to default(what a nightmare that was!). After reconfiguring the AP's to their new IP range, they where still unmanageable by the WMS5316.
I raised a call with Netgear, very dubious about upgrading it (if it lost it's settings, I'd have more pain). On their suggestion I upgraded to 2.1.2, and managed to get 2 AP's managed.
These new firmware's have no manual OID entry screen, so when some AP's didn't show I asked again for help.
I've since been pointed towards upgrading to 2.1.4(which worked without loosing settings!), which still doesn’t have a OID entry screen, still fails to auto discover on a non-default(192...) IP range, but I now have 8 managed AP's.
It's a bit messy, but the non manageable AP's needed a factory reset, a laptop on the 192.168.0.x range was then used to reconfigure each(since they all default to 192.168.0.237 it as to be one at a time!) to the right country settings and IP range(10.xxx for me), one I'd confirmed it was OK, on to the next.
I still think we need a crib sheet for different setting scenarios, there are some rogue AP/RF settings that don't work well, these need testing by Netgear, and we the customers need to be advised, before we loose all our hair!
Best of Luck!
Dave.