AP disconnects itself when just after binding to omada controller

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.

AP disconnects itself when just after binding to omada controller

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
AP disconnects itself when just after binding to omada controller
AP disconnects itself when just after binding to omada controller
2019-09-12 12:19:50 - last edited 2019-09-12 12:22:34
Model: EAP245  
Hardware Version: V3
Firmware Version: 2.2.0

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.

  0      
  0      
#1
Options
4 Reply
Re:AP disconnects itself when just after binding to omada controller
2019-09-12 12:53:41 - last edited 2019-09-12 12:55:33

Hi @Quobis,

 

try the following:

 

  • Perform a hardware reset on this EAP (press the RESET button with a paperclip for 5-7 sec.).
  • Connect the EAP to the same switch port used for the other EAP, which works (disconnect the other EAP temporarily).
  • Try to adopt the EAP.

 

What's the result?

༺ 0100 1101 0010 10ཏ1 0010 0110 1010 1110 ༻
  0  
  0  
#2
Options
Re:AP disconnects itself when just after binding to omada controller
2021-07-14 09:19:50

@Quobis I have the same problem, and it disconnects the whole network as well. Tried everything mentioned same result over and over. The Ap works flawlessly in stand alone 

  0  
  0  
#3
Options
Re:AP disconnects itself when just after binding to omada controller
2021-07-14 11:34:36

Dear @FAD-Champs,

 

FAD-Champs wrote

I have the same problem, and it disconnects the whole network as well. Tried everything mentioned same result over and over. The Ap works flawlessly in stand alone 


It's a pretty old thread. May I know the device information of your EAP and Controller?

What's the current firmware version of your EAP? Are you using Omada Software Controller (Windows/Linux) or OC200/OC300?

 

What do you mean that it disconnects the whole network?

How is the EAP connected in your network? Any VLAN configured on the controller?

Is the EAP connected to the original PoE injector for power and then connect to your router for the Internet?

2022 TP-Link Wi-Fi 7 Product Launch Event | Watch the Replay at https://www.tp-link.com/us/wifi7/event/.
  0  
  0  
#4
Options
Re:AP disconnects itself when just after binding to omada controller
2021-07-14 11:41:11

@Quobis Thanks for your kind reply. Yes it is old but it is the only relevant one I found. There is no similar situation in other threads.

 

My current setup is 8 EAPs 110 V4 Firmware 5.0.1 Build 20210316 Rel. 38795.

 

I am trying to introduce new EAPs 245 V3 Firmware 5.0.2 Build 20210303 Rel. 34713.

 

I use Omada Controller version4.4.3  on Windows 10. 

 

I have tried everything even tried disabling mesh, connecting to Different Vlans, reseting many times, using different Aps, you name it. It is driving my crazy. 

  0  
  0  
#5
Options

Information

Helpful: 0

Views: 1421

Replies: 4

Related Articles