Release Notes For Cisco VPN Client, Release 5.0.07.0291-FIPS

2y ago
43 Views
4 Downloads
462.17 KB
18 Pages
Last View : 10d ago
Last Download : 3m ago
Upload by : Francisco Tran
Transcription

Release Notes for Cisco VPN Client,Release 5.0.07.0291-FIPSUpdated May 22, 2010These release notes address the following subjects: Introduction, page 2 System Requirements, page 2 Limitations of the FIPS Release, page 3 Licensing Requirements for the FIPS-Compliant VPN Client, page 3 Installation Notes, page 4 Advisories for Windows Vista Users, page 5 Usage Notes, page 6 Known Caveats, page 16 Resolved Caveats, page 16 Related Documentation, page 17Americas Headquarters:Cisco Systems, Inc., 170 West Tasman Drive, San Jose, CA 95134-1706 USA

IntroductionIntroductionThese release notes are for the CiscoFIPS-compliant VPN Client, Release 5.0.07.0291-FIPS. The nameof the file on the software download site is vpnclient-win-msi-5.0.07.0291-k9.exe.NoteThe Cisco FIPS-compliant VPN Client is based on the Cisco VPN Client, Release 5.0.07.If you do not require FIPS compliance for your organization, please download the standard release ofthe Cisco VPN Client.The Federal Information Processing Standard (FIPS) 140-2 is a U.S. government standard for specificsecurity requirements for cryptographic modules. This standard applies to all federal agencies that usecryptographic-based security systems to protect sensitive information in computer andtelecommunication systems.The VPN Client creates a secure connection over the Internet between a remote PC and an enterprise orservice provider Cisco VPN device. This connection lets you access a private network as if you were anon-site user.This document identifies the system requirements, limitations and restrictions, known issues, resolvedcaveats, and related documentation. Please read it carefully prior to installation. The section, “UsageNotes,” describes interoperability considerations and other issues you should be aware of when installingand using the VPN Client.System RequirementsVPN Client 5.0.07 supports the following Microsoft OSs: Windows 7 on x86 (32-bit only) Windows Vista on x86 (32-bit only) Windows XP on x86VPN 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.VPN Client supports up to one Ethernet adapter and one PPP adapter.VPN Client 5.0.x is incompatible with the combination of Cisco Unified Video Advantage 2.1.2 andMcAfee 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 orConfiguration.) 50 MB hard disk space. 128 MB RAM(256 MB recommended) Administrator privilegesThe VPN Client supports the following Cisco VPN devices: Cisco Series 5500 Adaptive Security Appliance, Version 7.0 or later.Release Notes for Cisco VPN Client, Release 5.0.07.0291-FIPS2

Limitations of the FIPS Release 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.Limitations of the FIPS ReleaseThis FIPS release of the Cisco VPN Client has the following limitations: Transforms—The FIPS Client only allows AES (128, 192, 256) and SHA-1 transforms. Certificates—The FIPS Client only supports certificates that use AES and SHA-1 signatures. Therelease only supports certificate functionality with the Microsoft CAPI certificate store and does notsupport any certification functionality that uses the Cisco certificate store. In addition, theCertificate tab of the Client GUI and its menu has been removed and does not appear to users.Licensing Requirements for the FIPS-Compliant VPN ClientThe Cisco FIPS-compliant VPN client is licensed based on the ASA 5500 Series Adaptive SecurityAppliance model. Each security appliance model requires a different license. The license does not affectthe number of allowed concurrent VPN sessions.The following table shows the Product numbers (also called SKUs) of the licenses for each securityappliance model:NoteProduct Number(also called SKU)Security Appliance ModelDescriptionASA-FPS-CL-5510 ASA 5510FIPS-compliant VPN Client LicenseASA-FPS-CL-5520 ASA 5520FIPS-compliant VPN Client LicenseASA-FPS-CL-5540 ASA 5540FIPS-compliant VPN Client LicenseASA-FPS-CL-5580 ASA 5580FIPS-compliant VPN Client LicenseASA-FPS-CL-5505 ASA 5505FIPS-compliant VPN Client LicenseASA-FPS-CL-5550 ASA 5550FIPS-compliant VPN Client LicenseEach new security appliance model purchased after August 31st, 2009 requires a FIPS-compliant VPNclient license. Cisco customers with current SMARTnet contracts who purchased an ASA 5500 SeriesAdaptive Security Appliance before August 31st, 2009 are not required to purchase a license for thesespecific appliances and may contact the Cisco TAC for information on upgrade rights for theFIPS-compliant VPN client.Release Notes for Cisco VPN Client, Release 5.0.07.0291-FIPS3

