Omada Software controller v3.2.14 working fine, v4.1.5+ failing to adopt EAPs
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
I have a couple EAP 245 v3 that I am trying to manage with Omada Software controller. All devices and the Windows 2012 R2 Server running the controller are on the same subnet. EAP245 are up-to-date on the latest firmware. Whenever I tried to adopt the EAP in v4.1.5 or higher, the EAP failed to adopt with the error message the device failed to adoption because the device does not respond to the adoption command (or something very similar). After much frustration, I uninstalled the controller and installed v3.2.14. Devices adopted and provisioned just like they are supposed to. The EAP were factory reset prior to attempting to adopt in 4.3 and then 4.1.5.
The fact they are adopting fine in 3.2.14 makes me pretty sure there's no firewall blocks or network issues in play, but outside of that I'm stumped - any thoughts as to why they might not be adopting in version 4 of the software controller?
1. If you are sure that the EAP's firmware is compatible with the v4 Controller, then you can try to Ping the EAP's IP address on the PC with the software installed.
If the PC can Ping the EAP's IP address successfully, then it is probably related to the anti-virus and firewall, especially with TCP/UDP port 29810-29813.
2. Turn off the firewall directly may cause some unsecured problem, you may need to open ports on Windows Firewall.
https://www.windowscentral.com/how-open-port-windows-firewall