Какие галочки нужно ставить в ccleaner. Настройка программы CCleaner. Как выполнить стирание дисков

Cisco VPN Client - это официальное программное обеспечение, выпущенное крупнейшим в мире производителем промышленного сетевого оборудования - компанией Cisco. Основным назначением ПО является создание надежно защищенного IPSec-туннеля для передачи данных между клиентом и удаленным сервером. Как несложно догадаться по аббревиатуре VPN в названии программы, данное решение активно использует концепцию виртуальной сети для работы с маршрутизаторами, концентраторами и прочими девайсами в обход установленного фаервола. Стоит отметить, что развертывание этой самой виртуальной сети происходит в автоматическом режиме и требует минимального вмешательства со стороны пользователя.

Назначение

В первую очередь данный клиент необходим для осуществления удаленного клиентского обслуживания. Программа дает возможность выполнять сервисные операции с устройствами, поддерживающими Unified Client Framework. При необходимости клиент можно развернуть сразу для всего имеющегося оборудования. Для управления подключенными устройствами в Cisco VPN Client предусмотрен удобный менеджер, который также выполняет двухфакторную авторизацию и дает возможность управлять пользовательскими сертификатами.

При работе с клиентом допускается возможность использования USB-ключей и смарт-карт. Последние версии Cisco VPN Client (5.0.07.0410, 5.0.07.0440) научились загружать конфигурации VPN из центрального шлюза, что значительно повысило безопасность, простоту в эксплуатации масштабируемость системы.

Совместимость

Официальная поддержка Cisco VPN Client заявлена для операционных систем в промежутки между Windows XP и 7. Поэтому при использовании программного обеспечения на Windows 10 могут возникать проблемы совместимости. Также отметим, что на Windows 7 инсталлятор требуется запускать исключительно от имени администратора. На русский язык клиент, к сожалению, не переведен.

Ключевые особенности

служит для установления защищенного IPSec-туннеля;
является официальным программным решением от компании Cisco;
поддерживает двухфакторную авторизацию;
работает с самыми разными моделями сетевого оборудования;
обеспечивает возможность удаленного обслуживания.

Introduction

These release notes are for the Cisco VPN Client, Release 5.0.07.0290. The names of the files on the software download site are:

Vpnclient-win-msi-5.0.07.0290-k9.exe for Windows on x86 (32-bit).

Vpnclient-winx64-msi-5.0.07.0290-k9.exe for Windows on x64 (64-bit).

The VPN Client creates a secure connection over the Internet between a remote PC and an enterprise or service provider Cisco VPN device. This connection lets you access a private network as if you were an on-site user.

This document identifies the new features, system requirements, limitations and restrictions, known issues, resolved caveats, and related documentation. Please read it carefully prior to installation. The section, " ," describes interoperability considerations and other issues you should be aware of when installing and using the VPN Client.

New Features

VPN Client 5.0.07 features the following:

Support for Windows 7 on x64 (64-bit). This release, however, does not support WWAN devices (also called wireless data cards) on Windows 7 x86 (32-bit) and x64. For support of WWAN devices on Windows 7, please use the Cisco AnyConnect Secure Mobility client.

Support for Windows Vista on x64.

Packet LZS compression for x64 VPN Client.

Note that this version does not provide online help.

System Requirements

Cisco VPN Client 5.0.07 supports the following Microsoft OSs:

Windows 7 on x64 (64-bit)

Windows 7 on x86 (32-bit) only

Windows Vista on both x86 (32-bit) and x64

Windows XP on x86

VPN Client does not support the Tablet PC 2004/2005; and Windows 2000, NT, 98, and ME.

VPN Client supports smart card authentication on Windows 7, Vista, and XP. However, VPN Client does not support the ST Microelectronics smart card Model ST23YL80, and smart cards from the same family.

VPN Client supports up to one Ethernet adapter and one PPP adapter. It does not support the establishment of a VPN connection over a tethered link.

VPN Client 5.0.x is incompatible with the combination of Cisco Unified Video Advantage 2.1.2 and McAfee HIPS Patch 4 Build 688. To avoid system failures, uninstall either of these two applications, upgrade McAfee to the latest version, or use VPN Client 4.6.x.

To install the VPN Client, you need

Pentium® -class processor or greater

Microsoft TCP/IP installed. (Confirm via Start > Settings > Control Panel > Network > Protocols or Configuration.)