Installation NotesInstallation NotesRefer to “Cisco VPN Client User Guide for Windows, Chapter 2, for complete installation instructionsfor Windows users.NoteDue to issues surrounding network installation, Active Directory Group Policy software deployment isno longer supported. For more information and a workaround, refer to open caveat CSCse00525.Installation Notes - Windows PlatformsPlease note the following installation considerations for Windows usersAvoiding Vista Problems with the TCP/IP Registry Compatibility Service and the VPN Virtual AdaptorTo avoid problems with the TCP/IP Registry Compatibility service and the VPN Virtual Adaptor, westrongly recommend that Windows Vista users install Vista SP2 or later.For more information about a previous hotfix for this problem, go to this g from Windows XP Requires a Clean InstallationAfter upgrading Windows XP to Windows 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. Upgradingfrom a clean install of Windows XP to Vista has been tested and the VPN Client does work in thissituation.However, upgrading a Windows XP installation with legacy applications ranging from Firewalls,Antivirus, device drivers, and so on to Windows Vista is not supported, because the problems stem fromthe legacy applications no longer supported by the OS.Installing the VPN Client Software Using the MSI InstallerYou can use the MSI installer on Windows Vista and XP. Installing with MSI requires administratorprivileges.Before installing the Windows MSI installation package, you must manually uninstall the previous VPNClient if it is older than Release 4.7. The MSI installer does not uninstall the older versions; it attemptsto 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 VistaFor Windows Vista, please use add/remove programs to uninstall the VPN Client before upgrading to anew Client release.Release Notes for Cisco VPN Client, Release 5.0.07.0291-FIPS4

Advisories for Windows Vista UsersUsing the VPN ClientTo use the VPN Client, you need: Direct network connection (cable or DSL modem and network adapter/interface card), or Internal or external modemTo connect using a digital certificate for authentication, you need a digital certificate signed by one ofthe following Certificate Authorities (CAs) installed on your PC: Entrust Technologies (www.entrust.com) Netscape (www.netscape.com) Verisign, Inc. (www.verisign.com) Digital certificate stored on a smart card. The VPN Client supports smart cards via the MS CAPIInterface.The VPN Client accepts a blank password for certificate retrieval, but should not.About Version NumbersVPN Client software uses an all-numeric version numbering system to facilitate the automatic updatefunction. Release numbers are represented in the format: major release . minor release . sustaining release . build The major and minor release numbers represent the feature level of the product. Major and minorreleases implement new product capabilities. The sustaining and build release numbers representsignificant or minor patch levels, respectively. For example, 5.0.01.06000 represents feature release5.0.01, build 600.All sustaining and build releases are cumulative; however, we do not release all build numbers. The buildnumber for this release is 5.0.07.0291.Advisories for Windows Vista UsersWindows Vista users should be aware of the following characteristics of the Cisco VPN Client.Connection TimeUsing the VPN Client to connect a PC running Vista system might take longer than one runningWindows XP. The actual time it takes to connect might vary from customer to customer.Unsupported FeaturesThe Cisco VPN Client for Windows Vista does not support the following features: Upgrade from Windows XP (clean OS installation required). Start Before Logon Integrated Firewall InstallShield AutoUpdateRelease Notes for Cisco VPN Client, Release 5.0.07.0291-FIPS5

