The VPN seems connected but I can't connect to my server or transfer data. What is wrong?
There are a number of possible causes for such a behavior. This FAQ will help you to find out what is causing the problem in your specific situation.
In this FAQ we will be using the term remote host as a generic term for the computer/server you would like to connect to. The remote host can be a file server, an email server, a database server, a terminal server, a computer whose screen you want to share (remote desktop), or anything else you want to connect to through VPN.
1. Are you trying to connect to the remote host using its IP address or its host name?
If you are using a host name, please try using the IP address of the remote host instead. If it works with that, you may need to configure suitable remote DNS setup. Note that using Bonjour or NETBIOS hostnames is not possible over VPN.
2. Is the IP address you are connecting to part of the remote network?
For example, if your remote network is 192.168.42.0/24, you should be able to connect to IPs starting with 192.168.42.x, but connections to IPs starting with 192.168.43.x will not go through the VPN.
3. Is the local address in VPN Tracker part of the remote network?
Using a local address in VPN Tracker (Basic > Local Address) that is part of the remote network is not possible with most VPN gateways. Please use a local address that is not part of the remote network. For example, if your remote network is 192.168.42.0/24, use 10.99.99.1 as the local address.
If there is just one VPN user, you will in most cases be able to leave the local address empty. If there's more than one VPN user, each should use a different local address.
If you are using an automatic configuration method (e.g. 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. Refer to the configuration guide for your VPN gateway for more information.
4. Can you ping any computer in the remote network through the VPN?
You can find a ping tool directly in VPN Tracker under Tools > Ping Host.
If you can ping, but not connect specific services, please check firewall and authentication settings on the remote host providing these services.
5. If you can't ping, try re-running the VPN Availability Test
The VPN Availability Test can be found in the menu: Tools > VPN Availability Test. Then try connecting the VPN again.
6. Is your VPN gateway the default gateway (router) of its network?
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.
7. Are you trying to connect to a Windows (SMB) share from a Mac running Mac OS X 10.4 Tiger?
You may be running into a known bug with Mac OS X 10.4 Tiger. The bug is fixed in Mac OS X 10.5 and higher. If you have the possibility, test with Mac OS X 10.5 or higher, or read this FAQ.