RV180W PPTP: no access to clients or servers in remote LAN

[marco.spicher]

Hello

After searching a lot in the Internet about my issue without any success, I have to start my own discussion.

I set up the PPTP-Server and created a PPTP-User as described in the admin manual of the RC180W-Router. I can connect to the router through the build in VPN-PPTP function in Windows 7 and on my Android phone. Then, I can also ping the router and access the Web Management. But I cannot access the other clients and servers in my network, nor ping them.

My configuration is as follow:

• 3 VLANs:
  • VLAN1: 192.168.0.1 (255.255.255.0)
  • VLAN2: 192.168.2.1 (255.255.255.0)
  • VLAN3: 192.168.3.1 (255.255.255.0)
  • no inter-VLAN-routing
  • the clients and server I would like to access, are in VLAN1 and connected to the router on port 1.
• PPTP Configuration
  • Start IP: 192.168.0.201
  • End IP: 192.168.0.205
• Default firewall settings
• Remote Management on port 443 is enabled

If I connect to my router with VPN, I get the following informations on Windows 7:

• Athentification: MS CHA V2
• Encryption: MPPE 128
• Client IP: 192.168.0.202
• Subnetmask: 255.255.255.255
• Default Gateway: <none>
• Server IP: 192.168.0.201

Once connected, I can ping the router and access the Web Management on IP 192.168.0.1

I cannot access or ping any other client or server, for example 192.168.0.96

Regards,

Marco Spicer

[Ismael Arroyo · Accepted solution]

Marco,

I have noticed that you are in the same subnet at the PPTP Server subnet. Connecting PPTP clients would need to be in a different subnet other than 192.168.0.X. So an acceptable PPTP server configuration could be in 192.168.1.x subnet, as long its not in the 192.168.0.X subnet.  If this helps you and fixes your issue please mark your answer

[marco.spicher]

Thanks for your answer.

I changed the settings, so that the IP-range for PPTP is now from 192.168.4.1 to 192.168.4.6.

Still the same problem. I could ping and access the router at 192.168.0.1 but nothing else in the subnet 192.168.0.x

Then I created another VLAN for the subnet 192.168.4.x with enabled Inter-VLAN-Routing. And I also had to enable Inter-VLAN-Routing on my default VLAN (192.168.0.x). Now everything works perfect!

So, the solution is:

• PPTP IP range has to be in a different subnet than the "target" subnet
• PPTP IP range has to be part of a VLAN
• Inter-VLAN-Routing has to be enabled for this PPTP-VLAN and the "target" VLAN