Jul 27
So tonight I was trying to work remotely and was getting dropped recurrently.
I went out to www.whatismyip.com and checked the IP returned against the IP address on my local connection. They were different.
Next I looked at the profile settings for Cisco VPN client and at the “Transport” tab enabled “Transparent Tunneling” and “IPSec over UDP (NAT/PAT)”. It saved the day…
Feb 27
If you have a profile that used to work and is no longer working for you this might help… or not… The message “Remote peer is no longer responding” is used on more than one failure scenario.
Increase the log level on /etc/opt/cisco-vpnclient/vpnclient.ini:
[main]
BinDirPath=/usr/local/bin
EnableLog=1
[LOG.IKE]
LogLevel=15
[LOG.CM]
LogLevel=3
[LOG.CVPND]
LogLevel=3
[LOG.XAUTH]
LogLevel=3
[LOG.CERT]
LogLevel=3
[LOG.IPSEC]
LogLevel=15
[LOG.CLI]
LogLevel=3
[LOG.FIREWALL]
LogLevel=15
[LOG.PPP]
LogLevel=1
[LOG.DIALER]
LogLevel=1
[LOG.GUI]
LogLevel=1
Now Run:
# ipseclog ipseclog.txt &
Cisco Systems VPN Client Version 4.8.02 (0030)
Copyright (C) 1998-2007 Cisco Systems, Inc. All Rights Reserved.
Client Type(s): Linux
Running on: Linux i686 #1 SMP Wed Feb 11 23:58:12 EST 2009 i686
Config file directory: /etc/opt/cisco-vpnclient
[1] 5143
#
And now try connecting again.
After it fails check /var/log/ipseclog.txt and try finding DEL_REASON_PEER_NOT_RESPONDING.
Then if the profile you’re using has EnableNAT=1 try changing to EnableNAT=0 and try connecting again.
This solved the problem for me.
If you still have the problem try also restarting your Internet connection or the network service (Fedora):
# /etc/init.d/network restart
RSS