50 MB hard disk space.

128 MB RAM
(256 MB recommended)

Administrator privileges

The VPN Client supports the following Cisco VPN devices:

Cisco Series 5500 Adaptive Security Appliance, Version 7.0 or later.

Cisco VPN 3000 Series Concentrator, Version 3.0 or later.

Cisco PIX Firewall, Version 6.2.2(122) or Version 6.3(1).

Cisco IOS Routers, Version 12.2(8)T or later.

To download the version of AnyConnect, you must be a registered user of сайт.

To obtain the AnyConnect software, follow these steps:

Step 1 Follow this link to the Cisco AnyConnect Secure Mobility Client Introduction page:

http://www..html

Step 2 Click Download Software .

Step 3 Click Cisco VPN Client v5.x in the third column of the table under "Make a selection to continue."

Step 4 Click Yes in response to the prompt, "Do you want to view only the webpage content that was delivered securely?"

Step 5 Enter your сайт credentials.

Step 6 Ensure the Latest Releases folder is open.

Step 7 Click Download Now next to the associated name of the .exe file.

Step 8 Click Proceed with Download.

The webpage displays a link to the Cisco End User License agreement.

Step 9 Read and verify the download rules below the link, then click Agree .

Step 10 Click Download next to "Cisco VPN Client v5.x."

Installation Notes

Refer to "Cisco VPN Client User Guide for Windows, Chapter 2, for complete installation instructions for Windows users.

Note Due to issues surrounding network installation, Active Directory Group Policy software deployment is no longer supported. For more information and a workaround, refer to open caveat CSCse00525.

Installation Notes - Windows Platforms

Please note the following installation considerations for Windows users.

Installation Error 1720

If a 1720 error occurs during the installation of the VPN Client, please use the Microsoft WMI Diagnosis Utility to check the WMI status.

Please contact Microsoft if the utility reports errors.

vpnapi.dll File Installs in Wrong Directory (Windows 7 x64 Only)

If you install VPN Client onto Windows 7 x64, move the vpnapi.dll file from the %SystemRoot%\Program Files(x86)\Cisco Systems\VPN Client\ directory to the %SystemRoot%\SysWOW64 directory. Otherwise, applications that use the VPN Client API cannot do so.

Default Location for VPN Client Registry Values on Windows 7 x64

The default location of all VPN Client registry values for Windows 7 on x64 (64-bit) is:

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Cisco Systems\VPN Client

Avoiding Vista Problems with the TCP/IP Registry Compatibility Service and the VPN Virtual Adaptor

To avoid problems with the TCP/IP Registry Compatibility service and the VPN Virtual Adaptor, we strongly recommend that Windows Vista users install Vista SP2 or later.

For more information about a previous hotfix for this problem, go to this URL:

http://support.microsoft.com/kb/952876

Upgrading from Windows XP Requires a Clean Installation

After upgrading Windows XP to Windows 7 or Vista, one experiences various problems with the VPN Client, ranging from client not logging, client won"t connect, virtual adapter not installing, and so on. Upgrading from a clean install of Windows XP to Vista has been tested and the VPN Client does work in this situation.

However, upgrading a Windows XP installation with legacy applications ranging from Firewalls, Antivirus, device drivers, and so on to Windows 7 or Vista is not supported, because the problems stem from the legacy applications no longer supported by the OS.

Installing the VPN Client Software Using the MSI Installer

You can use the MSI installer on Windows 7, Vista, and XP. Installing with MSI requires administrator privileges.

Before installing the Windows MSI installation package, you must manually uninstall the previous VPN Client if it is older than Release 4.7. The MSI installer does not uninstall the older versions; it attempts to install before aborting gracefully. Once a version 4.7 MSI package has been installed on Windows XP, future client versions can detect the release present and automatically begin the uninstallation process.

Upgrading the VPN Client Software on Windows 7 and Vista

For Windows 7 and Vista, please use add/remove programs to uninstall the VPN Client before upgrading to a new Client release.

Using the VPN Client

To use the VPN Client, you need:

Direct network connection (cable or DSL modem and network adapter/interface card), or

Internal or external modem

To connect using a digital certificate for authentication, you need a digital certificate signed by one of the following Certificate Authorities (CAs) installed on your PC:

Entrust Technologies (www.entrust.com)

Netscape (www.netscape.com)

