AP disconnects itself when just after binding to omada controller
Hi guys,
I have an environment with 2 EAP330 and 2 EAP245. All of them are up to date.
I've bind three of them to an omada controller, but the last one has a problem.
When I adopt it, first, he's provisioning, then configuring, a lot of time. Then it connects just a few seconds and it appears as disconnected.
When it disconnects, it takes the default IP address (192.168.0.254) and recovers web management interface and says this:
When I reset it, process start agan.
I've follow exactly the same process as I did with the other EAP245. They're on the same VLAN, even they're connected to the same switch so it's not an routing problem.
Any help will be very appreciated.