Go to the Firewall--->Attack Defense and un-check the Block ping from WAN

Unchecking "Block Ping from WAN" had no affect. It doesn't work for me either.

Need to be able to use VPN for remote client to connect to LAN. Isn't that the whole point? Without this functionality the router is useless for remote clients.

I have the same issue. Not allowing remote clients connected to the VPN onto the same subnet as local computers completely breaks any functionality for file sharing or using resources on the LAN

I am having the same issues. Has anyone been able to figure it out yet?

So I've followed the step by step VPN instructions and I can see the tunnel is up. But I can't ping any of the resources in the remote network. So I ran a trace route and saw that the router is still forwarding the trace out the wan port. What is the TUN port address? My local subnet IP is 192.168.1.0 the remote subnet is 192.168.0.0.

Any help is appreciated.

I think I found a clue to my issue and that is one of double NAT - ISP provides a dsl modem/router that NAT the public IP. The 600 vpn sits behind this router
the 600vpn is connected directly behind a cable modem on the other end. Ipsec tunnels are up, The side with the double nats can see resources at the end with only one NAT, while that end cannot see beyond the end of the Tunnel on the double NAT side.

I'm not sure if double natting is an issue, if so then a work around is needed. It could also be the problem on the previous posters.

yodermeister wrote

Unchecking "Block Ping from WAN" had no affect. It doesn't work for me either.

Need to be able to use VPN for remote client to connect to LAN. Isn't that the whole point? Without this functionality the router is useless for remote clients.

I can ping, tracert and browse remote lan computer by ip address of remote Lan but unable to resolve by name. It is very funny but i need to browse remote pcs by name not by ip address. Is there any solution?

robeen wrote

I can ping, tracert and browse remote lan computer by ip address of remote Lan but unable to resolve by name. It is very funny but i need to browse remote pcs by name not by ip address. Is there any solution?

How did you get your lan computers to ping? I have tried everything...

Any results ?

I believe that my issue may be NATing as well. However, an OpenVPN client at the same remote location has no problem connecting to our main pfSense firewall that is on an adjacent IP.

I was able to get traffic through for a while, but after rebooting the TPLink reouters, the traffic fails again. Additionally, I had a test network setup locally and was unable to get TPlink 604W IPsec to pass traffic to pfSense IPsec primary router. In that case, I had to "mess" with the settings on the pfSense end. Eventually, the link would show as established, but then I got the same problem as TPlink head to head..... no traffic would pass through the VPN.

I really need this to work because it took too long for TPlink support to answer questions so the hardware vendor will no longer accept the units as returns.

I have a feeling this router is advertising capabilities that it doesn't really have. I followed their instructions exactly and tried every type of Client to LAN VPN and the PPTP tunnel is the only one that worked for a connection. Since I cannot even get to my local machines, it is useless.

The logging is horrible so I have to depend on client logs which are very hard to interpret. I think I'm going to return it and get something that might not have all the features they market, but I only care if they work. This appears to be a poorly designed router, the performance inside my network is worse then my old DIR-655.

I'm a system administrator and built the remote vpn and site to site vpns at work, but I cannot figure this thing out.