EAP Controller unable detect pending EAP

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

EAP Controller unable detect pending EAP

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
EAP Controller unable detect pending EAP
EAP Controller unable detect pending EAP
2018-04-04 15:41:17
Model :

Hardware Version :

Firmware Version :

ISP :

Good day people,

My problem as stated as above. Some context to be given, I am working in IT department for my company and they had installed EAP110-Outdoor AP in their branches. I wish to set up a controller back in my office to manage those EAPs, which is obviously in different network. I had problem doing so while following through the guide provided by TP-Link.

Installed EAP Firmware Build version: 20170914
EAP Controller version: EAP Controller_V2.5.4_Windows

Proven compatible.
https://www.tp-link.com/en/faq-913.html (Paragraph 3)

What I have done:

Branch side:
Installed EAP Discovery tool on my laptop and open it in the same network as EAP. The discovery tool able to detect EAP.
[*]Configure controller IP. Test ping successful on my side. Entered valid EAP username and password. Status shown pending.





Office side:
Installed EAP Controller.
[*]Configure basic settings - User account, added site etc.
[*]Already configured with public address and reachable via network from the outlet.





Problem faced so far:
On controller side, in access point tab, there is no pending EAP to be adopt.

Need some advice on it thanks!
  0      
  0      
#1
Options
4 Reply
Re:EAP Controller unable detect pending EAP
2018-04-08 21:55:08
For EAP discovery you need to open TCP ports 29811, 29812, 29813 and UDP port 29810 in the firewall on the Controller side. If you want to use portal functions or if you need remote web UI access to the EAP Controller, TCP ports 8088 and 8043 must be opened, too.
༺ 0100 1101 0010 10ཏ1 0010 0110 1010 1110 ༻
  0  
  0  
#2
Options
Re:EAP Controller unable detect pending EAP
2018-06-29 20:34:14

R1D2 wrote

For EAP discovery you need to open TCP ports 29811, 29812, 29813 and UDP port 29810 in the firewall on the Controller side. If you want to use portal functions or if you need remote web UI access to the EAP Controller, TCP ports 8088 and 8043 must be opened, too.


Ok now that I've opened them, netiher the EAP controller or EAP discovery utility can detect my two EAP225v3's!
File:
Capture5.JPGDownload
  0  
  0  
#3
Options
Re:EAP Controller unable detect pending EAP
2018-07-01 00:44:56

R1D2 wrote

For EAP discovery you need to open TCP ports 29811, 29812, 29813 and UDP port 29810 in the firewall on the Controller side. If you want to use portal functions or if you need remote web UI access to the EAP Controller, TCP ports 8088 and 8043 must be opened, too.


Ok now that I've opened them, netiher the EAP controller or EAP discovery utility can detect my two EAP225v3's!




  0  
  0  
#4
Options
Re:EAP Controller unable detect pending EAP
2018-07-01 04:39:17
You wrote you have assigned a public IP address to the server running the Controller, but in Discovery you did use a private IP address (192.168.1.81). If not using some kind of VPN between the branches and the main office, the private IP does not get routed on the Internet.

Here is how I manage to have different branch sites connect to the central office: EAP Controller runs on a system with a public IP address, ports mentioned above are open in the firewall. DHCP server in private LANs at branch offices communicate the Controller's public IP through DHCP option 138 (CAPWAP), so the EAPs will enter discovery stage as soon as they get a DHCP lease. The EAPs must not run in stand-alone mode for this scheme to work.
༺ 0100 1101 0010 10ཏ1 0010 0110 1010 1110 ༻
  0  
  0  
#5
Options