Edit,

Sorry I miss your point just now.

remote hosts ------------(internet)---------------600VPN -------LAN hosts

If the remote hosts can access the LAN hosts, the route should be no problem. Check the firewall on the remote ones.

Hi radvd, agreed they are all connected, both LAN and VPN clients are successfully connected to the R600VPN.

However I'm unable to establish any connection with the VPN clients from workstations within the LAN, this is what I want to achieve.

192.168.2.x (LAN workstations) ---------------- ping ----------------> 192.168.3.x (VPN clients)

can the remote hosts ping the LAN hosts in reverse?

Yes the remote hosts can ping the LAN hosts without issue.

That is really strange. I think you may check the firewall and PPTP settings on the remote clients first.

May also tracert the remote host from the LAN host to check the route.

On a LAN host, run cmd:
tracert 192.168.3.x

I won't have a chance to get to any of the remote workstations until the end of the week, so I'll have to provide an update then.

I did quickly connect to the VPN with my android phone - that can also ping the LAN-side workstations without issue, but when pinging my android device from the LAN I just receive "Request timed out" responses. Firewall settings will obviously be different though.

Are there any obvious settings I should be looking for in the PPTP options on the remote clients? They're all running Windows XP.

You should use the PPP IP address of the client as the destination when access from LAN.

ryan.gillies wrote

Region : Taiwan

Model : TL-R600VPN

Hardware Version : V2

Firmware Version : 1.2.2 Build 140530 Rel.35298n

ISP :

Hi all

I've been using the TL-R600VPN now for a couple of weeks without issue, and wanted to start expanding on its functions.

We have a number of remote machines which are now connecting to the router via PPTP. All of the client machines can successfully connect and access resources on the network.

However from the LAN side I'm unable to ping or connect with any of the client workstations.

Our LAN is running on a subnet of 255.255.0.0 spread across the 192.168.1.x and 192.168.2.x IP ranges. The VPN server is allocating addresses to its clients on the 192.168.3.x IP range. I tried moving the IP range of the VPN clients to 192.168.2.x as well but that wasn't successful.

The static routing table shows the clients connected, but I'm not overly familiar with how to interpret it. Its showing the external and internal IP of the clients in the destination network fields, all with a subnet of 255.255.255.255 and a gateway of 0.0.0.0

Can anyone enlighten me as to what I'm missing? Many thanks.

Rouer_man wrote

You should use the PPP IP address of the client as the destination when access from LAN.

I've tried this (with my android device at least) and receive a timeout error as well when pinging. However even if this were to work, it defeats the objective I want to achieve of programatically connecting to the remote hosts, as I won't know what the PPP IP is, I only know for certain the 192.168.3.x range.

Also, wouldn't connecting to the PPP IP be a connection over WAN, not over the VPN?

I will hopefully be going out to a couple of the above sites later this afternoon to do some more testing, however I have done some further investigation and believe I've identified the problem.

- I used a computer within the LAN to connect to the VPN - no issues with connections in either direction, so not much help here.

- I have been able to connect to one remote VPN client successfully - this remote client also happens to be the only workstation that connects directly to the internet via a PPPoE dialup, all the other remote clients connect via a router. This leads me to believe a firewall setting on the router is causing the issue.

Do these routers need to have PPTP passthrough available and enabled for me to connect to the remote clients from the LAN? Or does anyone know if I can simply open up port 1723 and direct it accordingly? I ask this in advance because I may need potential workarounds - the remote clients are installed with accompanying routers via a third party company, so if the router can't handle passthrough I'll need an alternative.

I have the same problem....

the vpn is working and from one side i reach with ping the lan ip of the other router....But I can´t reach with ping the computers of the remote lan......

With samba i can´t get either...

Any solution......