Scenario:
The office has a network with private IP:s ranging from 192.168.0.1 (the FVS318 router) to 192.168.0.255. The router has been set up for VPN according to instructions from Netgear docs, same goes for the ProSafe client.
The router can be accessed through a fixed IP or a DNS address. However, all traffic through this IP is forwarded to the fixed WAN IP of the router, which is 192.168.3.100. So, in other words, the public IP of the router is not the same as the one specified as the fixed WAN IP in the router configuration.
Whenever I try to access an IP of the office network, or try to manually establish the VPN tunnel, I get this message from the ProSafe client log:
7-13: 13:53:22.097 My Connections\OFFICE - Attempting to resolve Hostname (vpnrouter.wlst.se)
7-13: 13:53:22.147 My Connections\OFFICE - Initiating IKE Phase 1 (Hostname=vpnrouter.wlst.s
e) (IP ADDR=xxx.xx.xx.xxx)
7-13: 13:53:22.167 My Connections\OFFICE - SENDING>>>> ISAKMP OAK MM (SA, VID 2x)
7-13: 13:54:07.252 My Connections\OFFICE - message not received! Retransmitting!
7-13: 13:54:07.252 My Connections\OFFICE - SENDING>>>> ISAKMP OAK MM (Retransmission)
All settings have been configured in exact accordance with the instruction doc from Netgear regarding Client-to-gateway setup, except for the Shared Key that is... I have tried disabling the firewall software on the client (which runs with a dynamic IP by the way), but that has no effect.
I have no clue what to do about this, so any help would be greatly appreciated. Is there any reason why it would cause problems to have a different WAN IP set than the one that the client is trying to access the router through?
Start Free Trial
