What If I fail to establish EasyMesh network using TP-Link EasyMesh devices?

Archer AC1900 , Archer AX55 , RE715X , Archer AX53 , Archer AX10 , RE205 , Archer C80( V1 V2.20 ) , Archer C6( V4 ) , RE210 , RE330 , RE450 , RE315 , RE700X( V1 ) , Archer A64 , RE1750X , Archer C64 , RE780X , Archer AX1800 , Archer AX80( V1 ) , RE200 , Archer C59( V4.6 V4.80 ) , RE300 , Archer AX4400 , RE305 , Archer AX73 , RE765X , RE600X , Archer AC1900(USW) , Archer AX80V , RE190 , Archer A6( V4 ) , Archer AX72 , Archer AXE5400V , RE705X , RE550( V1 ) , Archer A8( V1 V2.20 ) , RE605X , Archer AX3000 Pro , Archer AX23( V1 V1.20 ) , Archer AX20( V3 ) , Archer AX21 , Archer AX3000V , Archer AX55 Pro , RE580X , Archer C88 , Archer C86 , Archer AX1500 , RE750C , RE2700X , RE220 , Archer AX3000( V2 V2.6 )
As actualizações recentes podem ter expandido o acesso às funcionalidades abordadas nesta FAQ. Visite a página de suporte do seu produto, selecione a versão de hardware correta para o seu dispositivo e consulte a Folha de dados ou a secção de firmware para obter as mais recentes melhorias adicionadas ao seu produto. Tenha em atenção que a disponibilidade do produto varia consoante a região e que determinados modelos podem não estar disponíveis na sua região.
If you have already tried to configure the EasyMesh network using TP-Link devices but it failed, please check the following troubleshooting.
There are two scenarios in relation to the EasyMesh configuration issue, please refer to the information below to locate the problem and troubleshoot it according to the corresponding suggestions:
1) If no satellite devices can be detected or satellite device is detected but cannot be added successfully when adding EasyMesh satellite devices on main router, please refer to Case 1.
2) If the EasyMesh page on Main Router only shows wireless connection even though Ethernet cable is connected between main router and satellite devices, please refer to Case 2.
Case 1: cannot establish wireless backhaul
1) Please make sure both the Main Router and Satellite devices have already supported EasyMesh and have the latest EasyMesh-Supported firmware.
Refer to: TP-Link EasyMesh Devices
2) Please make sure the EasyMesh is enabled on Main Router and Satellite devices.
3) Make sure the satellite router has been reset or set to satellite mode.
Note: For TP-Link satellite router, after you reset it or set it to satellite router mode, please don’t log in to its Web management page again.
4) Move the satellite device close to the main router to ensure a good WiFi connection between them.
5) Please try to add the satellite device via both web interface and also via WPS to see if both of them don't work.
Refer to the following guides for adding Satellite Router/Range Extender (two methods included):
How to add a router to an EasyMesh network as a satellite device
How to add an extender to an EasyMesh network as a satellite device
6) Reset the satellite devices and repeat the EasyMesh configuration process.
Case 2: cannot establish Ethernet backhaul
1) Make sure both the Main Router and Satellite devices have already supported EasyMesh Ethernet Backhaul and have the latest Ethernet Backhaul-Supported firmware.
Refer to: EasyMesh Routers Support Building a EasyMesh Network via Ethernet Backhaul NOW
2) Refer to this guide to make sure the configuration process is correct:
How to Build an Ethernet Backhaul Using Two EasyMesh Routers
How to build an Ethernet Backhaul using TP-Link EasyMesh Range Extenders
3) Make sure the Ethernet cable between main router and satellite device is working fine, try different Ethernet cables for testing
4) Connect satellite device directly to the main router if there is a switch or something in between.
5) Try to use different Ethernet/LAN port on Main router and Satellite devices as the backhaul port.
6) Reset the satellite device and repeat the EasyMesh configuration process.
If the above troubleshooting steps cannot solve the problem for both cases, please contact the TP-Link support and provide the following information for further troubleshooting:
a. the main router and satellite device’s model, hardware and firmware version.
b. detailed topology of your whole network.
c. detailed description of the current problem, provide some screenshots if possible.
Este guia foi útil?
A sua resposta ajuda-nos a melhorar o nosso site.
Qual é a sua preocupação com este artigo?
- Insatisfeito com o produto
- Demasiado Complicado
- Título Confuso
- Não se aplica a mim
- Muito Vago.
- Outro
Obrigado
We appreciate your feedback.
Click here to contact TP-Link technical support.
Este site utiliza cookies para melhorar a navegação no site, analisar atividades online e proporcionar aos utilizadores a melhor experiência no nosso site. Pode opor-se à utilização de cookies a qualquer momento. Pode aprender mais informações no nosso política de privacidade .
Your Privacy Choices
Este site utiliza cookies para melhorar a navegação no site, analisar atividades online e proporcionar aos utilizadores a melhor experiência no nosso site. Pode opor-se à utilização de cookies a qualquer momento. Pode aprender mais informações no nosso política de privacidade .
Os cookies são necessários para o funcionamento do website e não podem ser desativados nos seus sistemas.
TP-Link
accepted_local_switcher, tp_privacy_banner, tp_privacy_base, tp_privacy_marketing, tp_top-banner, tp_popup-bottom, tp_popup-center, tp_popup-right-middle, tp_popup-right-bottom, tp_productCategoryType
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
Os cookies de analise permite-nos analisar as suas atividades no nosso website para melhorar e ajustar a funcionalidade do nosso website.
O cookies de marketing podem ser definidos através do nosso website pelos nossos parceiros publicitários de forma a criar um perfil dos seus interesses e mostrar-lhe anúncios relevantes em outros 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
lidc, AnalyticsSyncHistory, UserMatchHistory, bcookie, li_sugr, ln_or