TPLink Router VPN issues with connecting to file shares or other networks
TPLink Router VPN issues with connecting to file shares or other networks
I configured my TP link router for VPN setups (OpenVPN and PPTP). I can connect and log in to the router, but I can't reach any other devices on the network. A ping to an active machine showed no response, suggesting it's acting as a guest network instead of my home network. Anyone know how to resolve this? Since I'm away from home, I can only adjust router settings. One suggestion was to link server devices to a separate TP-Link VPN while running the VPN through the router itself—maybe that would work better. Refer to the forum thread here: https://community.tp-link.com/us/home/fo...pic/211434
Is there a separate network segment formed by the VPN? Are you able to send a ping to the file server? Could you access the shared folder directly by typing its IP address manually?
Normally, a VPN operates in its own subnet, which determines what you can reach. By default, it only permits access to the WAN and local router; to connect to the LAN, NAT rules are required to translate between the VPN and LAN networks. It’s also wise to avoid PPTP due to security concerns—even with encryption—it’s considered outdated and vulnerable. OpenVPN is a better choice. The recommended fix appears in the community forum, suggesting you check the advanced settings, go to network options, and enable static routing.
The static routing entry seemed to have no impact at all. I included a screenshot of my VPN configuration for clarity. It's worth noting I can reach devices on Wi-Fi but not over Ethernet. My wired Windows PC isn't responding, even though the router shows it's connected. The other server requires a WOL command to activate. Not surprising that it doesn't work. And happy holidays to you both!
You haven’t used this router much before, but it appears to have internet and local network settings selected. The advanced section likely shows your routing details—check if the default gateway matches your router’s IP address. For the subnet, 192.168.2.1 seems correct for that range.
The advanced tab now displays additional main menu choices. Current routing settings are working properly on the VPN menu. It seems the problem isn't with the VPN subnet mask. Consider testing a different static route entry. The router's IP is 192.168.1.1, and the VPN IP has been updated to 192.168.3.x in the screenshot.
I understand enough to manage my own setup, but I’m unsure what’s required for this router to function properly. It seems puzzling why your tunnel gateway is configured at 192.168.3.2 instead of 192.168.3.0.
TPLink set up their router to manage VPN connections in a peculiar manner, as indicated by similar problems reported by others. My previous Netgear router didn’t have this issue.
You require the VPN for specific purposes. It’s possible to configure it directly on the router rather than just setting up WiredGuard internally. There might be a device running continuously on your local network that needs protection. A Raspberry Pi could also serve this role.