@Hank21 

Thank you for your interest in my problem.

My LDAP/AD server is located in the company's local network, in which the ER605 router is to handle external VPN connections.

After entering the address of the LDAP/AD server, i.e. ldap://192.168.1.10, the message remains the same.

  @canopus Unfortunately not, Other tasks were more important, so for the moment I had to let go of the subject.

  @Neeke85 We too have this problem, we are using the Omada Cloud Controller.

I have tested the same setting on a Draytek router on the local network and it connects up fine and lists the users, not sure whats wrong with Omada but it needs to be fixed URGENTLY.

  @Neeke85 Same problem here... Looks like it's terminally broken... Also, what's with the terrible 64 character limit on the regular DN?

  @Neeke85 Hello! Same problem here, with er7206 v1.0 router, managed by Omada software controller 5.8.

Same Issue here. 

Using LDAP for dozens of devices, however Omada-SDN refuses to connect to the internal 
LDAP-Servers / Windows Domain Controllers.

Same issue here, ER7206 v1.0, firmware 1.4.0 Build 20231114 Rel.36220, configured Active Directory + other services without problems, in case of TP-Link the only thing I get is "Failed to connect to the LDAP server."

  @Neeke85 I have same problem. I have a router er605 and not work. Then I install an Omada controller in the ubuntu and have the same problem. I test ldapsearch and work normal.

Neeke85 wrote

Hey,
Sorry for my english, i use google translate.

How to access LDAP in omada controller.
My configuration attempts are unsuccessful.
I get the message: "Directory search failed. Please check your LDAP server configurations."
I am sure that I gave good data because this data is also used in other applications using ldap.

Server Address: this is the address of the company's domain controller, which is only available within the company.