Usage NotesUsage NotesThis 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 “Known Caveats” onpage 16 of this document for the list of known problems.NoteSupport for this release is provided through the Cisco TAC for customers with SMARTnet supportcontracts.Split DNS with WildcardsA split-dns value containing wildcards can cause a system failure when a Windows user accesses certainURLs. 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 systemfailure. To avoid these failures, move the VPN adapter to the top of the binding order list of networkadapters. Note that Split DNS requires entries only for internal domains.Potential Compatibility IssuesYou might encounter the following compatibility issues when using the VPN Client with specificapplications. Whenever possible, this list describes the circumstances under which an issue might occurand workarounds for potential problems.Windows Interoperability IssuesThe following known issues might occur with the indicated Microsoft Windows operating systems andapplications software.Microsoft Internet Connection Sharing IncompatibleThe VPN Client is not compatible with Microsoft ICS (Internet Connection Sharing (ICS) on the samePC.VPN Client Cannot Launch Microsoft Connection ManagerThe VPN Client does not detect a dialup connection made with Microsoft Connection Manager becauseof incompatibilities between the requirements of the two applications.Microsoft MSN InstallationMicrosoft’s MSN installation fails if you have already installed the VPN Client. Uninstall the VPNClient 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 ShutdownIf the VPN Concentrator is configured to send WINS server addresses to the VPN Client and the PC isshut down or restarted without first disconnecting the VPN Client, the WINS servers are not removedfrom the network properties. This might cause local PC registration and name resolution problems whilenot connected with VPN.Release Notes for Cisco VPN Client, Release 5.0.07.0291-FIPS6

Usage NotesTo 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 yournetwork 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 WindowsLogon Properties, check Disconnect VPN connection when logging off.DNSFor DNS resolution, if the DOMAIN NAME is not configured on the network interface, you must enterthe 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 aninstalled 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 DisconnectThe 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. RunMicrosoft 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 isinstalled but not configured for email, although it is the default mail client. It is caused by a RegistryKey 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 orInternet 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 OnlyVPN Encapsulation adds to the overall message length. To avoid refragmentation of packets, the VPNClient must reduce the MTU settings. The default MTU adjusted value is 1300 for all adapters. If thedefault adjustments are not sufficient, you may experience problems sending and receiving data. Toavoid fragmented packets, you can change the MTU size, usually to a lower value than the default. Tochange the MTU size, use the VPN Client SetMTU utility. If you are using PPPoE, you may also haveto set the MTU in other locations. Refer to the following table for the specific procedures for each typeof 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 datathat was passed down from the Network Layer, plus (sometimes) trailer data. An Ethernet frame has anMTU of 1500 bytes, but the actual size of the frame can be up to 1526 bytes (22-byte header, 4-byte CRCtrailer).Release Notes for Cisco VPN Client, Release 5.0.07.0291-FIPS7

Usage NotesRecognizing a Potential MTU ProblemIf you can connect with the Cisco VPN Client but cannot send or receive data, this is likely an MTUproblem. 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 ValueIf you do not experience a problem, do not change the MTU value. Usually, an MTU value of 1300works. 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.Connection TypeProcedurePhysical AdaptersUse the SetMTU utility supplied with the Cisco VPN Client.Dial-upUse the SetMTU utility supplied with the Cisco VPN Client.PPPoE - All Vendors Use SetMTU.Cert DN Matching Cannot Match on Email Field EAYou cannot match the Cert DN field (EA) when using the Peer Cert DN Verification feature on the VPN3000 Concentrator because the VPN 3000 Concentrator does not assign a value to that field.VPN Dialer Application Can Load During OS Shutdown or RestartWhen using the VPN Client Start Before Logon feature in “fallback” mode, the VPN dialer applicationloads during a shutdown or restart of the operating system. This does not cause any problems and can beignored.America Online (AOL) Interoperability IssuesThe following interoperability issues apply to AOL dialup connections only.AOL Versions 5.0 and 6.0The VPN Client supports AOL Version 5.0. AOL Version 6.0 is also supported, with one limitation: whenconnected, browsing in the network neighborhood is not available.AOL Version 7.0AOL Version 7.0 uses a proprietary heartbeat polling of connected clients. This requires the use of splittunneling to support the polling mechanism. Without split tunneling, AOL disconnects after a period oftime between 5 and 30 minutes.Release Notes for Cisco VPN Client, Release 5.0.07.0291-FIPS8

Usage NotesAOL 7 Disconnects after VPN AuthenticationWhen making a dialup connection with AOL 7.0 Revision 4114.537, then attempting to connect with theVPN Client, AOL might disconnect while the user is being authenticated. This is an AOL issue, not aVPN Client problem (CSCdy45351).VPN Client Fails to Connect over Some AOL Dialup ConnectionsThe 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 toa different connection type for the second attempt. This second attempt can sometimes cause AOL tocommunicate over two PPP adapters (visible in ipconfig /all output). When this happens, the VPN Clientcannot 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 PPPadapters.ZoneAlarm Plus Versions 3.1.274 and Earlier Are Incompatible with VPN ClientThe following known incompatibility exists between the Cisco VPN Client and Zone Labs ZoneAlarmPlus version 3.1.274 and earlier. If you are using such a version of ZoneAlarm Plus, please visithttp://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 thefollowing occur when the PC boots:ZAPLUS.exe has generated errors and will be closed by Windows. You will need to restart theprogram.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 ( nosymbols ).The result of such errors is that the ZoneAlarm GUI does not run, and therefore a user cannot changeany settings in ZoneAlarm Plus or allow new programs to access the Internet. (CSCdy16607).CheckPoint ZoneAlarm (Integrity Agent) Is Incompatible with VPN ClientThe VPN Client is not compatible with the software firewall provided with ZoneAlarm (Integrity Agent)v8.0.298. (CSCtc46109)Auto-update Package No Longer SupportedVPN Client does not support the auto-update package for versions higher than 5.0.3.0560.Release Notes for Cisco VPN Client, Release 5.0.07.0291-FIPS9

Usage NotesClose Client before HibernationWindows Vista leave the client hanging while it attempts to disconnect upon awakening afterhibernation. To avoid this issue, close the client interface before hibernation and reopen it uponawakening.Upgrading Zone-Alarm Pro to Version 3.7.098 Causes Error When VPN Client IsAlready Installed on the PCUpgrading ZoneAlarm Pro version 3.5.xxx to ZoneAlarm Pro version 3.7.098 when the VPN Client isinstalled on the PC might cause the following error to appear:“The procedure entry point DbgProcessReset could not be located in the dynamic link libraryVSUTIL.dll.”Click OK. The installation continues. See ZoneLabs bug number 10182.DHCP Route RenewalIf the public network matches the private network (for example, a public IP address of 192.168.1.5, witha subnet mask of 255.255.0.0, and an identical private IP address) and the public network route metricis 1, traffic might not be tunneled to the private network. The same problem can occur if you are usinga virtual adapter and the public metric is smaller than the virtual adapter metric.In Windows Vista, you can increase the metric of the public network as follows:Step 1Select Start Control Panel (Network and Internet) View Network Status and Tasks.Step 2Right-click the icon representing the public interface and select Properties.Step 3Select Internet Protocol Version 4 and click Properties.Step 4Click 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 1Select Start Settings Control Panel Network and Dial-up Connections.Step 2Select the public interface and click properties for the public interface.Step 3Select Internet Protocol (TCP/IP) and get the properties for the Internet Protocol (TCP/IP).Step 4Click Advanced, and set the interface metric to 2 or greater.Release Notes for Cisco VPN Client, Release 5.0.07.0291-FIPS10

Usage NotesWindows XP Only—Data Meant for Private Network Stays Local if VPN ClientLocal Network Is on Same IP Subnet as Remote Private NetworkThis problem occurs only with the VPN Client, Release 4.6 and only with Virtual Adapter onWindows XP when the VPN Client local network is on the same IP subnet as the remote privatenetwork. When a VPN connection is up, data meant for the private network stays local. For example:192.168.1.0/255.255.255.0Beginning with VPN Client, Release 4.6, the Virtual Adapter attempts to modify local route metricsto allow data to pass over the VPN tunnel. In some cases, it is impossible for the VPN Client to makethis modification.To work around this problem, make the change manually, using the following procedure:Step 1Run Control Panel Network and Dialup Connections.Step 2Right-click on the adapter in question and select Properties.Step 3From the Adapter Properties dialog, select TCP/IP from the list and click Properties.Step 4Click Advanced and increase the number in the “Interface metric” box by 1 (it is usually 1, so making it2 works).Step 5Click OK to exit out of all dialogs.Step 6The VPN connection should now work.DNS Server on Private Network with Split DNS Causes ProblemsWhen an ISP DNS server is included in the Split Tunneling Network List and Split DNS Names areconfigured, 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 DNSqueries that are about hosts on the Split DNS Names list to corporate DNS servers, and discards all DNSqueries 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 NetworkList. 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 TunnelingNetwork List, or do not configure split DNS (CSCee66180).No Limit to Size of Log FileWhen logging is enabled on the VPN Client, all of the log files are placed in the Program Files\CiscoSystems\VPN Client\logs directory and are date and time stamped. There is no limit to the size of thelog when logging is enabled. The file will continue to grow in size until logging is disabled or the VPNClient program is closed. The log is still available for viewing until the VPN Client program isre-launched, at which time the display on the log tab and log window are cleared. The log file remainson the system and a new log file is created when the VPN Client, with logging enabled, is launched.Release Notes for Cisco VPN Client, Release 5.0.07.0291-FIPS11

Usage NotesStart Before Logon and Microsoft Certificate with Private Key Protect FailsTrying to connect the VPN client using Start Before Logon (SBL) and Microsoft Machine-basedcertificates 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 areeither 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 WindowsDesktop. You do not see this message while at the Logon desktop, therefore the VPN Client cannot gainthe 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 notbe accessible before logging on). Instead of using Start Before Logon, log on to the PC using cached credentials, make the VPNconnection, and— using the “stay connected at logoff” feature—logoff/logon with the VPNestablished to complete the domain logon.Linksys Wireless AP Cable/DSL Router Version 1.44 or Higher FirmwareRequirementTo use the VPN Client behind a Linksys Wireless AP Cable/DSL router model BEFW11S4, the Linksysrouter must be running version 1.44 or higher firmware. The VPN Client cannot connect when locatedbehind 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 CertificatesYou can configure the VPN Client to require the presence of a smart card when certificates are used. Ifthis feature is configured, the VPN Client displays an error message if a smart card is not present. Thecertificates need not be present on the smart card itself. To configure this feature, add the following lineto the user’s client profile, specifying the appropriate vendor for your smart card:SmartCardName Name of Smart Card Vendor If you are using pre-shared keys instead of certificates, this requirement is not enforced, even ifconfigured.To disable the smart card verification function, completely delete the entry: SmartCardName text from the user’s client profile (CSCec82220).Release Notes for Cisco VPN Client, Release 5.0.07.0291-FIPS12

