Reply
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
wms5316 and wndap350
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2010-11-09
02:27 PM
2010-11-09
02:27 PM
wms5316 and wndap350
New wms5316
New wndap350’s
Old wg302v2
The wms5316 detects the wg302 and does not detect the wndap350. The data sheet shows that all functions are available with the wndap350 and is manageable. I have reset all boxes to factory settings with the same result. The firmware on the 350’s is the only firmware available and also is shown to be compatible. What I need help with is how to access the wndap350’s via the wms5316, Since they are not discovered by the controller. Any real help would be appreciated.
New wndap350’s
Old wg302v2
The wms5316 detects the wg302 and does not detect the wndap350. The data sheet shows that all functions are available with the wndap350 and is manageable. I have reset all boxes to factory settings with the same result. The firmware on the 350’s is the only firmware available and also is shown to be compatible. What I need help with is how to access the wndap350’s via the wms5316, Since they are not discovered by the controller. Any real help would be appreciated.
Message 1 of 7
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2010-11-09
02:40 PM
2010-11-09
02:40 PM
Re: wms5316 and wndap350
the wndap350 probably has a mac-address that not being known by the wms. you should be able to add the OID (the first half of the mac-addres) manually to the wms.
Message 2 of 7
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2010-11-09
04:57 PM
2010-11-09
04:57 PM
Re: wms5316 and wndap350
Thanks that was the answer. I hope the next firmware version applies the fix.
Message 3 of 7
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2010-11-10
02:34 AM
2010-11-10
02:34 AM
Re: wms5316 and wndap350
this is not a bug.. new oids will come out all the time.. thats what that option is for. to manually add the new stuff if the wms doesnt know it yet.
505admin wrote: Thanks that was the answer. I hope the next firmware version applies the fix.
Message 4 of 7
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2011-04-11
08:07 AM
2011-04-11
08:07 AM
Re: wms5316 and wndap350
beisser wrote: the wndap350 probably has a mac-address that not being known by the wms. you should be able to add the OID (the first half of the mac-addres) manually to the wms.
thank you - you have saved my day 🙂
Message 5 of 7
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2011-07-08
07:51 AM
2011-07-08
07:51 AM
WMS5316 and OUI discovery
Hi,
I work in Netgear Tech support.
We've had calls, where customers have a new WMS5316, and they can't discover the WNDAP350. This is a bug in Firmware.
For one WNDAP350, can you get the first 6 digits,
or 3 octets of their MAC address.
Go System , Advanced. >> Discovery OUI >> Organisational Unit Identifier>>
and add in the first 6 digits, in that field. 😮
WNDAP350-- MAC is E0-91-F5
Regards,
John M
Tech Support,
Netgear-- Cork,
Ireland
I work in Netgear Tech support.
We've had calls, where customers have a new WMS5316, and they can't discover the WNDAP350. This is a bug in Firmware.
For one WNDAP350, can you get the first 6 digits,
or 3 octets of their MAC address.
Go System , Advanced. >> Discovery OUI >> Organisational Unit Identifier>>
and add in the first 6 digits, in that field. 😮
WNDAP350-- MAC is E0-91-F5
Regards,
John M
Tech Support,
Netgear-- Cork,
Ireland
Message 6 of 7
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2011-09-09
08:03 AM
2011-09-09
08:03 AM
Wms5316 --Firmware Version 2.1.2 -- 11th August 2011
Hello,
Rev 2.1.2 of firmware elimates the need to perform OUI discovery. 😮
If anyone is having trouble discovering APs on 2.1.2 firmware of the WMS, please see use the following workaround.
Auto Discovery:
Only scans the default subnet of 192.168.0.0/24
IP Discovery:
Web interface>> Configuration >> Access Point Discovery>>
Must be used for any other subnet, can only scan a /24 subnet at a time.
When scanned, and Access Points don’t show up, you have to click the Access Point Discovery.
*****
WMS5316 Firmware Version 2.1.2Release Date: 08/11/2011
http://support.netgear.com/app/answers/detail/a_id/19382
Notes
WMS5316 default IP is 192.168.0.250
WMS5316 supports configuration and monitoring of following Access Point models running at least below specified firmware versions.
a. WNDAP350: Firmware WNDAP350_V2.0.27.
b. WNDAP360: Firmware WNDAP360_V2.0.7.
c. WNAP210: Firmware WNAP210_V2.0.27.
d. WNAP320: Firmware WNAP320_V2.0.3.
e. WG103: Firmware WG103_V2.0.37.
Rev 2.1.2 of firmware elimates the need to perform OUI discovery. 😮
If anyone is having trouble discovering APs on 2.1.2 firmware of the WMS, please see use the following workaround.
Auto Discovery:
Only scans the default subnet of 192.168.0.0/24
IP Discovery:
Web interface>> Configuration >> Access Point Discovery>>
Must be used for any other subnet, can only scan a /24 subnet at a time.
When scanned, and Access Points don’t show up, you have to click the Access Point Discovery.
*****
WMS5316 Firmware Version 2.1.2Release Date: 08/11/2011
http://support.netgear.com/app/answers/detail/a_id/19382
Notes
WMS5316 default IP is 192.168.0.250
WMS5316 supports configuration and monitoring of following Access Point models running at least below specified firmware versions.
a. WNDAP350: Firmware WNDAP350_V2.0.27.
b. WNDAP360: Firmware WNDAP360_V2.0.7.
c. WNAP210: Firmware WNAP210_V2.0.27.
d. WNAP320: Firmware WNAP320_V2.0.3.
e. WG103: Firmware WG103_V2.0.37.
Message 7 of 7
Announcements
• What is the difference between WiFi 6 and WiFi 7?
• Yes! WiFi 7 is backwards compatible with other Wifi devices? Learn more