Software
Linux
UBVPN
VPN Troubleshooting
Kernel Update
Has the VPN client been working previously? If you have recently updated your Linux kernel (either by the up2date utility or manually), you will need to re-install the VPN client. Please simply uninstall, then install again.
Location
Where are you trying to use the VPN client from? There are only two locations that the VPN clientwill connect successfully from. Those are:
- An off-campus internet or UB PPP connection.
- On-campus using UBWireless.
Internet Access
Can you access the Internet from your current location? You need a working network connection before you can connect using the VPN client.
Firewall settings
Can you login using the VPN client, but not view any UB related pages? Your firewall might be blocking the ports the VPN client uses to transmit its data. Your firewall must allow the following types of traffic to pass through: UDP port 500 (ISAKMP), IP protocol 50 (ESP), and UDP port 4500 (for use with NAT-T, for users utilizing NAT).
VPN client version
You may not be using the correct version of the VPN client. UBLinux4 as well as Red Hat Enterprise Linux 4 use the 2.6 kernel,which require a newer version of the VPN client.
Check the log files
If you are using UBLinux4 and start the VPN client by using the UB menu item, then there should be a log file named vpnclient in the /var/log/ directory. If this file does not exist, or if you did not install the VPN client using an RPM, you can enable logging by following these instructions while logged in as superuser:
- edit the file /etc/CiscoSystemsVPNClient/vpnclient.ini and change EnableLog=0 to EnableLog=1 . The log levels for each component range from 0 (disabled) to 3 (verbose).
-
Run the command
/usr/local/bin/ipseclog /somewhere/logfile.txt
somewhere is a directory and logfile is the name of the logfile. Do this before starting the VPN Client to enable logging. If the file already exists, the file will be overwritten by the new data.
Try running the VPN client now that logging is now enabled. The log files may shed some light on what is wrong.
Additional Information