Usage NotesAllowing ICMP Traffic to Pass Through the FirewallThe following configurations allow inbound ICMP packets (pings) when the default firewall rule for theCentralized 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 [Main] section of the vpnclient.ini file. A connection is made to the VPN Concentrator that pushes the default CPP firewall rule to the VPNClient.Use the parameter, “StatefulFirewallAllowICMP 1”only if you want to allow ICMP traffic to passthrough the firewall.Use Zone Labs Integrity Server 2.1.052.0 or Higher with VPN Client 4.0Versions of the Zone Labs Integrity Server earlier than 2.1.052.0 exhibit the following problem. If twoor more VPN Clients running on Windows XP are connected to a VPN 3000 Series Concentrator andreceive firewall policy from a ZoneLabs Integrity Server, the Integrity Server registers only oneconnection.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 Serverversion 2.1.052.0 fixes this issue.Restart VPN Client Service if You Install VPN Client before Zone AlarmThe 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 trustedzone.VPN Client cTCP Connection Fails If Checkpoint Client Is InstalledWhen the Checkpoint VPN-1 SecuRemote client is installed with the 4.6 or higher VPN Client, and theVPN Client attempts to connect using cTCP, the VPN Client cannot make the connection. Connectionsdo work with UDP, NAT-T, and non-NAT connections.To make a connection with cTCP when the Checkpoint VPN-1 SecuRemote is installed, you mustdisable the Check Point SecuRemote driver in the Connections Properties. To do this, you must beadministrator. Follow these steps:Step 1Click Start Settings Control Panel Network and Dial-up Connections.Step 2Select the Local Area Connection you use.Step 3Click on File Properties.Step 4Uncheck Check Point SecuRemote, and click OK.Release Notes for Cisco VPN Client, Release 5.0.07.0291-FIPS13

