Why my clients don't roam or connect to the nearest AP
EAP680 HD , EAP620-Outdoor HD , EAP670-Outdoor HD , EAP245 , EAP320 , EAP683 , EAP673-Extender , EAP120 , EAP230-Wall , EAP680 , Omada EAP770 , EAP113-Outdoor , EAP215-Bridge KIT , EAP225-Outdoor Plus , Festa F65 , EAP115 , EAP235 , EAP610-Outdoor Plus , EAP650-Outdoor , EAP610 HD , EAP653 UR , EAP660 HD , EAP625-Outdoor HD , EAP670-Outdoor , Omada EAP780 , EAP673 , EAP110 , EAP670 , EAP115-Bridge , EAP620 HD Plus , EAP235-Wall , EAP225 , EAP215-Bridge , EAP610-Outdoor , EAP115-Wall , EAP610GP-Desktop , EAP225 Plus , EAP683 UR , EAP225-Wall , EAP655-WE-AC , EAP211-Bridge , EAP225-Outdoor , EAP223 , EAP783 , EAP220 , EAP265 HD , EAP115-Bridge KIT , EAP620 HD , EAP613 , EAP615-WE , EAP610 , EAP653 , EAP110-Wall , EAP211-Bridge KIT , EAP655-Wall , EAP615-Wall , EAP620 HD-PLUS , EAP773 , EAP772 , EAP650 , EAP683 LR , EAP330 , EAP770 , EAP690E HD , EAP615GP-Wall , EAP723 , EAP623-Outdoor HD , EAP110-Outdoor , EAP650-Wall , EAP235-Wall Plus , EAP245 Plus
Recent updates may have expanded access to feature(s) discussed in this FAQ. Visit your product's support page, select the correct hardware version for your device and check either the Datasheet or the firmware section for the latest improvements added to your product.
Contents
Factor 1: Interference or Network Congestion
Factor 2: Signal Strength Threshold
Factor 3: Wireless Clients’ Limitations
Factor 4: Coverage and Placement
Factor 5: Configuration on the Controller
This article covers factors to help you resolve roaming issues in your Wi-Fi network, such as interface and network congestion, signal strength, coverage range and placement etc.
- Omada Controller (Software Controller / Hardware Controller / CBC, v5.9 and above)
- Omada AP
After your APs have established the mesh network, your wireless clients will automatically connect to the nearest AP. However, a few of the wireless clients will connect to the further APs, which may be determined by the roaming mechanism of themselves. This article will introduce some of the factors that cause the wireless client not roam or connect to the nearest AP.
Factor 1: Interference or Network Congestion
Fast roaming requires a strong and stable Wi-Fi signal. High levels of interference or network congestion may hinder fast roaming. Other Wi-Fi networks, electronic devices, or physical obstacles can interfere with the Wi-Fi signal, which weaken AP's roaming performance to a great extent. Therefore, please avoid crowded Wi-Fi environments and minimize interference sources as much as possible.
Factor 2: Signal Strength Threshold
Roaming is primarily determined by signal strength. If the current AP's signal strength remains relatively strong, wireless clients may choose not to initiate a roaming process to connect to a closer AP. To trigger roaming, ensure that the current AP's signal strength is below a certain threshold.
Factor 3: Wireless Clients’ Limitations
Some wireless clients have roaming aggressiveness settings that determine how quickly they move between APs. If the roaming aggressiveness is set to a low value, clients may be less likely to roam to another AP. On the other hand, some clients may have limitations or compatibility issues with specific roaming protocols or AP configurations. For this case, please check your clients' settings and adjust the roaming aggressiveness as needed.
Factor 4: Coverage and Placement
Roaming performance can be affected by inadequate coverage or incorrect placement of APs. It is important to ensure that the APs are strategically positioned in areas where clients are expected to roam for providing sufficient coverage and overlapping signals. Conducting a site survey can help identify weak signal areas or coverage gaps. Ensure that your Wi-Fi network has appropriate range and signal strength, allowing seamless roaming without any disruptions.
Factor 5: Configuration on the Controller
- When the Lock to AP function is enabled on the Controller, the wireless clients can only connect to the selected APs. If the nearest AP is not selected, the client will not be able to connect to it.
- When a specific frequency radio is disabled for certain APs on the Controller, while the client happens to be connected to the disabled radio, the client will not be able to connect to it which is exactly the nearest AP.
- When the SSID Override function is enabled for certain APs on the Controller, the APs in the network may not all have the same SSID, which may result in the client unable to connect to the nearest AP.
- With WLAN Optimization enabled, the network will try to use more non-overlapping channels. Some outdated clients may not support all the channels currently deployed in the network, which may result in the client unable to connect to the nearest AP as well.
In summary, Any of the above factors may cause wireless clients fail to roam / connect to the nearest AP. To benefit from the Fast Roaming feature on Omada AP, please ensure:
- All the APs and the wireless clients support 802.11k and 802.11v protocols.
- Omada Controller is managing the APs properly and keep running.
- All the APs are having the same SSID and security settings.
- The wireless coverage between adjacent AP is overlapped for 20%-30%.
- It's better to choose different channels to reduce wireless interference between APs.
- As the roaming-related information is maintained by the Omada Controller, Fast Roaming function takes effect only when the Omada Controller is running.
If the problem still exists after trying the above operations, please contact TP-Link technical support for the further help.
Get to know more details of each function and configuration please go to Download Center to download the manual of your product.
Is this faq useful?
Your feedback helps improve this site.
What’s your concern with this article?
- Dissatisfied with product
- Too Complicated
- Confusing Title
- Does not apply to me
- Too Vague
- Other
We'd love to get your feedback, please let us know how we can improve this content.
Thank you
We appreciate your feedback.
Click here to contact TP-Link technical support.
TP-Link Community
Still need help? Search for answers, ask questions, and get help from TP-Link experts and other users around the world.
We have updated our Policies. Read Privacy Policy and Terms of Use here.
This website uses cookies to improve website navigation, analyze online activities and have the best possible user experience on our website. You can object to the use of cookies at any time. You can find more information in our privacy policy .
We have updated our Policies. Read Privacy Policy and Terms of Use here.
This website uses cookies to improve website navigation, analyze online activities and have the best possible user experience on our website. You can object to the use of cookies at any time. You can find more information in our privacy policy .
Basic Cookies
These cookies are necessary for the website to function and cannot be deactivated in your systems.
TP-Link
accepted_local_switcher, tp_privacy_base, tp_privacy_marketing, tp_smb-select-product_scence, tp_smb-select-product_scenceSimple, tp_smb-select-product_userChoice, tp_smb-select-product_userChoiceSimple, tp_smb-select-product_userInfo, tp_smb-select-product_userInfoSimple, tp_top-banner, tp_popup-bottom, tp_popup-center, tp_popup-right-middle, tp_popup-right-bottom, tp_productCategoryType
Livechat
__livechat, __lc2_cid, __lc2_cst, __lc_cid, __lc_cst, CASID
Youtube
id, VISITOR_INFO1_LIVE, LOGIN_INFO, SIDCC, SAPISID, APISID, SSID, SID, YSC, __Secure-1PSID, __Secure-1PAPISID, __Secure-1PSIDCC, __Secure-3PSID, __Secure-3PAPISID, __Secure-3PSIDCC, 1P_JAR, AEC, NID, OTZ
Analysis and Marketing Cookies
Analysis cookies enable us to analyze your activities on our website in order to improve and adapt the functionality of our website.
The marketing cookies can be set through our website by our advertising partners in order to create a profile of your interests and to show you relevant advertisements on other websites.
Google Analytics & Google Tag Manager
_gid, _ga_<container-id>, _ga, _gat_gtag_<container-id>
Google Ads & DoubleClick
test_cookie, _gcl_au
Meta Pixel
_fbp
Crazy Egg
cebsp_, _ce.s, _ce.clock_data, _ce.clock_event, cebs
Hotjar
OptanonConsent, _sctr, _cs_s, _hjFirstSeen, _hjAbsoluteSessionInProgress, _hjSessionUser_14, _fbp, ajs_anonymous_id, _hjSessionUser_<hotjar-id>, _uetsid, _schn, _uetvid, NEXT_LOCALE, _hjSession_14, _hjid, _cs_c, _scid, _hjAbsoluteSessionInProgress, _cs_id, _gcl_au, _ga, _gid, _hjIncludedInPageviewSample, _hjSession_<hotjar-id>, _hjIncludedInSessionSample_<hotjar-id>
lidc, AnalyticsSyncHistory, UserMatchHistory, bcookie, li_sugr, ln_or