Why port forwarding feature is not working on my Wi-Fi router or Deco?
Archer C1200 , Archer C5400 , Deco X20 , Archer C4 , Deco BE65-5G , Archer C5 , TL-WR843ND , Deco M1300 , Archer AX10 , Archer C2 , Deco HC4 , Archer AX96 , Deco X25 , Archer C6U , Deco Voice X50 , TL-WDR3600 , Deco X4300 Pro , TL-WR741ND , TL-WR940N , Archer C80 , Deco W6000 , Archer AXE95 , Archer C8 , Archer AX10000 , Archer C9 , Archer C6 , Archer C7 , TL-WR1043ND , Archer AX90 , Deco X3600 , Archer C5400X , Deco X1500-4G , Archer A20 , Archer C60 , Deco X50-PoE , Archer A1200 , Archer C64 , Deco W7200 , TL-WR941ND , Deco P9 , Deco P7 , Deco X20-DSL , Archer C59 , Archer C58 , Archer AX4200 , Archer C3200 , Archer A2 , Archer AX75 , Archer AX73 , Deco X20-4G , Archer A10 , Deco PX50 , Archer C50 , Archer C55 , Archer C54 , Deco S7 , Deco S4 , Archer AXE75 , Archer A6 , Archer A7 , Archer AX72 , Deco XE70 Pro , Archer A5 , Deco X90 , Archer A8 , Deco X3000-5G , Archer A9 , Deco W2400 , Archer AX68 , Archer AX5300 , Deco X96 , Archer C4000 , Deco XM73 , Deco XE75 Pro , Deco XE200 , TL-WR842N , Deco M9 Plus , TL-WR841HP , Archer AXE300 , Archer AX1500 , TL-WDR4900 , Archer AX60 , Deco M3W , Archer AX3000 , Deco W3600 , Archer A2600 , Archer AX55 , TL-WR841ND , Archer C5200 , Archer AX53 , Deco X68 , Archer AX51 , Archer C50 V3.0 , Deco WM9000 , Archer C5 V4 , Archer A2200 , Deco X58-4G , Deco X5700 , TL-WR743ND , Archer C20(ISP) , Deco XE5300 , Archer C3150 , Archer AX50 , Archer C20 V4 , Deco M5 , Deco M4 , Deco XE75 , Deco M3 , Archer AX6000 , Archer C25 , Deco X75 , Archer C24 , DecoX5700 , Deco X50-4G , Archer A64 , Archer C2 V1 , Archer AX10/A , Archer C2600 , Archer C21 , Archer C20 , TL-WR840N , Archer C2 V3 , Archer A10 Pro , Archer AX1800 , Deco X50-Outdoor , Deco Voice X20 , Deco X73-DSL , Deco X50-5G , Deco X80 , Deco HB6300-PoE , Archer AX206 , Deco 5G , Deco M5 Plus , TL-WR842ND , Archer C900 , Archer AX4400 , Archer C3000 , Archer C50
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.
Please follow the steps below for troubleshooting port forwarding failures on a TP-Link router.
Step 1: Make sure the server is accessible from the internal network
You will want to double-check the IP address and the port number of the server. Check if you can access that server in the local network. If you are unable to access the server in your local network, please check the settings of your server.
Step 2: Check the port forwarding settings in the router.
Step 3: Check the firewall setting.
Windows firewall will block the connection from the different subnet, and it will divide the difference according to the network location you have chosen. You may refer to Tip 2.
Step 4: Pay attention to the WAN IP address in the status page
If there are still problems, please check the WAN IP of the router. Verify the router is getting a public IP address. If it is a private IP address, which means it's not enough to only open the port on the TP-Link, you have to do the same setting on the modem router as well. You may refer to the Tip1 to check WAN IP.
But for the CG-NAT ISP: Comporium and Direct link - radio service, and most 3G/4G/5G ISPs, they usually provide the customer a private IP address or CGNAT address. CGNAT address ranges from 100.64.0.0 to 100.127.255.255, which looks like public IP address but actually not, therefore, it will also cause you unable to use the OpenVPN or port forwarding and affect the NAT Type. You could contact the ISP and ask them to offer a Public IP address.
Step 5: Check the IP setting on the client.
Some devices need to set static IP on the Internet setting. So the correct IP setting is necessary. The IP should be the same subnet as the router, and the gateway on the client’s setting should be the router’s LAN IP address.
If it is possible, we suggest you use DHCP to get IP from the router directly.
Tip 1: How to check the WAN IP address?
For Deco :
Launch the Deco app, and go to More>Internet Connection>IPv4 to check the WAN IP address of the Deco network.
For DSL Modem Router:
New designed blue UI:
New logo:
New UI:
For Wireless Router:
Green UI:
New designed blue UI:
New UI:
Gaming UI:
For 4G LTE Router:
New logo:
New UI:
Tip 2: How to change the Network Location for the clients?
Method 1:You can disable the firewall in the Control Panel-> System and Security-> Windows Firewall.
Click “Turn Windows Firewall on or off” to modify it.
If you have used some other firewalls such as Bitdefender, Norton, please uninstall them or set them in the silent mode.
Method 2: Change the network type to Home network/Private network.
For Win7 : Please go to Control Panel-> Network and Internet-> Network and Sharing Center.
Click it and choose “Home Network”.
For Win 10: Please go to Setting-> Network and Internet.
Click the connection which has been set up, then you can see the Network profile setting, save it as “Private”.
Note:
WAN IP should be a public IP address. The WAN IP is assigned dynamically by ISP. If the WAN IP address of the router is not a public IP address, but a private IP address, that means there is another NAT device connected to the WAN port of the router. You need to open the service ports on that device as well.
For most of the 4G LTE router, the internet service provider usually gives the private IP Address. So, if you want to do the port forwarding, please contact your internet service provider to assign you a public IP address or do the port forwarding in their part.
Please google if you don't know how to tell Public IP Address or Private IP Address.
Feel free to contact us if it's not working after the above steps.
Related FAQs
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.
Setup Videos
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