symantec endpoint protection 14 enable aggressive mode

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.

Symantec endpoint protection 14 enable aggressive mode