Solution Cannot open 1701 port on Archer C80
This Article Applies to:
Archer C80_V1
Issue Description/Phenomenon:
There are cases that customers want to access a local L2TP/IPSec VPN server from an outside network, thus they will be required to open some specific ports on the gateway router, such as port 500, 4500, and 1701.
Typical network layout would be as follows:
However, customers will find they cannot open port 1701 on the Archer C80, it reports an error "Conflicting with existing port: 1701. To avoid conflict, please enter another value.". This is because the 1701 port is reserved for the L2TP WAN connection on the Archer C80 with the previous firmware, and you cannot open it for another server.
Available Solutions:
Step 1
Update and install the latest firmware for the Archer C80, which is Archer C80_V1_1.11.30 Build 220624, then try to open port 1701 for the local L2TP/IPSec VPN server on the router.
Step 2
If you still fail to open port 1701 on the C80, please disable the IPSec Passthrough on the router. You can find it under the Advanced > Security > ALG page as follows:
Related Articles:
How to open a range of ports on Archer C80
Port forwarding: how to set up virtual server on TP-Link wireless router?
Why port forwarding feature is not working on my router?
-------------------------------------------------
Have other off-topic issues to report?
Welcome to > Start a New Thread < and elaborate on the issue for assistance.
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Hi, I tried it and seems to be OK. Port has been forwarded and vpn worked. Thanks
- Copy Link
- Report Inappropriate Content
Glad to know it works.
- Copy Link
- Report Inappropriate Content
Hi, Can the problem be resolved for port 44158 as well?
I have the same error on an Archer A64 for port 44158
Thanks!
- Copy Link
- Report Inappropriate Content
xCS wrote
Hi, Can the problem be resolved for port 44158 as well?
I have the same error on an Archer A64 for port 44158
Thanks!
Can you confirm which device or service you were trying to open port 44158 for? Be sure that this port is not occupied by any other devices or services in the network. You can do a simple test like the below:
Disconnect all devices from the A64 network, or power them off when that's convenient, then restart the A64 to release the connections, connect only one device to the A64 after the restart, then confirm if you can open port 44158.
- Copy Link
- Report Inappropriate Content
Hi, I'm having the same Problem on Port 5060 for SIP on a C80 v1 , latest official fw.
5060 can't be used as internal or external port in any forwarding
I've tried disabling everything under ALG, firewall but the port always conflicts with a invisible 5060.
This is quite urgent as the clients office cannot receive phone calls anymore.
Thank you.
- Copy Link
- Report Inappropriate Content
Hi, I removed the internet cable and any wire was connected to the device and then I could do portforwarding.
Success!
- Copy Link
- Report Inappropriate Content
After reading through the related threads I tried both, but neither disabling UPnP and restarting nor removing the ethernet cables during reboot helped me.
- Copy Link
- Report Inappropriate Content
PBS-ASIA wrote
After reading through the related threads I tried both, but neither disabling UPnP and restarting nor removing the ethernet cables during reboot helped me.
@PBS-ASIA Can you describe the issue in detail? How did you test if the port 5060 is open or closed and why do you need to open port 5060?
- Copy Link
- Report Inappropriate Content
Thank you for your reply.
I too, got the error message of conflicting ports when trying to set it up, just with port 5060 not 1701 or any other aforementioned port.
So I was never able to save the port forwarding in the first place.
While this needs to be addressed by your colleagues for sure, in my case it's not important anymore because I was able to send the tp link device back to the vendor and will use a different product.
Thank you.
- Copy Link
- Report Inappropriate Content
Hello
HW:
Firmware Version:
1.11.30 Build 220624 Rel.50807n(4555)
Hardware Version:
Archer C80 1.0
I am having a similar issue after updating to C80_V1_1.11.30 Build 220624; this worked while I was on the beta firmware which was posted here a while ago (post was edited since then) -- I can't downgrade either :-(
The network layout is very simple :
Router connects to the internet through PPPOE and my Synology NAS (running L2TP VPN) is connected to router (wired). I have a few other devices on my network (IoT devices, Tv etc)
I am able to connect to the VPN server from inside the network (by using the local ip -- 192.168.0.105) but I am not able to do that from outside the network even though the pass-through option is enabled and ports are forwarded.
Just to reiterate, this worked on the beta fw that was posted here (c80v1-up-noboot_2021-02-19_10.17.18.zip)
I've tried with no other devices/cables connected, except WAN and Synology after multiple factory resets but to no avail.
DMZ doesn't work either
Here's my router config:
Thank you
-Alex
- Copy Link
- Report Inappropriate Content
Information
Helpful: 8
Views: 9095
Replies: 28
Voters 5