Usage NotesInstalling the VPN Client on a Japanese System Using MSIFollow these steps to install the VPN Client on a Japanese system, using Microsoft Installer:Step 1Extract the file vpnclient-win-msi-5.0.00.0340-k9.exe to any folder.Step 2Execute vpnclient setup.msi. The installer runs in English.Step 3After installation is complete, modify vpnclient.ini as follows: ClientLanguat jpStep 4Launch the VPN Client.Duplicate IP Address Triggers Error 442 on Windows VistaThe following error “Reason 442: failed to enable virtual adapter” appears after Windows Vista reportsa duplicate IP address detected. Subsequent connections fail with same message, but the OS does notreport a duplicate IP address detected.To work around error 442, do the following steps:Step 1Open “Network and Sharing Center”.Step 2Select “Manage Network Connections”.Step 3Enable the Virtual Adapter (“VA”—Cisco VPN Adapter).Step 4Right-click on Cisco VPN Adapter and select “Diagnose” from the context menu.Step 5Select “Reset the network adapter Local Area Connection X”.If this procedure does not work, run the following command from cmd:reg add eters /v ArpRetryCount /tREG DWORD /d 0 /fThen reboot.This resolves the issue until the OS reports a duplicate IP address again. Follow the preceding steps toresolve it again.If that doesn't work, you might have UAC enabled. If so, you must run cmd as administrator and repeatthe previous registry workaround.Release Notes for Cisco VPN Client, Release 5.0.07.0291-FIPS14

