Cisco Cisco AnyConnect Secure Mobility Client v2.x Troubleshooting Guide

The VPN connection has been terminated due to the secure gateway being shutdown. 

A new connection is necessary, which requires re-authentication.

The administrator issued an orderly shutdown of the secure gateway. In preparation, the 

secure gateway terminated the VPN connection.

Try a new VPN connection to see if another secure gateway accepts it.

The VPN connection is not allowed via a local proxy. This can be changed through 

AnyConnect profile settings.

In accordance with the AnyConnect configuration, AnyConnect prevented the use of a 

local proxy to establish a VPN connection.

Remove the local proxy and try a new VPN connection.

None. Check Allow Local Proxy Connections on the 

AnyConnect client profile if you want to permit the use of a local proxy.

The VPN connection to the secure gateway was disrupted and could not be 

automatically re-established. A new connection is necessary, which requires 

re-authentication.

Automatic VPN reconnection attempts failed. The VPN connection required an 

automatic reconnection because of a connection failure or disruption. Possible causes include a local 
network failure, internet device failure, or secure gateway failure.

Verify network connectivity, then try a new VPN connection.

The VPN connection was re-established but the secure gateway assigned a new 

configuration that could not be successfully applied. A new connection is 

necessary, which requires re-authentication.

Automatic VPN reconnection attempts failed. A modified VPN connection 

configuration from the secure gateway requires another automatic reconnection.

Verify network connectivity, then try a new VPN connection.

The VPN connection was started by a remote desktop user whose remote console has 

been disconnected. It is presumed the VPN routing configuration is responsible for 

the remote console disconnect. The VPN connection has been disconnected to allow 

the remote console to connect again. A remote desktop user must wait 90 seconds 

after VPN establishment before disconnecting the remote console to avoid this 

condition.

AnyConnect detected a remote console disconnect within 90 seconds of the 

establishment of a VPN session. AnyConnect terminated the session because it detected an 
interruption of the remote console session, indicating the necessity of restoring the local IP 
forwarding table to permit the re-establishment of the remote console session.

Remote console users should wait more than 90 seconds following VPN 

connection establishment before disconnecting the remote console session to avoid this condition.