eap 225 outdoor in disconnect status
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
I have completed configuring my eap 225 outdoor with my oc200 at home and it worked like a charm. When I set up the devices at the office, I have noticed that my EAP 225 outdoor, thru omada cloud , says that the status is disconnected. The hardware I changed during the installation here in the office is a longer cat 6 cable (15 meters). When I tested the setup at home, I used a cat 5e cable. I believe that EAP225 outdoor device should still would with cat6 or I may be wrong? Restarted the PoE and reconnected the cables to other LAN ports and still no go. Firmware is updated. Any other troubleshooting step I should do? Thanks
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Are you using the same controller device and site setup at the factory, and if not, did you factory default the EAP225-outdoor to enable it to be adopted by the new Controller?
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
When you reset the 225-outdoor, when it boots back up, is it broadcasting a TPLINK-xXXXXX SSID, or the one you previously configured? You have to lean on that reset button by the ethernet jack for a good 30s to be sure you factory default it, and not just 'reboot' it.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Okay, that's good news. I assume you are using the passive POE injector that came with the EAP225-outdoor? If so, please connect the POE LAN port of the injector to the unused OC200 ethernet port using a known good cable for testing, and a known good cable between the injector and the AP. The controller should detect the EAP as being ready for adoption. If it doesn't, you need to change your cables and inspect the pins inside the POE ports and the AP itself for damage or debris.
If you cannot get the controller to 'see' the AP when the controller is directly connected to your router's LAN (for DHCP) and the AP, you most likely have a hardware fault.
Also please make sure both devices have the latest firmware installed. What controller software version are you running BTW?
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 696
Replies: 7
Voters 0
No one has voted for it yet.