ksj2010
asked on
VPN Connection with Netgear FVS318N
Hello Experts,
I have recently purchased a Netgear FVS318N router to connect to my small office (one server, three workstations) via VPN. I have setup a VPN policy and am able to connect from my iPad, iPhone and MacBook (OS X Lion) and I receive an IP address, however I am not able to Remote Desktop to the server or my desktop from this connection.
I believe I have the IPSec connection setup properly, when I connect to the VPN I receive an IP address from the internal network and I can see the DNS Server in the DNS lookup for it. However, I can't ping or RDP. Do I need to setup a policy or ... ?
Thanks!
Kris
I have recently purchased a Netgear FVS318N router to connect to my small office (one server, three workstations) via VPN. I have setup a VPN policy and am able to connect from my iPad, iPhone and MacBook (OS X Lion) and I receive an IP address, however I am not able to Remote Desktop to the server or my desktop from this connection.
I believe I have the IPSec connection setup properly, when I connect to the VPN I receive an IP address from the internal network and I can see the DNS Server in the DNS lookup for it. However, I can't ping or RDP. Do I need to setup a policy or ... ?
Thanks!
Kris
ASKER
Excellent suggestion! The remote location that I was testing from was also one of "my" networks, so the remote and local subnets were the same. I reconfigured my local LAN to 192.168.3.x and went to another location. Again I was able to connect to the VPN, but was not able to move any traffic over it.
Thanks for the suggestion. Any other ideas?
Thanks for the suggestion. Any other ideas?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
My own troubleshooting resolved the issue.
For instance, if both LANs are on the 192.168.0.x subnet, your computer will not be able to tell whether, say, 192.168.0.101, is a local or a remote IP address.
The easiest way to solve this is to change the subnet of your home LAN to something not commonly used by other LANs (i.e. not the Netgear or Dlink or LinkSys default subnets).
Change the home LAN to the 192.168.7.x subnet, for instance, and see if that solves your problem.