Usage NotesWindows Vista Window Auto-tuning Feature Might Cause Net

3 Release Notes for Cisco VPN Client, Release 5.0.07.0291-FIPS Limitations of the FIPS Release † 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. Limitations of the FIPS Release This FIPS relea

Related Documents:

Cisco ASA 5505 Cisco ASA 5505SP Cisco ASA 5510 Cisco ASA 5510SP Cisco ASA 5520 Cisco ASA 5520 VPN Cisco ASA 5540 Cisco ASA 5540 VPN Premium Cisco ASA 5540 VPN Cisco ASA 5550 Cisco ASA 5580-20 Cisco ASA 5580-40 Cisco ASA 5585-X Cisco ASA w/ AIP-SSM Cisco ASA w/ CSC-SSM Cisco C7600 Ser

SSL VPN Client for Windows/Mac OS ZyWALL 110 VPN Firewall ZyWALL 1100 VPN Firewall USG20W-VPN VPN Firewall ZyWALL 310 VPN Firewall. Datasheet ZyWALL 110/310/1100 and USG20(W)-VPN 5 Model ZyWALL 110 ZyWALL 310 ZyWALL 1100 USG20-VPN USG20W-VPN Prod

The following is a list of user guides and other documentation related to the VPN Client for Mac OSX and the VPN devices that provide the connection to the private network. Release Notes for the Cisco VPN Client, Release 4.0 Cisco VPN Client Administrator Guide, Release 4.0 Cisco VPN 3000 Series Concentrator Getting Started Guide .

VPN Passthrough: having the device installed as an intermediate part of a secure VPN, requires additional VPN gateway. Remote User VPN Site-to-Site VPN Termination PPTP Termination ( refer to page 15) Peplink Site-to-Site VPN ( refer to page 10) . t Requirement System Requirement for Site-to-Site VPN Configuration When configuring a VPN .

Dec 22, 2015 · Cisco ISR G2, ISR-800 and CGR 2010 Security Target 8 TOE Hardware Models ISR G2 (ISM-VPN-19, ISM-VPN-29, ISM-VPN-39) - Cisco 1905 ISR Cisco 1921 ISR Cisco 1941 ISR Cisco 1941W ISR Cisco 2901 ISR Cisco 2911 ISR Cisco 2921 ISR Cisco 2951 ISR Cisco 3925 ISR

Dec 13, 2011 · 3 Release Notes for Cisco VPN Client, Release 5.0.07.0290 Downloading the Latest Version † 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. Downloading the Latest Version To download the version of AnyConnect, you must be a registered user of Cisco.com.File Size: 212KB

Oct 27, 2014 · Cisco ISR 4400 Series Cisco ISR 4300 Series Cisco ISR 4431 Cisco ISR 4321 Cisco ISR 4451 Cisco ISR 4331 Cisco ISR 4351 Table 1 Cisco IOS XE 3S–to–Cisco IOS Release Number Mapping Cisco IOS XE 3S Release Cisco IOS Release 3.14 15.5(1)S 3.13S 15.4(3)S 3

* Corresponding author: Room A02, University of Ulster, Shore Road, Co. Antrim, BT37 0QB email: vkborooah@gmail.com. ** Email: at@monkprayogshala.in . 2 1. Introduction . If countries have a ‘unique selling point’ then India’s must surely be that, with over 700 million voters, it is the world’s largest democracy. Allied to this is the enthusiasm with which Indians have embraced the .