EAP220 Does not work when the controller and AP in separate network
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
EAP220 Does not work when the controller and AP in separate network
Model :
Hardware Version : Not Clear
Firmware Version :
ISP :
Model : EAP 220
Firmware 20150619-rel43709
AP : Subnet A - 10.0.1.0/24
Static IP - 10.0.1.11
Controller : Subnet B - 192.168.1.0/24
I can ping from Subnet B (Controller Side) to AP IP addresss 10.0.1.11
I have follow the article ( http://www.tp-link.com/en/faq-913.html ) to set the controller IP,
But neither the discovery nor the controller software able to see the AP, and hence cannot adopt the AP.
Try to login the web management for the AP itself, the webpage cannot be loaded either but ping the IP has response
When I connect the AP to a laptop directly without changing any setting, the webpage http://[AP IP] can be loaded without issue.
Any advice appreciated.
I have used similar product from Ubiquiti with 20 over AP, but no issue with the same setup where the controller and AP are located at separate networks.
Hardware Version : Not Clear
Firmware Version :
ISP :
Model : EAP 220
Firmware 20150619-rel43709
AP : Subnet A - 10.0.1.0/24
Static IP - 10.0.1.11
Controller : Subnet B - 192.168.1.0/24
I can ping from Subnet B (Controller Side) to AP IP addresss 10.0.1.11
I have follow the article ( http://www.tp-link.com/en/faq-913.html ) to set the controller IP,
But neither the discovery nor the controller software able to see the AP, and hence cannot adopt the AP.
Try to login the web management for the AP itself, the webpage cannot be loaded either but ping the IP has response
When I connect the AP to a laptop directly without changing any setting, the webpage http://[AP IP] can be loaded without issue.
Any advice appreciated.
I have used similar product from Ubiquiti with 20 over AP, but no issue with the same setup where the controller and AP are located at separate networks.