Verisign, Inc. (www.verisign.com)

Microsoft Certificate Services — Windows 2003

Microsoft Certificate Services — Windows 2000

Digital certificate stored on a smart card (supported only on Windows Vista and XP at this time). The VPN Client supports smart cards via the MS CAPI Interface.

The VPN Client accepts a blank password for certificate retrieval, but should not.

About Version Numbers

VPN Client software uses an all-numeric version numbering system to facilitate the automatic update function. Release numbers are represented in the format:

...

The major and minor release numbers represent the feature level of the product. Major and minor releases implement new product capabilities. The sustaining and build release numbers represent significant or minor patch levels, respectively. For example, 5.0.01.06000 represents feature release 5.0.01, build 600.

All sustaining and build releases are cumulative; however, we do not release all build numbers. The build number for this release is 5.0.07.0290.

Advisories for Windows 7 and Vista Users

Windows 7 and Vista users should be aware of the following characteristics of the Cisco VPN Client.

Secondary IP Address Used for VPN Session with Windows 7

On Windows 7, the Cisco VPN Client uses the primary IP address of an interface during the VPN session setup. However, if the same interface has a secondary IP address, the VPN Client uses the secondary IP address to transmit all traffic once the session is established.

Using the VPN Client to connect a PC running Windows 7 or Vista system might take longer than one running Windows XP. The actual time it takes to connect might vary from customer to customer.

IPv6 Resources Accessible on LAN

Windows 7 and Vista users who establish a VPN Client connection can use IPv6 to access resources on the LAN, regardless of whether split tunneling is configured. By default, Windows 7 enables IPv6. The only workaround is to disable IPv6 on the endpoint. This issue applies to all VPN Client releases that support Windows 7 and Vista.

Unsupported Features

The Cisco VPN Client for Windows 7 and Vista does not support the following features:

Upgrade from Windows XP (clean OS installation required).

Start Before Logon

Integrated Firewall

Usage Notes

This section lists issues to consider before installing VPN Client Release 5.0.07.

In addition, you should be aware of the known caveats in this release. Refer to of this document for the list of known problems.

Note Support for this release is provided through the Cisco TAC for customers with SMARTnet support contracts.

VPN Client May Not Work Properly After Laptop Wakes up from Suspend Mode

The Cisco VPN Client may not work properly on a laptop after it wakes up from suspend mode. If a VPN 4.8 (or later) Client is connected to a central site-device, and the client device (typically a laptop) goes into Suspend Mode, then the VPN Client disconnects. Upon waking up from Suspend Mode, the VPN Client is disconnected. A pop-up message appears, allowing you to reconnect the VPN connection. However, selecting reconnect may not re-establish the VPN tunnel.

This situation occurred with the VPN 4.8 Client installed on a Windows XP Laptop. The client disconnects after going into any hibernate or standby situations.

This behavior was tracked with the defect ID CSCsf96588 and resolved; however, Cisco cannot guarantee that this solution will work on all hardware platforms and operating systems. You may still encounter the behavior described in CSCsf96588 when running Cisco VPN client version 4.8 and later. If you do see the behavior described in the defect, use the following workaround:

Workaround

Disconnect the Cisco VPN session before going into Hibernate or Standby Mode. When you awaken your computer, re-establish the Cisco VPN session. Use one of these methods to disconnect the Cisco VPN Client:

Open the Cisco VPN Client on the desktop, select the connection entry and click Disconnect .

Right-click the Cisco VPN client icon in the system tray and click Disconnect .

Open Windows Task Manager, click the Processes tab, and end the vpngui.exe process.

Cannot Connect to ASAs Using the Same FQDN with TCP

VPN Client cannot complete a VPN connection if it is using IPsec over TCP and two or more ASAs are using the same FQDN.

As a workaround, use IPsec over UDP or plain IPsec, or upgrade to Cisco AnyConnect Secure Mobility client, release 2.5(3), 3.0(2), or later.

VPN Connection Retained When Switching Users

If one user uses VPN Client to establish a VPN connection and another user uses the Switch User feature to log into Windows, the second user also has access to that connection. As a workaround, upgrade to the Cisco AnyConnect Secure Mobility client.

Split DNS with Wildcards

