NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
stroebi
Dec 07, 2011Aspirant
Problem discovering WNDAP360 with WMS5316
Hy folks, WMS5316 Firmware v2.1.2 WNDAP360 Firmware v2.1.1 Both in factory setting After reading some topics with the WNDAP350 I found out that the WMS5316 discovers the AP by sending a SNMP-...
cwolfram
Jan 31, 2013Aspirant
Interestingly, I have a similar problem:
The WMS5316 won't discover our WNDAP360-APs.
Firmware on the WMS5316 is 2.1.4.15
Firmware on the WNDAP360s is 2.1.5
Our Network: 192.168.0.0/23
WMS5316: 192.168.0.10
A WNDAP360: 192.168.0.21
Now the interesting part (see the following screenshot from Wireshark):
For Discovery, the WMS5316 (.10) sends out an SNMP request.
The AP (.21) recognizes it and answers - but to an IP address that is not in our network (192.168.2.132).

Why? I really don't know.
Subnet masks are correct in both devices (255.255.254.0). What can it be?
Has anyone the same problem?
The WMS5316 won't discover our WNDAP360-APs.
Firmware on the WMS5316 is 2.1.4.15
Firmware on the WNDAP360s is 2.1.5
Our Network: 192.168.0.0/23
WMS5316: 192.168.0.10
A WNDAP360: 192.168.0.21
Now the interesting part (see the following screenshot from Wireshark):
For Discovery, the WMS5316 (.10) sends out an SNMP request.
The AP (.21) recognizes it and answers - but to an IP address that is not in our network (192.168.2.132).

Why? I really don't know.
Subnet masks are correct in both devices (255.255.254.0). What can it be?
Has anyone the same problem?