greatfestive wrote

Our setup is:

LAN 10.11.8.0/255.255.248.0

Now my clients can connect fine, the get IP address in the 172.31.10.100+ range.

However the clients cannot connect to the 10.11.8.x network automatically.

Hello,

I have the same situation as you do.

My setup is (following TP-Link example as describe in: http://www.tp-link.com/en/article/?id=385):
- ER6120 LAN IP address 192.168.0.1 / 255.255.255.0
- LAN IP address range 192.168.0.0 / 255.255.255.0
- PPTP VPN clients IP address range 172.31.10.10+ / 255.255.255.255

My clients can connect through PPTP, can get IP address in the 172.31.10.10+ range, but cannot connect to the local network.

Ping from client (172.31.10.10) to 192.168.0.1 (ER6120) have been successfully replied.
But ping to other LAN IP address range (192.168.0.2 - 192.168.0.254) always "Request Time Out"

I also tried configure the static route:
Destination: 172.31.10.0
Subnet Mask: 255.255.255.255
Next Hop: 192.168.0.0
Interface: LAN
Metric: 1

But did not work, the ping result from client to 192.168.0.2 - 192.168.0.254 always "Request Time Out", only ping to 192.168.0.1 (ER6120) replied.
Contact TP-Link support a week a go but no response until now.

I can add static routes on the client and make this work, but I'd rather not. I don't want clients to send all traffic through the VPN.

Please let me know, how do you add the static routes to make it work?

Thank you.

Wieb for static routes on the client (in this case Mac OSx) you can simply do:

/sbin/route add 10.11.8.1/21 -iface ppp0

Theres a fairly similar way to do this in Windows. Linux is pretty straightforward as well.

What do you mean by "However the clients cannot connect to the 10.11.8.x network automatically".
Do you mean you can't ping the LAN IP address of TL-ER6120?

I don't think it is a problem of TL-ER6120 as you can Ping the LAN IP address of TL-ER6120.
The thing is the firewall of all the PCs in the LAN network will block the Ping test.
In other word, if you disable the firewall on all your PCs, then the Ping test will be OK.

greatfestive wrote

Wieb for static routes on the client (in this case Mac OSx) you can simply do:
/sbin/route add 10.11.8.1/21 -iface ppp0
Theres a fairly similar way to do this in Windows. Linux is pretty straightforward as well.

PPTP client (172.31.10.10) Windows route interface list :

===========================================================================
Interface List
37...........................VPN Connection
12...bc 5f f4 b0 19 49 ......Intel(R) Ethernet Connection I217-V
1...........................Software Loopback Interface 1
13...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter
14...00 00 00 00 00 00 00 e0 Teredo Tunneling Pseudo-Interface
19...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #2
===========================================================================

According to interface list above, I have been added this route on Windows PPTP client (172.31.10.10):

route add 192.168.0.0 MASK 255.255.255.0 192.168.0.1 METRIC 5 IF 37

But it didn't work, although the ER6120 (192.168.0.1) firewall has been turned off and also the firewall on all the PCs on local network (192.168.0.2 - 192.168.0.254) .

Just like previously before added the static route above, ping from PPTP client (172.31.10.10) to 192.168.0.1 (ER6120) have been successfully replied.
But ping to other LAN IP address range (192.168.0.2 - 192.168.0.254) always "Request Time Out"

For static routes on the client

Instead ER6120, I also have Cisco RV04 which more easier to setup than TP-Link ER6120.
In Cisco RV04, we don't have to add static route on each PPTP clients (client side), but it is enough added inside Cisco RV042 static route table itself (server side).

So any clients which connected to PPTP server (RV042) will has the same static route because the static route already setup in server side.
Less trouble and less headache if we could setup the static route on server side. :)

Can we do this on ER6120?
Please help.

Vincent wrote

I don't think it is a problem of TL-ER6120 as you can Ping the LAN IP address of TL-ER6120.
The thing is the firewall of all the PCs in the LAN network will block the Ping test.
In other word, if you disable the firewall on all your PCs, then the Ping test will be OK.

Instead TP-Link ER6120, we also have Cisco RV042.
The purpose we bought ER6120 because ER6120 has more PPTP clients (32 clients max) than RV042 (5 clients max).

So in our local network, we have 2 separate incoming PPTP connections (from RV042 and from ER6120) which use 2 separate WAN connections.
If there is a firewall problem in local network, the PPTP clients ping test from both RV042 and ER6120 should be fail.

But unfortunately, the PPTP clients ping test from RV042 are fine.
The PPTP clients from RV042 can do ping to all PCs in local network without trouble.

Only the ping test from ER6120 PPTP clients are fail, so I think this is not firewall problem which block the ping test but static route problem on ER6120.

Please help.

Your description is a little confusing.
Anyway you can follow the FAQ below to configure your TL-ER6120.

If your TL-ER6120's PPTP is working on lan-to-lan mode, please click the following link:
http://www.tplink.com/en/article/?faqid=411

If your TL-ER6120's PPTP is working on client-to-lan mode, please click the following link:
http://www.tplink.com/en/article/?faqid=385

Vincent wrote

If your TL-ER6120's PPTP is working on client-to-lan mode, please click the following link:
http://www.tplink.com/en/article/?faqid=385

I have been followed http://www.tplink.com/en/article/?faqid=385, please see on post #2 above.

My setup is (following TP-Link example as describe in: http://www.tp-link.com/en/article/?id=385):
- ER6120 LAN IP address 192.168.0.1 / 255.255.255.0
- LAN IP address range 192.168.0.0 / 255.255.255.0
- PPTP VPN clients IP address range 172.31.10.10+ / 255.255.255.255

My clients can connect through PPTP, can get IP address in the 172.31.10.10+ range, but cannot connect to the local network.

Ping from client (172.31.10.10) to 192.168.0.1 (ER6120) have been successfully replied.
But ping to other LAN IP address range (192.168.0.2 - 192.168.0.254) always "Request Time Out"

As you could see, I tried to follow the FAQ as exactly as possible, the setup and all of the IP addresses are identical as described on FAQ http://www.tplink.com/en/article/?faqid=385

Your description is a little confusing.

My question is simple:
- How to setup ER6120 so the PPTP clients (172.31.10.10+ range) can connect to the local network (192.168.0.2 - 192.168.0.254)?

For the note, the FAQ on http://www.tplink.com/en/article/?faqid=385 only explained about "how to connect PPTP clients to ER6120".
But not explained about "how to connect PPTP clients to local network through ER6120" (which I need it)

Please help.

This is to clarify the problem, there is no posibility to access to another IP in the same network, except ip of router on L2TP or PPTP configurations.

We check that: Tunnel is ok, ping over router ip is ok too, tracert over this ip is ok, but tracert over another ip in same tunnel goes through WAN, no to LAN. ¿WHY?

We have checked to put and static route no ping too.

We check to install older firmware version 1.0.2_P5 // 20120719, same...

Is there some one that tested it and got it??, Really????

Hello everybody,

Is there any one that test configuraton explained on http://www.tplink.com/en/article/?faqid=385?. As stated on this thread ping to LAN doesnt works Someone can send exact configuration to config that?

Thanks !!!!