A split-dns value containing wildcards can cause a system failure when a Windows user accesses certain URLs. For example, the split-dns value a,b,c,d,e,f,g,h,i,j,k,l,m,no,p,q,r,s,t,u,v,w,x,y,z can cause a system failure. To avoid these failures, move the VPN adapter to the top of the binding order list of network adapters. Note that Split DNS requires entries only for internal domains.

Potential Compatibility Issues

You might encounter the following compatibility issues when using the VPN Client with specific applications. Whenever possible, this list describes the circumstances under which an issue might occur and workarounds for potential problems.

Windows Interoperability Issues

The following known issues might occur with the indicated Microsoft Windows operating systems and applications software.

Microsoft Internet Connection Sharing Incompatible

The VPN Client is not compatible with Microsoft ICS (Internet Connection Sharing (ICS) on the same PC.

Wireless Hosted Network Feature Incompatible with VPN Client

The VPN client can become unstable when using the Wireless Hosted Network feature in Windows 7. Therefore, when using the VPN Client, we do not recommend enabling this feature or running front-end applications that enable it such as Connectify or Virtual Router.

VPN Client Cannot Launch Microsoft Connection Manager

The VPN Client does not detect a dialup connection made with Microsoft Connection Manager because of incompatibilities between the requirements of the two applications.

Microsoft MSN Installation

Microsoft"s MSN installation fails if you have already installed the VPN Client. Uninstall the VPN Client before you install MSN. After MSN has completed installation, you can install the VPN Client.

WINS Information Might Not Be Removed from Windows Servers If Not Disconnected Before Shutdown

If the VPN Concentrator is configured to send WINS server addresses to the VPN Client and the PC is shut down or restarted without first disconnecting the VPN Client, the WINS servers are not removed from the network properties. This might cause local PC registration and name resolution problems while not connected with VPN.

To work around this problem, do one of the following:

Be sure to disconnect the VPN Client before shutting down. If you are having problems, check your network properties and remove the WINS entries if they are not correct for your network.

Alternatively, enable "Disconnect VPN connection when logging off". Go to Options > Windows Logon Properties, check Disconnect VPN connection when logging off.

DNS

For DNS resolution, if the DOMAIN NAME is not configured on the network interface, you must enter the fully qualified domain name of the host that needs to be resolved.

Network Interfaces

The VPN Client does not support Point-to-Point Protocol over ATM (PPPoA).

The VPN Client cannot establish tunnels over Token Ring. However, it does not conflict with an installed Token Ring interface.

The VPN Client on Windows 7 does not support WWAN devices (also called wireless data cards).

Microsoft Outlook Error Occurs on Connect or Disconnect

The following Microsoft Outlook error might occur when the VPN Client connects or disconnects:

"Either there is no default mail client, or the current mail client cannot fulfill the messaging request. Run Microsoft Outlook and set it as the default mail client."

This message does not affect operation of the VPN Client. The issue occurs when Microsoft Outlook is installed but not configured for email, although it is the default mail client. It is caused by a Registry Key that is set when the user installs Outlook.

To eliminate this message, do one of the following:

Right-click the Outlook icon, go to Properties, and configure it to use Microsoft Exchange or Internet Mail as the default mail client.

Use Internet Explorer to configure the system to have no default mail client.

Configure Outlook as the default mail client.

Adjusting the Maximum Transmission Unit (MTU) Value - Windows Only

VPN Encapsulation adds to the overall message length. To avoid refragmentation of packets, the VPN Client must reduce the MTU settings. The default MTU adjusted value is 1300 for all adapters. If the default adjustments are not sufficient, you may experience problems sending and receiving data. To avoid fragmented packets, you can change the MTU size, usually to a lower value than the default. To change the MTU size, use the VPN Client SetMTU utility. If you are using PPPoE, you may also have to set the MTU in other locations. Refer to the following table for the specific procedures for each type of connection.

The MTU is the largest number of bytes a frame can carry, not counting the frame"s header and trailer. A frame is a single unit of transportation on the Data Link Layer. It consists of header data, plus data that was passed down from the Network Layer, plus (sometimes) trailer data. An Ethernet frame has an MTU of 1500 bytes, but the actual size of the frame can be up to 1526 bytes (22-byte header, 4-byte CRC trailer).

Recognizing a Potential MTU Problem

If you can connect with the Cisco VPN Client but cannot send or receive data, this is likely an MTU problem. Common failure indications include the following:

You can receive data, such as mail, but not send it.

You can send small messages (about 10 lines), but larger ones time out.

You cannot send attachments in email.

Setting the MTU Value

If you do not experience a problem, do not change the MTU value. Usually, an MTU value of 1300 works. If it does not, the end user must decrease the value until the Cisco VPN Client passes data. Decrement the MaxFrameSize value by 50 or 100 until it works.

The following table shows how to set the MTU value for each type of connection.


Physical Adapters
	Use the SetMTU utility supplied with the Cisco VPN Client.
PPPoE - All Vendors

Cert DN Matching Cannot Match on Email Field EA

You cannot match the Cert DN field (EA) when using the Peer Cert DN Verification feature on the VPN 3000 Concentrator because the VPN 3000 Concentrator does not assign a value to that field.

VPN Dialer Application Can Load During OS Shutdown or Restart

When using the VPN Client Start Before Logon feature in "fallback" mode, the VPN dialer application loads during a shutdown or restart of the operating system. This does not cause any problems and can be ignored.

America Online (AOL) Interoperability Issues

The following interoperability issues apply to AOL dialup connections only.

AOL Versions 5.0 and 6.0

The VPN Client supports AOL Version 5.0. AOL Version 6.0 is also supported, with one limitation: when connected, browsing in the network neighborhood is not available.

AOL Version 7.0

AOL Version 7.0 uses a proprietary heartbeat polling of connected clients. This requires the use of split tunneling to support the polling mechanism. Without split tunneling, AOL disconnects after a period of time between 5 and 30 minutes.

AOL 7 Disconnects after VPN Authentication

When making a dialup connection with AOL 7.0 Revision 4114.537, then attempting to connect with the VPN Client, AOL might disconnect while the user is being authenticated. This is an AOL issue, not a VPN Client problem (CSCdy45351).

VPN Client Fails to Connect over Some AOL Dialup Connections

The Cisco VPN Client connecting over an AOL dialup connection fails to complete the connection, particularly when using AOL 7.0 and 8.0.

The AOL dialup process uses a fallback method which, if your initial attempt to connect fails, resorts to a different connection type for the second attempt. This second attempt can sometimes cause AOL to communicate over two PPP adapters (visible in ipconfig /all output). When this happens, the VPN Client cannot connect. This is a known issue, and AOL is investigating the problem.

To work around this issue, try to reconnect the dialup connection and try to avoid getting two PPP adapters.

ZoneAlarm Plus Versions 3.1.274 and Earlier Are Incompatible with VPN Client

The following known incompatibility exists between the Cisco VPN Client and Zone Labs ZoneAlarm Plus version 3.1.274 and earlier. If you are using such a version of ZoneAlarm Plus, please visit http://www.zonelabs.com or contact your Zone Labs representative for an update.

On a PC with ZoneAlarm Plus version 3.1.274 (or earlier) and the VPN Client, errors similar to the following occur when the PC boots:

ZAPLUS.exe has generated errors and will be closed by Windows. You will need to restart the program.

An error log is being generated.

The Application Log records a message similar to the following:

The application, ZAPLUS.EXE, generated an application error. The error occurred on 7/23/2002... The exception was c0000005 at address 00401881 ().

The result of such errors is that the ZoneAlarm GUI does not run, and therefore a user cannot change any settings in ZoneAlarm Plus or allow new programs to access the Internet. (CSCdy16607).

CheckPoint ZoneAlarm (Integrity Agent) Is Incompatible with VPN Client

The VPN Client is not compatible with the software firewall provided with ZoneAlarm (Integrity Agent) v8.0.298. (CSCtc46109)

Auto-update Package No Longer Supported

VPN Client does not support the auto-update package for versions higher than 5.0.3.0560.

Close Client before Hibernation

Windows 7 and Vista leave the client hanging while it attempts to disconnect upon awakening after hibernation. To avoid this issue, close the client interface before hibernation and reopen it upon awakening.

Upgrading Zone-Alarm Pro to Version 3.7.098 Causes Error When VPN Client Is Already Installed on the PC

Upgrading ZoneAlarm Pro version 3.5.xxx to ZoneAlarm Pro version 3.7.098 when the VPN Client is installed on the PC might cause the following error to appear:

"The procedure entry point DbgProcessReset could not be located in the dynamic link library VSUTIL.dll."

Click OK. The installation continues. See ZoneLabs bug number 10182.

DHCP Route Renewal

If the public network matches the private network (for example, a public IP address of 192.168.1.5, with a subnet mask of 255.255.0.0, and an identical private IP address) and the public network route metric is 1, traffic might not be tunneled to the private network. The same problem can occur if you are using a virtual adapter and the public metric is smaller than the virtual adapter metric.

In Windows 7 and Vista, you can increase the metric of the public network as follows:

Step 1 Select Start > Control Panel > (Network and Internet) > View Network Status and Tasks.

Step 2 Right-click the icon representing the public interface and select Properties.

Step 3 Select Internet Protocol Version 4 and click Properties.

Step 4 Click Advanced in the General tab, and set the interface metric to 2 or greater.

In Windows XP, you can increase the metric of the public network as follows:

Step 1 Select Start > Settings > Control Panel > Network and Dial-up Connections.

Step 2 Select the public interface and click properties for the public interface.

Step 3 Select Internet Protocol (TCP/IP) and get the properties for the Internet Protocol (TCP/IP).

Step 4 Click Advanced, and set the interface metric to 2 or greater.

Windows XP Only—Data Meant for Private Network Stays Local if VPN Client Local Network Is on Same IP Subnet as Remote Private Network

This problem occurs only with the VPN Client, Release 4.6 and only with Virtual Adapter on Windows XP when the VPN Client local network is on the same IP subnet as the remote private network. When a VPN connection is up, data meant for the private network stays local. For example: 192.168.1.0/255.255.255.0

Beginning with VPN Client, Release 4.6, the Virtual Adapter attempts to modify local route metrics to allow data to pass over the VPN tunnel. In some cases, it is impossible for the VPN Client to make this modification.

To work around this problem, make the change manually, using the following procedure:

Step 1 Run > Control Panel > Network and Dialup Connections.

Step 2 Right-click on the adapter in question and select Properties.

Step 3 From the Adapter Properties dialog, select TCP/IP from the list and click Properties.

Step 4 Click Advanced and increase the number in the "Interface metric" box by 1 (it is usually 1, so making it 2 works).

Step 5 Click OK to exit out of all dialogs.

Step 6 The VPN connection should now work.

DNS Server on Private Network with Split DNS Causes Problems

When an ISP DNS server is included in the Split Tunneling Network List and Split DNS Names are configured, all DNS queries to domains other than those in the Split DNS Names list are not resolved.

By definition, split DNS is used so that only certain domains get resolved by corporate DNS servers, while rest go to public (ISP-assigned) DNS servers. To enforce this feature, the VPN Client directs DNS queries that are about hosts on the Split DNS Names list to corporate DNS servers, and discards all DNS queries that are not part of the Split DNS Names list.

The problem is when the ISP-assigned DNS servers are in the range of the Split Tunneling Network List. In that case, all DNS queries for non-split-DNS domains are discarded by the VPN Client.

To avoid this problem, remove the ISP-assigned DNS server from the range of the Split Tunneling Network List, or do not configure split DNS (CSCee66180).

No Limit to Size of Log File

When logging is enabled on the VPN Client, all of the log files are placed in the Program Files\Cisco Systems\VPN Client\logs directory and are date and time stamped. There is no limit to the size of the log when logging is enabled. The file will continue to grow in size until logging is disabled or the VPN Client program is closed. The log is still available for viewing until the VPN Client program is re-launched, at which time the display on the log tab and log window are cleared. The log file remains on the system and a new log file is created when the VPN Client, with logging enabled, is launched.

Start Before Logon and Microsoft Certificate with Private Key Protect Fails

Trying to connect the VPN client using Start Before Logon (SBL) and Microsoft Machine-based certificates fails. This failure is a Microsoft issue, not a VPN Client problem.

If your certificate has private key protection enabled, every time you use the certificate keys you are either prompted for a password to access the key, or notified with a dialog and asked to click OK.

The prompt displayed when using a certificate with private key protection appears on the Windows Desktop. You do not see this message while at the Logon desktop, therefore the VPN Client cannot gain the access to the certificate needed to connect.

Use one of the following workarounds:

Get a certificate without private key protection. Make sure it is machine-based; otherwise it will not be accessible before logging on).

