I 've setup a Windows Server 2008 machine as a VPN(PPTP) server. The server has two network interfaces - one private (192.168.9.0/24) and the other public (Internet). I've a Windows 7 PC connected to the server on local LAN, with IP 192.168.9.3 and gateway 192.168.9.1.
Secondly, I've a router at a remote location in which I've configured it as a VPN client and setup it up to connect to the VPN server via the WAN. The router's LAN has an IP 192.168.8.1 and is connected to a Windows 7 PC with IP 192.168.8.3 and gateway 192.168.8.1. The server's VPN settings are configured to use a IP pool of 192.168.7.1-192.168.7.20. The server takes up the 192.168.7.1 on the tunnel, and the remote router gets assigned for example, 192.168.7.5.
So far everything is fine, except that in my scenario I need the Win7 PC with 192.168.9.3 IP to connect to a TCP port (e.g., FTP) on the 192.168.8.3 Win7 PC through the VPN. This is the reverse of typical VPN requirement. I'm so far able to connect to the 192.168.8.3 PC using a client running on the server itself. The server correctly routes the traffic through the VPN tunnel to the remote end. I'm also able to ping the remote VPN tunnel end, i.e., 192.168.7.5 from the server.
However, if I run the same client application on the 192.168.9.3 PC and try to connect to the 192.168.8.3 PC, I can't get through. From this PC I can't even ping the remote VPN tunnel-end (192.168.7.5).
What could be the issue, and how to fix it?
Thanks!
VK
