Omada Controller can't find EAPs on same subnet

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Omada Controller can't find EAPs on same subnet
Omada Controller can't find EAPs on same subnet
2020-06-11 22:08:35 - last edited 2020-06-12 01:00:32

I have a simple setup : 

Omada controller 3.2.10 64-bit on windows 10 pro (192.168.1.100) - for testing purposes, firewall is disabled

EAP245 fw1.4.0 Build 20180323 (192.168.1.113)

EAP120 fw 2.0.2 Build 20160405 (192.168.1.126) - I later found it is not compatible, returning it to amazon to replace with EAP225...

 

I cannot get Controller to find the EAPs. If I exit Omada Controller and start Omada Discovery utility on the same computer, it finds the EAPs instantly, so I can say the network topology seems right, but I can't manage to configure Omada controller.

0
0
#1
Options
1 Reply
Re:Omada Controller can't find EAPs on same subnet
2020-06-12 20:05:13 - last edited 2020-06-12 20:05:25

Hi @c0ss3tt3,

 

Which EAP245 is that?  V1?  Do a factory reset and manually upgrade the firmware through the web ui of the AP first.  It might be old enough to not be supported by the current version o Omada.

 

-Jonathan

0
0
#2
Options