Instead of using Start Before Logon, log on to the PC using cached credentials, make the VPN connection, and— using the "stay connected at logoff" feature—logoff/logon with the VPN established to complete the domain logon.

Linksys Wireless AP Cable/DSL Router Version 1.44 or Higher Firmware Requirement

To use the VPN Client behind a Linksys Wireless AP Cable/DSL router model BEFW11S4, the Linksys router must be running version 1.44 or higher firmware. The VPN Client cannot connect when located behind a Linksys Wireless AP Cable/DSL router model BEFW11S4 running version 1.42.7 firmware. The VPN Client may see the prompt for username/password, then it disappears.

VPN Client Can Require Smart Card When Using Certificates

You can configure the VPN Client to require the presence of a smart card when certificates are used. If this feature is configured, the VPN Client displays an error message if a smart card is not present. The certificates need not be present on the smart card itself. To configure this feature, add the following line to the user"s client profile, specifying the appropriate vendor for your smart card:

SmartCardName=

If you are using pre-shared keys instead of certificates, this requirement is not enforced, even if configured.

To disable the smart card verification function, completely delete the entry: SmartCardName= from the user"s client profile (CSCec82220).

Allowing ICMP Traffic to Pass Through the Firewall

The following configurations allow inbound ICMP packets (pings) when the default firewall rule for the Centralized Protection Policy (CPP) is pushed to the VPN Client.

