Reply

Re: Problem discovering WNDAP360 with WMS5316

stroebi
Aspirant

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-Request.
So,



      Now, after this investigations everything works proper, but nothing works as I expect!



    Please help me!
Try to find a WLAN-Cable!
Message 1 of 10
zpower
Novice

Re: Problem discovering WNDAP360 with WMS5316

I also purchased the same devices last week and have the same problem:

1 NetGear WMS5316 Firmware 2.1.2
2 NetGear WNDAP360 APs Firmware 2.0.7

At one point I upgraded the APs to firmware 2.1.1, however, a KB article stated that for these APs the firmware should be at least below 2.0.7. I attempted Device Discovery with the APs set to firmware 2.1.1 but the WMS could not find them, so I flashed the firmware back to 2.0.7 and it still could not find them. I know the APs are working because I can ping them from the WMS and I can log into them.

I also attempted device discovery with the WMS at firmware 2.0.3. I was somewhat more successful with this method because instead of using SNMP to connect to the APs the WMS (according to forum users) just sends out a network ping and brings back any devices that respond. I had to add the OIU number to the WMS, but after doing this the APs were found. The problem with this method, however, was that the devices showed up as Unknown and the option to add them to the WMS was grayed out.

I am at a loss and any advice would be helpful. I'm on the phone with NetGear support right now, but I've been bounced around from department to department six times now with no one taking ownership of this particular device.
Message 2 of 10
zpower
Novice

Re: Problem discovering WNDAP360 with WMS5316

I got help from NetGear this afternoon and they gave me a fix to solve the problem. Basically I had to update the firmware on the APs to v2.1.1 and then after applying the firmware update, I had to reset the APs to factory settings. Once this was done, the WMS Device Discovery worked flawlessly. It found the APs and allowed me to reset their IPs. I had to do each one individually because they initially had the same IP address (192.168.0.100).

😄 very happy that it's working now.
Message 3 of 10
cwolfram
Aspirant

Re: Problem discovering WNDAP360 with WMS5316

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?
Message 4 of 10
zpower
Novice

Re: Problem discovering WNDAP360 with WMS5316

Not sure why this is happening for you. Have you tried contacting Netgear support as well as posting on the forums?
Message 5 of 10
cwolfram
Aspirant

Re: Problem discovering WNDAP360 with WMS5316

zpower wrote:
Have you tried contacting Netgear support as well as posting on the forums?


No, not yet, but it is my next step.

Here is the link to the screenshot again since the picture above doesn't show up: http://d.pr/i/KCVy
Message 6 of 10
zpower
Novice

Re: Problem discovering WNDAP360 with WMS5316

That's weird, initially I could see your screenshot.

Anyway, I have no idea why the AP would be sending information to an address not in your network. Maybe it has some held over information from when it was tested at the manufacturer. When I was having these problems, one of the things I had to do was update the AP to the latest firmware, and after doing that reset the AP to factory default. Maybe you could try that to see if it helps.
Message 7 of 10
cwolfram
Aspirant

Re: Problem discovering WNDAP360 with WMS5316

zpower wrote:
When I was having these problems, one of the things I had to do was update the AP to the latest firmware, and after doing that reset the AP to factory default. Maybe you could try that to see if it helps.


I tried that about a dozen times. Always the same problem. I even took another AP (also a WNDAP360) to see if it has the same problem. It did.

Time for Netgear Support I guess. 😕
Message 8 of 10
YKK_PC_Tech
Novice

WNDAP350 also sending traffic to 192.168.2.132

cwolfram wrote:
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?


Just wanted to let you know we are noticing traffic coming from our WNDAP350's to the exact same IP but we are on a 10.240.0.0 address range. We are not using SNMP so I've disabled it and want to see if that stops the traffic.
We are using Firmware Version: WNDAP350_V2.1.7
Message 9 of 10
Nhellie
Virtuoso

Re: Problem discovering WNDAP360 with WMS5316

What IP address did you set on the APs? Are the AP's being detected?
Message 10 of 10
Top Contributors
Discussion stats
  • 9 replies
  • 12712 views
  • 0 kudos
  • 5 in conversation
Announcements

Orbi WiFi 6E