EAP Won’t use new SSID
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
I just adopted my EAP225 to my OC200 and setup site and SSID but the eap won't take those settings. Even if I turn on a gues network the eap only outputs the factory default SSID with no password
what am I missing?
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Dear @Shaneb0422,
I just adopted my EAP225 to my OC200 and setup site and SSID but the eap won't take those settings.
Can you get Internet access from the default SSID? Is the EAP225 showing up as Connected on the site you created from OC200? Does the MAC address of the EAP225 match the MAC address printed on the unit itself?
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Dear @Shaneb0422,
I had to manually load the firmware on each of my APs, the firmware said up-to-date from the omada controller but for some reason this solved my issues with adopting or EAPs catching site changes
Thank you for your valued reply and feedback. Glad to hear that the issue was resolved finally. Enjoy the Internet with Omada EAPs!
- Copy Link
- Report Inappropriate Content
@Shaneb0422 Hi. I am now experiencing this same problem (5/8/21). I've installed EAP245s with the OC200 at many sites. This is the first time I've encountered a failure of this type. TPLink tech support couldn't even grasp what was going on. They asked many questions from a script and it was very hard to understand them through the language barrier. This is the only post I have found that mirrors the problem I am having..."EAPs adopted and provisioned via OC200 but still broadcast the default SSID". You noted that manually updating the firmware did the trick because from the OC200 POV, their firmware was up to date. So my question are 1) after you "forgot" the EAPs from the OC200 list and then accessed the EAP via its web interface, was it's firmware up to date? 2) Did you update the firmware, reinstall the existing firmware or fall back the firmware? What firmware version(s) were in play here? Thanks, Dean
UPDATE: I just went on the site remotely and now, after two days, the OC200 (as well as omada.tplinkcloud.com) are showing that the EAP's firmware (2.4.0) is not compatible with the OC200's firmware (4.3.5)! Thus, I was able to upgrade their firmware to 5.0.2 and now, (I believe, as I am remote) the problem is solved! Good, but what took so long for the OC200 to figure this out?
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 1247
Replies: 4
Voters 0
No one has voted for it yet.