On the VPN Client:

Stateful Firewall (Always On) is enabled.

The setting "StatefulFirewallAllowICMP=1" is added to the section of the vpnclient.ini file.

A connection is made to the VPN Concentrator that pushes the default CPP firewall rule to the VPN Client.

Use the parameter, "StatefulFirewallAllowICMP=1"only if you want to allow ICMP traffic to pass through the firewall.

Use Zone Labs Integrity Server 2.1.052.0 or Higher with VPN Client 4.0

Versions of the Zone Labs Integrity Server earlier than 2.1.052.0 exhibit the following problem. If two or more VPN Clients running on Windows XP are connected to a VPN 3000 Series Concentrator and receive firewall policy from a ZoneLabs Integrity Server, the Integrity Server registers only one connection.

On the Integrity Flex (client agent), under "Policies", the "Integrity Server" column flashes "Connected" then "Disconnected" over and over. The VPN Client log also includes the following event: "The firewall, configured for Client/Server, returned a status of lost connection to server." Zone Labs Integrity Server version 2.1.052.0 fixes this issue.

Restart VPN Client Service if You Install VPN Client before Zone Alarm

The firewall enhancement, "Prevent VPN Traffic Blocking", automatically adds the Loopback address (127.0.0.1) and the address of the VPN 3000 Concentrator to the ZoneAlarm or ZoneAlarmPro trusted zone.

