An EAP610 allow connection and other EAP610 not!
Hi,
i have two EAP610 on two floors house adopted by OC200v1 controller (fw version 1.32.6 Build 20241101 Rel.41525).
I cannot connect an android phone (Oppo reno 12f 5G) to EAP 610 on the ground floor, phone says connect failed. But, if i try to connect phone on EAP610 on the first floor, it connects. What could be the issue?
In the log on controller, i cannot see any event about this connection attempt.
Here config images (EAP610-PP allow connection, EAP610-PT don't allow connection).
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Tried to change WPA mode to WPA2 only (without WPA3), and client can now connect to EAP610-PT too. Changed again to WAP2/WAP3 and it can't connect anymore. But.... why a device works with WAP2/WPA3 and the other not? Same device?!
Is device at ground floor a faulty device?
- Copy Link
- Report Inappropriate Content
Hi @Antony23
Thanks for posting here.
Generally, hardware defects would not cause such an issue.
Were you using the same wireless client to test the connection with these two APs? If not, please retest using the same mobile device and let us know the result.
BTW, I found that the firmware version for your EAP and controller are really old. please update them to the latest versions to see if it helps.
OC200:
https://static.tp-link.com/upload/firmware/2025/202505/20250521/OC200(UN)_v1.0_1.35.7%20Build%2020250514.zip
EAP610 V3:
EAP610 | EAP613 Pre-release Firmware Adapted to Omada Controller v6.1 (Released on 4th Jul, 2025)
- Copy Link
- Report Inappropriate Content
I have exactly had the same problem, I have a mix of access points, I have a pixel phone with Wifi 6e, and a Motorola Wifi6 phone. The pixel phone roams without problems, the Motorola phone does not roam at all. After a little experimenting I found out that there are some devices that do not roam very well with WAP3 enabled. When I create an SSID with WPA2 and PMF to Capable, 802.11r deactivated, the Motorola phone roams without any problems. I googled a little and I do not think it is an access point problem, I see many other types of access points have the same problem, it is simply some devices that are not fully compatible with WPA3 and roaming.
What kind of phone do you have?
- Copy Link
- Report Inappropriate Content
My problem is not roaming, my problem is phones won't connect at all.
- Copy Link
- Report Inappropriate Content
Yes, i'm using the same wireless client to test both the APs. The same client connect immediately EAP610-PP, e won't connect at all with the other EAP610-PT.
Today i tried with an other android phone. The result is that not problem at all with EAP610-PP (as the other client) and with EAP610-PT i had to try to connect different times consecutively before it connects successfully (in the failed attempts i received connection timeout error).
So it's clear i have a problem with one of mine EAP610. I suspect ah hw fault at this point. The other EAP610 works perfectly.
- Copy Link
- Report Inappropriate Content
Hi @Antony23
Thanks for the reply.
Do you adopt the two EAPs on the same site? This is to confirm if their configurations are the same.
Could you let me know if you updated the EAP and the controller to the latest version? Does it make any difference?
If the EAP-PT never works, it may be an EAP defect, but it may also be caused by some other factors, such as the Ethernet cable.
To confirm this, you may swap the two EAP units and see if the issue comes with the EAP or the cable.
If come with the EAP-PT, you may contact your retailer to check the warranty.
If comes with the Ethernet cable/installation location, please change different cables/ports to plug the EAP-PT.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 211
Replies: 6
Voters 0
No one has voted for it yet.