If the VPN gateway is not the default gateway, you will in many cases need a suitable routing setup in order for responses to reach you. Is your VPN gateway the default gateway (router) of its network? VPN Tracker automatically runs the test for every new Internet connection it is able to detect but even if a connection has been tested before, there are various reasons why the behavior of that connection may have changed in the meantime.ħ. The results of this test depend on the capabilities of your local Internet router/modem or the Internet connection itself and they influence how the VPN tunnel is established. The VPN Availability Test can be found in the menu: Tools > VPN Availability Test. If you can't ping anything, try re-running the VPN Availability Test So if you can ping that address but no other remote address, it is most likely a routing issue at the remote end.Ħ. The LAN address of the VPN gateway is special in the regard that this address doesn’t need to be routed at all.

You can find a ping tool directly in VPN Tracker under Tools > Ping Host. Can you ping the LAN address of the VPN gateway? If that field is empty in your configuration, VPN Tracker will just use the IP address of your primary network interface as local address, and of course, this can also cause an address conflict with another user, that’s why we do not recommend to leave that field empty if there are multiple VPN users.ĥ. If multiple VPN users exist, pleas make sure no two users are using the same local address (Basic > Local Address), otherwise one of them will not be able to use the tunnel anymore whenever both of them are connected. Could multiple VPN users use the same local address? Refer to the configuration guide for your VPN gateway for more information.Ĥ. Mode Config, EasyVPN, DHCP over VPN) you may be able to assign a local address to VPN Tracker that is part of the remote network. If you are using an automatic configuration method (e.g. For example, if your remote network is 192.168.13.0/24, do not use an address starting with 192.168.13. Please use a local address that is outside all remote networks. Using a local address in VPN Tracker (Basic > Local Address) that is part of the remote network is not possible with most VPN gateways.

Is the local address in VPN Tracker part of the remote network? Is the IP address you are connecting to really part of the remote network?įor example, if your remote network is 192.168.13.0/24, you should be able to connect to IPs starting with 192.168.13.x, but connections to IPs starting with 192.168.14.x will not work as they are outside the address range of traffic tunneled through the VPN.ģ. Note that using Bonjour or NETBIOS hostnames is generally not possible over VPN.Ģ. Please make sure DNS is enabled for the VPN connection and correctly configured. If that works, the problem has to do with DNS resolution. If you are using a host name, please try once using its IP address instead.

Are you trying to connect to the destination device using a host name? The destination device can be anything from a normal computer, to a server, to a network printer.ġ. In this FAQ we will be using destination device as a generic term for the device you are trying to connect to. This FAQ will help you to find out what is causing the problem in your specific situation. There are a number of possible causes for such a behavior.

Ipsecuritas 4.7 sierra