Check Point Integrity Firewall Incompatibility

Cisco VPN Client may not start if the Check Point Integrity personal firewall is running. Either shut down the Integrity client (iclient.exe) or disable its firewall.

Caution Do not disable the firewall if you are using the ZoneAlarm firewall.

Cisco VPN Client – это клиент для доступа к виртуальной частной сети (VPN). Программа разработана крупнейшим производителем сетевого оборудования – компанией Cisco.

Итак, чтобы пользоваться VPN-соединением, вам необходимо создать новое подключение. Для этого запускаете клиент и нажимаете кнопку New. Здесь вам необходимо ввести название подключения, ip-адрес, групповые логин и пароль. Далее сохраняете профиль, и он появится у вас в списках доступных соединений. Затем выбираете это соединение и нажимаете Connect. Cisco VPN Client предложит вам ввести личные логин и пароль. Если они введены правильно, программа начнет подключение к сети. После успешного соединения в системном трее появится значок замка.

Если у вас есть отдельный файл с уже настроенной конфигурацией (формат PCF), то вы можете импортировать его в программу, чтобы не вводить все параметры вручную.

Чтобы просмотреть статистику, щелкните правой кнопкой по значку и кликнете на Statistic. Здесь вы увидите объем полученного и отправленного трафика, время подключения, количество отправленных и полученных пакетов и т. д.

Особенности программы

Подключение к виртуальной частной сети (VPN).
Возможность импорта файла с настройками.
Ведение подробной статистики (время подключения, объём трафика и др.).
Поддержка Windows XP и выше.

Таким образом, с помощью Cisco VPN Client вы легко подключитесь к виртуальной частной сети. Программу можно скачать абсолютно бесплатно.

