EAP225 unable connect, disconnnect after updating OMADA controller OC300 with Latest Firmware 5.3.2
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
After OC300 update to 5.3.2 the EAP 225 on the network show to be disconnected , when forgotten via configure, the EAP appears as managed by others, after adapting EAP 225 connects for 30 seconds , than heart beat missed occurs and than disconnected. This happens to EAP225 only , All EAP 115 connect instantly after the upgrade of OC300 to 5.3.2.
Please provide urgent solution.
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Is your EAP225 wired or wirelessly connected to your network?
Have you tried resetting the EAP and then using controller adopt again?
Generally speaking Forget does not mean you have reset the EAP, it just puts the EAP back into Standalone.
You need to manually reset the EAP and then see if the controller can find it.
It is very important to make sure that the EAP and the controller can communicate with each other, you can ping the IP address of the EAP on the controller side to try.
- Copy Link
- Report Inappropriate Content
This sounds very similar to https://community.tp-link.com/en/business/forum/topic/574182 issue I had with my 225-outdoor.
I eventually got it working by:
1) Revert oc200 to backup that still had it linked and managing the EAP225.
2) Power down EAP225
3) Boot EAP225 and verify that it becomes connected to oc200 (but like you said this will only last a minute before it disconnects)
4) Before EAP225 disconnects again, press forget which should tell oc200 to forget it and should cause the EAP225 to reset itself to factory settings
5) Now EAP225 should show up in oc200 as not provisioned. Select "Adopt".
6) Once adopted, apply settings to EAP225 and it should stay connected.
You could also try manually resetting the EAP225 instead of relying on the oc200 to reset it. I avoided this becaues my access point was hard to reach.
- Copy Link
- Report Inappropriate Content
Is your EAP225 wired or wirelessly connected to your network?
Have you tried resetting the EAP and then using controller adopt again?
Generally speaking Forget does not mean you have reset the EAP, it just puts the EAP back into Standalone.
You need to manually reset the EAP and then see if the controller can find it.
It is very important to make sure that the EAP and the controller can communicate with each other, you can ping the IP address of the EAP on the controller side to try.
- Copy Link
- Report Inappropriate Content
I would follow @Virgo advice.
I had a client with the same issue. After the forget and full reset on the AP. I had to log into the AP and set the IP address of the controller. that stuck.
- Copy Link
- Report Inappropriate Content
This sounds very similar to https://community.tp-link.com/en/business/forum/topic/574182 issue I had with my 225-outdoor.
I eventually got it working by:
1) Revert oc200 to backup that still had it linked and managing the EAP225.
2) Power down EAP225
3) Boot EAP225 and verify that it becomes connected to oc200 (but like you said this will only last a minute before it disconnects)
4) Before EAP225 disconnects again, press forget which should tell oc200 to forget it and should cause the EAP225 to reset itself to factory settings
5) Now EAP225 should show up in oc200 as not provisioned. Select "Adopt".
6) Once adopted, apply settings to EAP225 and it should stay connected.
You could also try manually resetting the EAP225 instead of relying on the oc200 to reset it. I avoided this becaues my access point was hard to reach.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 1065
Replies: 6
Voters 0
No one has voted for it yet.