Cisco VPN – весьма популярный софт, который предназначен для удаленного доступа к элементам частной сети, поэтому используется он в основном в корпоративных целях. Данная программа работает по принципу клиент-сервер. В сегодняшней статье мы рассмотрим подробно процесс установки и настройки клиента Cisco VPN на устройствах под управлением .

Для того чтобы установить ВПН клиент Cisco на Windows 10, потребуется выполнить дополнительные действия. Это связано с тем, что программа перестала официально поддерживаться еще с 30 июля 2016 года. Несмотря на данный факт, сторонние разработчики решили проблему запуска на Windows 10, поэтому программное обеспечение Cisco VPN актуально и по сей день.

Процесс инсталляции

Если попытаться запустить программу стандартным способом без дополнительных действий, то появится вот такое уведомление:

Для корректной же установки приложения вам необходимо сделать следующее:

Перейти на компании «Citrix» , которая и разработала специальное ПО «Deterministic Network Enhancer» (DNE).
Далее необходимо найти строки со ссылками на загрузку. Для этого опуститесь почти в самый низ страницы. Нажмите на том участке предложения, которое соответствует разрядности вашей операционной системы (х32-86 или х64).

Моментально начнется загрузка исполняемого файла. По окончании процесса следует запустить его двойным нажатием ЛКМ .

В главном окне «Мастера установки» нужно ознакомиться с лицензионным соглашением. Для этого поставьте галочку напротив строки, которая отмечена на скриншоте ниже, а потом нажмите кнопку «Install» .

После этого начнется установка сетевых компонентов. Весь процесс будет выполняться автоматически. Вам нужно будет лишь немного подождать. Спустя некоторое время увидите окно с уведомлением об успешной установке. Для завершения нажмите кнопку «Finish» в этом окне.

Следующим шагом будет загрузка установочных файлов Cisco VPN. Сделать это можно на либо же перейдя по зеркальным ссылкам ниже.

В результате у вас на компьютере должен быть один из следующих архивов.

Теперь кликните по скачанному архиву два раза ЛКМ . В результате вы увидите небольшое окошко. В нем можно выбрать папку, куда будут извлечены установочные файлы. Нажмите на кнопку «Browse» и выберите нужную категорию из корневого каталога. Затем нажмите кнопку «Unzip» .

Обратите внимание, что после распаковки система попытается автоматически запустить инсталляцию, но на экране появится сообщение с ошибкой, которое мы опубликовали в начале статьи. Дабы это исправить, необходимо зайти в папку, куда ранее были извлечены файлы, и запустить оттуда файл «vpnclient_setup.msi» . Не перепутайте, так как в случае запуска «vpnclient_setup.exe» вы снова увидите ошибку.

После запуска появится главное окно «Мастера установки» . В нем следует нажать кнопку «Next» для продолжения.

Далее необходимо принять лицензионное соглашение. Просто поставьте отметку возле строки с соответствующим названием и нажмите кнопку «Next» .

Напоследок остается лишь указать папку, куда программа будет инсталлирована. Мы рекомендуем оставить путь без изменений, но при необходимости можно нажать кнопку «Browse» и выбрать другой каталог. Затем нажмите «Next» .

В следующем окне появится сообщение о том, что все готово к установке. Для начала процесса жмем кнопку «Next» .

После этого начнется непосредственно установка Cisco VPN. По окончании операции на экране появится сообщение об успешном завершении. Остается лишь нажать кнопку «Finish» .

На этом процесс инсталляции Cisco VPN Client подошел к концу. Теперь можно приступить к настройке подключения.

Конфигурация подключения

Настроить Cisco VPN Client легче, чем может показаться на первый взгляд. От вас потребуется лишь определенная информация.

Если процесс подключения пройдет успешно, вы увидите соответствующее уведомление и иконку в трее. После этого VPN будет готов к использованию.

Устранение ошибки подключения

К сожалению, на Windows 10 попытка подключиться к Cisco VPN очень часто заканчивается следующим сообщением:

Чтобы исправить ситуацию, следует выполнить следующее:

Проделав описанные действия, вы избавитесь от ошибки при подключении к VPN.

На этом наша статья подошла к своему завершению. Надеемся, у вас получится установить клиент Cisco и подключиться к нужному VPN. Отметим, что данная программа не подойдет для обхода различных блокировок. Для этих целей лучше использовать специальные браузерные расширения. Ознакомиться со списком таковых для популярнейшего браузера и ему подобных вы можете в отдельной статье.