|
|
 |
Note You can find the most current documentation for the VPN Client at http://www.cisco.com or http://cco.cisco.com. These electronic documents may contain updates and changes made after the hard copy documents were printed. |
These release notes support VPN Client software Release 4.0. These release notes describe new features, limitations and restrictions, interoperability notes, caveats, and related documentation. Please read the release notes carefully prior to installation. The section, "Usage Notes," describes interoperability considerations and other issues you should be aware of when installing and using the VPN Client.
Caveats Resolved in Release 4.0
Obtaining Technical Assistance
The VPN Client is an application that runs on a Microsoft® Windows®-based PC, a Sun ultraSPARC workstations, a Linux desktop, or a Macintosh (Mac) personal computer that meets the system requirements stated in the next section. In this document, the term "PC" applies generically to all these computers, unless specified otherwise.
The VPN Client on a remote PC, communicating with a Cisco VPN device at an enterprise or service provider, creates a secure connection over the Internet that lets you access a private network as if you were an on-site user. This secure connection is a Virtual Private Network (VPN).
Refer to Chapter 2, "Installing the VPN Client," in the VPN Client User Guide for Windows, Release 4.0 or Cisco VPN Client User Guide for Mac OS X, as appropriate for your platform, for a complete list of system requirements and installation instructions.
The Cisco VPN Client supports the following Cisco VPN devices:
Because of platform differences, the installation instructions for Windows and non-Windows platforms also differ.
The following notes are important for users who are upgrading to Windows XP and users who want to downgrade to an earlier version of the VPN Client software.
Release 4.0 includes the following installation considerations for Windows users:
Installing the VPN Client software on Windows NT, Windows 2000, or Windows XP with InstallShield requires Administrator privileges. If you do not have Administrator privileges, you must have someone who has Administrator privileges install the product for you.
If you are using the MSI installer, you must have Windows NT-based products such as Windows NT 4.0 (with SP6), Windows 2000, or Windows XP. Installing with MSI also requires Administrator privileges.
|
Note Windows Installer 2.0 must be installed on a Windows NT or Windows 2000 PC before configuring the PC for a Restricted User with Elevated Privileges (CSCea37900). |
When you attempt to install the VPN Client using MSI install (vpnclient_en.exe) on NT SP3, SP4, or SP5, the error messages do not indicate that the VPN Client cannot be installed on those operating systems because they are unsupported. Once the errors occur, no other messages are displayed and the installation is aborted.
When you attempt to run vpnclient_en.exe on Windows NT SP3, SP4, or SP5 you see the following messages:
"Cannot find the file instmsiw.exe (or one of its components). Make sure the path and filename are correct and that all the required libraries are available."
"Cannot find the file MSIEXEC (or one of its components). Make sure the path and filename are correct and that all the required libraries are available."
The Windows Installer (MSI) can be installed only on NT SP6, so the error messages you see using earlier service packs are due to an MSI incompatibility (CSCdy05049).
The following sections describe actions you must take when installing the VPN Client on a Solaris platform.
If you have a previous version of the VPN Client running under Solaris, you must uninstall the older VPN Client before installing a new VPN Client. You are not required to uninstall an old VPN Client, if one is present, before installing a new VPN Client for Linux or Mac OS X.
Refer to the Cisco VPN Client User Guide for Linux, Solaris, and Mac OS X, Chapter 2, for complete uninstallation information.
If you have an IP firewall installed on your workstation, the reboot after installation of the VPN Client takes an inordinate amount of time. This is caused by a conflict between the vpnclient kernel module cipsec and the ipfilter firewall module. To work around this issue, disable the ipfilter firewall kernel module before you install the VPN Client (CSCdw27781).
Release 4.0 of the VPN Client software includes the following new features.
A virtual adapter is a software-only driver that acts as a valid interface in the system. Its purpose is to solve protocol incompatibility problems. The virtual adapter appears in the network properties list just like a physical adapter.
In Release 4.0, the VPN Client provides a consistent graphical user interface across all supported Windows operating systems and Mac OS X, recognizing that the Windows and Mac operating systems follow different conventions, and that the Windows version has additional features. The VPN Client documentation is based on this new user interface.
In Release 4.0, the VPN Client can display to the user the reason for a VPN 3000 Concentrator-initiated disconnection. If the VPN 3000 Concentrator, Release 4.0, disconnects the VPN Client and tears down the tunnel, the VPN Client, Release 4.0, displays a popup window showing the reason for the disconnect and also logs a message to the Notifications log and the IPSec log file. For IPSec deletes that do not tear down the connection, the event message appears only in the log file.
The administrator on the VPN 3000 Concentrator can enable or disable this feature, called Alerts in the VPN Concentrator configuration. It is not configurable on the VPN Client. When this feature is enabled, the VPN 3000 Concentrator and the VPN Client negotiate whether to display these messages. See the Cisco VPN Client User Guide, Release 4.0, for a description of the conditions that can cause such disconnects.
Rather than creating a host-to-network security association (SA) pair for each split-tunneling network, this feature provides a host-to-ALL approach, creating one tunnel for all appropriate network traffic apart from whether split-tunneling is in use. With this feature, the VPN Client supports a single SA per VPN connection and directs all the appropriate traffic through this tunnel, regardless of whether split tunneling is in use. The Statistics page on the VPN Client reflects the traffic for this single SA.
In Release 4.0, the VPN Client supports Sygate Personal Firewall and Sygate Personal Firewall Pro, Version 5.0, Build 1175 and higher. Other supported features new with this release include:
In Release 4.0, the VPN Client is compatible with VPN clients from Microsoft, Nortel, Checkpoint, Intel, and others. This feature offers the ability to use other VPN products while the Cisco VPN Client is installed.
The VPN Client, Release 4.0, includes improvements in RADIUS SDI XAuth handling, which may improve performance. Administrators can configure this feature in the .pcf file and the .ini file. For information, see VPN Client Administrator Guide, Release 4.0, Chapter 2.
The format of the names of log files generated by the VPN Client GUI has changed to LOG-yyyy-MM-dd-hh-mm-ss.txt from MMM-d-yyyy-hh-mm-ss.log. This new format complies with the ISO 8601 extended specification for representations of dates and times and avoids issues with localization.
The new log file names have a chronological order that is the same as their alphanumeric order. This provides for a method of enumerating only the log files generated by the GUI.
This section lists issues to consider before installing Release 4.0 of the VPN Client software.
In addition, you should be aware of the open caveats regarding this release. Refer to "Open Caveats" of these Release Notes for the list of known problems.
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.
The following known issues might occur with the indicated Microsoft Windows operating systems and applications software.
On Windows 95 and Windows 98, dynamic WINS support works with DHCP-enabled adapters (for example, PPP or NIC adapters that get their IP information dynamically). For static configurations, users must manually configure the adapters with WINS information.
Users running Windows NT 4.0 with Service Pack 4 require a hot fix from Microsoft for proper operation. This fix is available on the Microsoft GetHostByName API Returns Unbindable Address page: http://support.microsoft.com/support/kb/articles/Q217/0/01.ASP.
The following problem has occurred on some Windows NT SP3 systems (CSCdt11315).
When using the Client with digital certificates stored in the Microsoft certificate store, the Client may fail to connect. This is accompanied by the following Client event in the Log Viewer:
4101 13:41:48.557 01/05/01 Sev=Warning/2 CERT/0xA3600002
Could not load certificate (null) from the store.
Workaround: Two workarounds exist. Choose one of the following:
The VPN Client does not see a dialup connection made with Microsoft Connection Manager because of incompatibilities between the requirements of the two applications (CSCdx85663).
On some Windows 98 PCs with the VPN Client installed, if you restart the PC, it may stop responding (that is, "hang") on the screen that says "Windows is shutting down".
Wait a minute. If the PC is still not responding, press the reset button. When the PC reboots, it should not run through ScanDisk, indicating the shutdown was successful in closing all open files. This problem may occur on some PCs and not on others, and we are looking for a solution. Windows 98 shutdown has numerous issues, as can be seen the following Microsoft Knowledge Base Article:
"Q238096 - How to Troubleshoot Windows 98 Second Edition Shutdown Problems" (CSCdt00729).
For the Cisco VPN Client running on a Windows 2000 system, you cannot access Microsoft resources unless you add the Client for Microsoft Networks for the Dial-up adapter.
Using versions of the Aladdin Runtime Environment (RTE) on Windows NT and Windows 2000 can cause the following behavior. The login prompt that is posted by the Aladdin etoken when connecting the VPN Client can get hidden in the background. If this happens, the VPN connection can timeout and fail with the following event:
"System Error: Connection Manager failed to respond."
A side effect of this is that the VPN Client's service and dialer might become out of synch, and the PC might need to be restarted (CSCdv47999). To avoid this issue, use the Aladdin Runtime Environment (RTE) version 2.65 or later.
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.
If the VPN Concentrator is configured to send WINS server addresses down 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:
The 4.0 VPN Client with Auto Initiation enabled on a Windows NT system may exhibit the following behavior. After removing a NIC card, the VPN Client may continue to trigger an Auto Initiation connection event though the NIC card has been removed. To stop its connection attempts, you can place the VPN Client in Suspended mode after a failed or canceled VPN connection. You can also disable this feature from the GUI by using Options > Automatic VPN Initiation, and unchecking "Enable". If you add a new NIC, the problem goes away. (CSCdx46812).
For DNS resolution, if the DOMAIN NAME is not configured on the network interface, you need to enter the fully qualified domain name of the host that needs to be resolved.
Network ICE's BlackICE Defender is a traffic monitoring security product. If you properly configure it, BlackICE Defender can work with the VPN Client. You must configure BlackICE Defender for Trusting, Nervous, or Cautious mode. If you use Nervous or Cautious mode, add the public IP address of the VPN Concentrator to the list of trusted addresses. You can now configure the VPN Client to work with BlackICE Defender configured for Paranoid mode when in Tunnel-everything mode. Split Tunneling requires BlackICE to be in Trusting, Nervous, or Cautious mode.
The Cisco VPN Client firewall has the following requirements for BlackICE (BlackICE Defender 2.5 or greater or BlackICE Agent 2.5 or greater). For BlackICE Defender 2.5, copy the BICTRL.DLL file from the Cisco installation release medium to the BlackICE installation directory on the VPN Client PC. This is a mandatory step for making a connection requiring BlackICE.
BlackICE Defender version 2.9 and greater includes the BICTRL.DLL file in the Network ICE distribution medium, so that you do not need to copy it from the Cisco installation release medium.
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:
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).
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:
Usually, an MTU value of 1300 works. If it doesn't, 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.
Versions of the Asante firmware caused a problem with rekeying and keepalives when a VPN Client had an all-or-nothing connection to a VPN Concentrator through an Asante FR3004 Cable/DSL router. Version 2.15 (or later) of the Asante firmware resolves these issues. For more information about Asante cable/DSL routers, see the following Web sites:
All Nexland Pro routers support passing multiple IPSec sessions through to Cisco VPN 3000 Series Concentrators. To enable this function, the Nexland user must select IPSec Type 2SPI-C on the Nexland options page.
The discontinued Nexland ISB2LAN product correctly handles a single connection, but problems can occur when attempting to make multiple client connections to the same Secure Gateway from behind an ISB2LAN Nexland Cable/DSL router. Nexland has fixed this problem in the Nexland Pro series of routers (CSCdt10266).
You cannot match on the Cert DN field (EA) when using the Peer Cert DN Verification feature because the VPN Concentrator does not assign a value to that field (CSCdx25994).
When using the VPN Client's Start Before Logon feature (Windows NT, Windows 2000, or Windows XP) in "fallback" mode, the VPN dialer application loads during a shutdown or restart of the operating system. This will not cause any problems and can be ignored (CSCdu02071).
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 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.
When making a dialup connection with AOL 7.0 Revision 4114.537 (for Windows 95, 98, ME, Windows 2000 and XP), 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).
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.
The workaround is to try to reconnect the dialup connection to try to avoid getting two PPP adapters (CSCea29056).
The following known issues might occur when using the VPN Client with the indicated browser software.
The following error occurs in the VPN Client log when using a Digital Certificate from the Microsoft Certificate Store. This can occur on Windows NT 4.0 with Service Pack 5 and on Internet Explorer 4.0 with SP2 and using the VPN Client v3.1 or v3.5:
"Could not load certificate cn=Joe Smith,ou=Engineering,o=MyCompany,l=Buffalo, st=new york,c=US,e=jsmith@mycompany.com from the Unsupported Store store"
Both the VPN Client and the Certificate Manager can see and validate the Certificate, but when you try to connect using that Certificate, you get a message in the Connection History dialog that says, "Failed to establish a secure connection to the security gateway".
To fix this problem, do one of the following:
To use certificates with non-exportable keys, you must have the VPN Client, Release 3.6 or 4.0, and your PC must have Internet Explorer version 5.0 SP2 or later installed to function properly. (CSCdx90228).
The following known issues might occur when using Entrust Entelligence software with the VPN Client.
Using the VPN Client with Entrust Entelligence might result in a delay of approximately 30 seconds if you are trying to connect while Entrust is "online" with the CA. This delay varies, depending on your Entrust CA configuration. If the Entrust CA is on the private network, then the chance of Entrust being online are low, since the VPN connection is needed to communicate with the CA.
If you experience this delay, do one of the following:
When using VPN Client with Start Before Logon (Windows NT and 2000) and Entrust Entelligence, the Entrust system tray icon indicates that it is "logged out" once in Windows. It is really logged in, just not in the normal Windows desktop. The reason for this is that the context that Entrust was logged into was on the "Logon desktop". This is an Entrust issue, not a VPN Client problem.
Entrust operates normally once logged into within Windows (CSCdu29239).
After establishing a VPN connection with Entrust Entelligence certificates, the Entrust client may appear offline. It may appear this way even after the Entrust client has successfully communicated with the Entrust i500 directory.
To work around this issue, do one of the following:
When using the Release 3.5.1 or 3.1 VPN Client with the Entrust Entelligence 4.0 software, the Start Before Logon feature does not function properly. Upgrading to Entrust Entelligence 5.1 resolves this problem (CSCdu61926).
When using the VPN Client with Start Before Logon and Entrust Entelligence, some Entrust dialogs do not display properly on the logon desktop that displays before going into Windows NT or Windows 2000. The first time the VPN Client dialer and service access the Entrust certificates, it prompts for a security check. This prompt displays in Windows, but not at the logon screen.
To work around this problem, connect the VPN Client once, while in Windows and after installing, to register the VPN applications (ipsecdialer.exe and cvpnd.exe) with Entrust. Once you have done this you can use it at the logon desktop (CSCdu62212).
Entrust Entelligence certificate renewal (key update) will not work over a VPN Client connection unless Entrust Entelligence version 5.1 SP3 or later is being used. Other Entrust Entelligence operations using older versions work properly.
To work around this issue, do one of the following:
The Glossary button at the top of all Help screens tries to contact univercd at www.cisco.com (the Cisco documentation site). This connection requires connectivity to Cisco's main web site. If your PC does not have a corporate Internet connection or your firewall blocks access, the following error appears when you attempt to access the Glossary:
"The page cannot be displayed."
To access the Glossary, you must be connected to www.cisco.com (CSCdy14238).
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, the following errors 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, ZAPLUS.EXE, generated an application error. The error occurred on 7/23/2002... The exception was c0000005 at address 00401881 (<nosymbols>).
Similar errors occur on other Windows operating systems.
The result of this error is that the ZoneAlarm GUI does not run, and therefore a user can not change any settings in ZoneAlarm Plus or allow new programs to access the Internet.(CSCdy16607).
The Loopback address and the VPN 3000 Concentrator's address are automatically added to the ZoneLabs "Trusted Zone" on Windows NT-based systems.
If a Windows NT based-PC has ZoneAlarm, ZoneAlarm Pro, or Zone Labs Integrity Agent, and the VPN Client Release 4.0 installed on it, the loopback address (127.0.0.1) is automatically added to Zone Labs "Trusted Zone" when the Client service is started. Additionally, the VPN 3000 Concentrator's address is automatically added to the "Trusted Zone" when a connection is made (CSCea61272).
Linux users running 2.4 kernels may encounter the following warning when the VPN Client kernel module is loaded:
Warning: loading /lib/modules/2.4.18-3/CiscoVPN/cisco_ipsec will taint the kernel: no license
This message indicates that the VPN Client kernel module is not licensed under the GPL, so the Linux kernel developers will not debug any kernel problems that occur while this kernel module is loaded. This message does not affect the operation of the VPN Client in any way (CSCdy31826).
In a Windows 2000 or Windows XP environment, 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's route metric is 1, then traffic might not be tunneled to the private network (CSCdz40609). 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 2000 and Windows XP, you can increase the metric of the public network by doing the following steps:
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.
If the VPN Client running in the Solaris environment uses routed RIP to learn its default route, you might lose connectivity. This is because RIP is blocked when the VPN Client is connected in all tunneling mode (CSCdv75825).
This problem occurs only with the VPN Client, Release 4.0 and only with Virtual Adapter (Windows 2000 and Windows XP), when the VPN Client's 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
The VPN Client, Release 4.0, with 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 (CSCdz38680).
To work around this problem, make the change manually, using the following procedure:
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.
The supported version of Sygate Personal Firewall is version 5.0, build 1175. Earlier versions might cause the following Blue screen to occur on a Windows NT-based system that has made many connects/disconnects with the VPN Client (CSCdy62426):
Stop: 000000d1 (BAD0B0B8, 00000002, 00000000, BFF12392)
***Address BFF12392 base at BFF10000, Datestamp 3CCDEC2C - Teefer.sys
The VPN Client for Windows, Release 4.0, requires the use of the Windows 98 or later operating system. We recommend updating your Operating system to a newer version of Windows (CSCea06231).
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 (CSCdy87504). The log file remains on the system and a new log file is created when the VPN Client, with logging enabled, is launched.
Trying to connect the VPN client using Start Before Logon (SBL) and Microsoft Machine-based certificates fails. This 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:
Start Before Logon fails if the VPN Client is downgraded from Release 4.0 to 3.6. The reason for this is that the file csgina.dll is upgraded when the VPN Client version 4.0 is installed. If the VPN Client is downgraded to version 3.6, the csgina.dll file for version 4.0 is not replaced, and this breaks ability in the VPN Client version 3.6 to Start Before Logon (CSCea03685).
Follow this procedure to drop back to the VPN Client version 3.6 from version 4.0.
Step 2 After rebooting, search for csgina.dll. This file is found in the System32 directory.
Step 3 Rename csgina.dll to something like csgina.old.
Step 4 Install the VPN Client version 3.6.
To use the VPN Client behind a Linsksys 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 Linsksys 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 (CSCdz52156).
Caveats describe unexpected behavior or defects in Cisco software releases. The following lists are sorted by platform and then by identifier number for the specified platform.
|
Note If you have an account with CCO, you can use Bug Navigator II to find caveats of any severity for any release. To reach Bug Navigator II on CCO, choose Software & Support: Online Technical Support: Software Bug Toolkit or navigate to http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl . |
This section lists open caveats for the VPN Client running on a Windows platform.
The VPN Client may swap Primary and Secondary WINS received from the Concentrator. In a few cases, the VPN Client receives a Primary and a Secondary WINS server from the Concentrator but swaps them when they are added to the IP Configuration. If this happens, it may cause browsing problems if the Secondary WINS server is not as populated as the Primary. Disconnecting and reconnecting may fix the problem.
When the VPN Client is installed on a Windows 2000 PC with the Efficient Networks NTS EnterNet 300 PPPoE version 1.41 or 1.5c, the following message appears:
"EnterNet could not find the (adapter) for complete pc management NIC (adapter). But it did locate the (adapter) for complete pc management NIC (adapter) - Deterministic Network Enhancer Miniport adapter through which your network server is reachable. Do you want to switch to this adapter?"
Answer Yes every time this question appears. The installation then continues normally.
A similar message appears on Windows NT 4.0. The message is:
"EnterNet could not find the (adapter). But it did locate the (adapter) through which your network server is reachable. Do you want to switch? Yes No"
Answer Yes to this question. The installation then continues normally.
If the VPN Client is uninstalled, the next time the NTS EnterNet 300 PPPoE version 1.41 is used the message, "EnterNet could not find the (adapter). But it did locate the (adapter) through which your network server is reachable. Do you want to switch? Yes No"
Answer Yes to this question. The installation then continues normally.
Problems have occurred when an ISA legacy NIC card (IBM Etherjet 10MB) is used in a PC with PnP OS enabled. The WINS servers did not function correctly when a VPN Client connection was made. This could be an issue with other legacy NIC cards as well.
The end results are that the WINS servers sent from the Secure Gateway cannot be viewed in the Network configuration, and problems with browsing/logon over the VPN connection may occur.
Disable PnP OS in the PC's BIOS or statically configure the WINS servers.
When you connect the VPN Client to a VPN 3000 Concentrator that issues two DNS servers, both appear under ipconfig /all, but only one appears under the Network settings TCP/IP Properties. DNS server appears to be missing under TCP/IP Properties (Advanced button, DNS TAB). We do not know whether this causes any problems.
On Windows 98, Windows ME, and Windows NT machines, you may see a problem with FTP file transfers over a long period of time (hours) while connected with the VPN Client. The symptom is that the FTP session never starts (no response to the 'open' command) and the Client Log Viewer shows the following events:
74 22:31:08.704 02/08/01 Sev=Warning/2 IPSEC/0xE370000C
Failed to acquire a TCP control resource, the queue is empty.
75 22:31:08.704 02/08/01 Sev=Warning/2 IPSEC/0xA370001A
VRS processing failed, discarding packet
Other applications like PING and HTTP should work fine, but for FTP to work again, you must disconnect and reconnect the VPN Client.
This problem does not occur on Windows 2000 and Windows NT machines.
You might see the following problem on systems running Windows NT and Windows 2000 when you are using the Start Before Logon feature of the VPN Client with third-party dialer. If the third-party dialer does not get set to the foreground when launched, add the following parameter to the vpnclient.ini file in the VPN Client directory (\Program Files\Cisco Systems\VPN Client\Profiles):
The value is the time in milliseconds that the VPN Client waits for the third party dialer to load before attempting to place it in the foreground. The default time is 1000 milliseconds.
For problem dialers/applications, try 2500 milliseconds or greater.
SCEP enrollment might fail to complete successfully after the PKI administrator has granted your request.
If this happens, delete your failed request and submit a new one.
To delete the request, click the Certificate tab, select the failed request, and click Delete on the toolbar. Alternatively, open the Certificates menu and select Delete.
The following issue can exist when using the VPN Client Start Before Logon feature with Entrust SignOn. Entrust SignOn is an add-on to the Entrust Entelligence client that allows logging into the Entrust profile and the NT domain from a single login.
The Entrust SignOn GINA dll does not support chaining to other GINA dll files. To make the Entrust SignOn product and the VPN Client with Start Before Logon function properly together, install the VPN Client after Entrust SignOn. The VPN Client replaces the Entrust GINA (etabcgin.dll) with its own (csgina.dll).
VPN Client and Entrust Entelligence - VPN Connection timeout.
In version 3.1, the potential exists for the VPN Client Connection Manager and the VPN dialer to get out of sync with each other. This occurs only after a VPN Client upgrade on the first time the VPN Client accesses a given Entrust profile. The following sequence outlines how a user could get the connection into this state:
Step 2 Entrust prompts for password and security hash check. The user clicks Yes.
Step 3 Entrust prompts for password for cvpnd.exe security access.
If the user waits here or walks away from PC, the VPN Connection times out in 3 minutes.
Step 4 The user returns and enters the Entrust password, then clicks Yes to the security hash check question.
Step 5 The VPN connection completes, and data can be passed. The VPN dialer appears as not connected.
Step 6 Clicking Connect returns "A connection already exists". The user clicks Cancel, and the dialer appears connected in the system tray.
The VPN connection can be used as a normal connection.
This issue occurs on a Windows NT PC that is running ZoneAlarm or Sygate Personal Firewall, if the VPN Client is set to Start Before Logon and an upgrade to the VPN Client is implemented. Do not attempt a connection before the logon when you reboot, because both firewalls do not automatically give the VPN Client permission to access the Internet. Both firewalls see the upgrade as a new application attempting to access the Internet, and it requires user permission through its pop-up menus. The user must logon to the Windows NT PC using cached credentials, then launch a VPN connection. The firewall then asks permission to allow the VPN Client to connect. Answer yes to each connection. After that, Start Before Logon works fine.
The message, "The necessary VPN sub-system is not available. You will not be able to make a connection to the remote IPSec server." might appear on a PC when Start Before Logon is enabled on the Client and ZoneAlarm is also running. The message appears when the ctrl+alt+del key combination is pressed. This has happened because the Cisco Systems VPN Service has terminated unexpectedly.
Logon to the PC with cached credentials, open "Services" in control panel and start the VPN service. A connection to the VPN Concentrator will be possible once the service has started.
When connecting to a VPN 3000 Concentrator over PPPoE using the EnterNet 300 client software from Efficient Networks, Inc., if a firewall is required by the VPN Concentrator, the following message might appear:
"The Client did not match any of the Concentrator's firewall configurations..."
If this message appears, click OK and then click Connect. The connection to the VPN Concentrator then proceeds successfully.
If you make connections from the command line interface, the following problem can occur. When a firewall is required to connect and the firewall fails or is shut down, you do not see any message giving the reason for the lost connection.
If you use the VPN Client with a Digital Certificate and your Client sits behind a Cable/DSL router or some other NAT device, you might not be able to connect to your VPN Gateway device (that is, the VPN 3000 Concentrator). The problem is not with the VPN Client or the Gateway; it is with the Cable/DSL router. When the VPN Client uses a Digital Certificate, it sends the Certificate to the VPN Gateway. Most of the time, the packet with the Certificate is too big for a standard Ethernet frame (1500), so it is fragmented. Many Cable/DSL routers do not transmit fragmented packets, so the connection negotiation fails (IKE negotiation).
This problem might not occur if the Digital Certificate you are using is small enough, but this is only in rare cases. This fragmentation problem happens with the D-Link DI-704 and many other Cable/DSL routers on the market. We have been in contact with a few of these vendors to try to resolve the issue.
Testing with the VPN Client Release 3.1 indicates that VPN Client connections using Digital Certificates can be made using the following Cable/DSL routers with the following firmware:
Linksys BEFSRxx v1.39 or v1.40.1
Others like 3COM 3C510, and D-Link DI-704 either had updated firmware that was tested and failed, or had Beta firmware that was NOT tested because the firmware notes did not indicate a fix specifically for fragmentation.
The following message might appear when a connection using the EnterNet 300 version 1.4 PPPoE software and transferring via FTP:
93 09:42:06.020 08/02/01 Sev=Warning/2 IPSEC/0xE3700002
Function CniInjectSend() failed with an error code of 0xe4510000 (IPSecDrvCB:517)
This does not interfere with your connection. You can ignore this message.
When Zone Alarm's Internet setting is set to high and the VPN Concentrator sends a CPP firewall policy that allows inbound traffic on a specific port, the CPP rule takes precedence over the Zone Alarm rule allowing the specified port to be open.
Importing a PKCS12 (*.p12 or *.pfx) certificate using the Certificate Manager that has not been password protected will fail with the following error:
"Please make sure your import password and your certificate protection password (if for file based enrollment) are correct and try again."
Get a *.p12 certificate that has been password protected.
Attempting to install/uninstall Gemplus Workstation version 2.x or earlier while the Cisco VPN Client and its GINA (csgina.dll) is installed will cause the following error, and Gemplus will not install/uninstall:
"A 3rd party GINA has been detected on your system. Please uninstall it before installing this product."
When a CPP Firewall policy is in place that drops all inbound and outbound traffic and no WINS address is sent to the VPN Client from the 3000 series Concentrator, Start Before Logon fails. If a WINS address is in place, Start Before Logon works fine. Also, if a WINS address is sent and the CPP rule drops all inbound traffic, but allows all outbound traffic, Start Before Logon works fine.
Using the Aladdin "R2" model etoken, certain functions can be performed using the certificate even after the R2 token has been detached from the system (USB port). The VPN Client, for instance, can perform an IKE rekey without the token attached to the system. The reason for this is the design of the "R2" etoken: it does not contain the RSA key functions needed and must upload the private key to the system for these functions.
In contrast, the Aladdin "PRO" etoken must be connected to the USB port during an IKE rekey, otherwise the VPN Client connection terminates. This is Aladdin's problem; it is not a VPN Client problem.
Using the Solaris VPN Client, some applications are unable to operate properly. A possible indicator of the problem is that a large ping is unable to pass through the VPN Tunnel.
An MTU issue currently exists with the Solaris VPN Client that causes fragmentation errors that might affect applications passing traffic through the VPN Tunnel.
To identify whether the VPN Client is properly fragmenting packets, use the following commands:
ping -n <known good ping target address>
ping -n -s <known good ping target address> 2500
The first command ensures that the target is reachable, and the second determines whether fragmentation is an issue
Step 2 2)IP Compression may be set to "LZS" in the VPN Group on the Concentrator. This decreases the size of the encrypted packet and may allow the smaller packet to avoid fragmentation. If NAT is being used, switching the NAT method of the client from cTCP (TunnelingMode=1) to UDP (TunnelingMode=0) may also reduce the size of the packet.
When you have multiple VPN Client connections behind Linksys Cable/DSL router, the following problem can occur. Due to a Linksys problem with firmware versions 1.39 and 1.40.1, making multiple VPN Client connections enabling the feature "Allow IPSec over UDP" (transparent tunneling) may cause data transfer problems.
Allow IPSec over UDP is a VPN Client feature that allows ESP packets to be encapsulated in UDP packets so they traverse firewall and NAT/PAT devices. Some or all of the clients may not be able to send data. This is due to a Linksys port mapping problem, that Linksys has been notified of.
If possible, do not use the "Allow IPSec over UDP" (transparent tunneling) feature when you have multiple VPN Client connections behind Linksys Cable/DSL router.
The following Microsoft Outlook error might occur when the VPN Client connects or disconnects. This occurs when Microsoft Outlook is installed but not configured.
To set Microsoft Outlook as the default mail client, right-click on the Outlook icon, go to Properties, and configure it to use Microsoft Exchange or Internet Mail.
The make module process fails during installation of the VPN Client for Linux.
The module build process must use the same configuration information as your running kernel. To work around this problem, do one of the following:
Getting Entrust certificates using SCEP does not get the Root CA certificate. The Entrust CA does not send the whole certificate chain when enrolling with SCEP. Therefore, making a VPN Client connection might require the manual installation of the Root certificate before or after SCEP enrollment. Without the existence of the Root CA certificate, the VPN Client fails to validate the certificate and fails with the following VPN Client event/error messages:
"Get certificate validity failed"
"System Error: Unable to perform validation of certificate <certificate_name>."
If an attempt to load the VPN Client is made before the Clients Service loads, the following error occurs: "The necessary VPN sub-system is not available. You will not be able to make a connection to the remote IPSec server."
Wait until the Service has loaded, then start the VPN Client.
A customer had problems enrolling the Mac OS version of the VPN Client. Following some troublesome attempts at debugging the enrollment of the MacOS VPN Client with a Baltimore CA, it was felt that the Documentation should be improved and the Certificate Manager enhanced.
It seems that the critical thing as far as Baltimore is concerned is to put either or both of the challenge phrase (-chall) and the host's FQDN (-dn) in the request. This appears to be similar for the successful SCEP enrolment in a Verisign Onsite PKI. Perhaps there's a case for tweaking the interface a bit, or at least making some notes in the manual!
Just doing cisco_cert_mgr -U -op enroll only asks for a Common Name, which is not enough. The request that succeeded on two separate Baltimore installations, one of which had an expired RA certificate, was as follows (switches only shown for brevity):
cisco_cert_mgr -U -op enroll -cn -ou -o -c -caurl -cadn -chall -dn
The ou is required for connecting to a Cisco 3030 VPN Concentrator and is the group name. On almost every attempt, the certificate manager dies after starting to poll the CA, with an error in the log: "Could not get data portion of HTTP request".
If this happens, it is possible to resume the enrollment with cisco_cert_mgr -E -op enroll_resume. The last attempt didn't fail at all though, and the certificate manager kept running until the request was approved, which is how it should behave.
If IOS sends a split tunnel attribute that is host-based (255.255.255.255 mask), the VPN Client uses the host in a QM, but it passes the IPV4_ADDR_SUBNET in the ID payload.
IOS expects IPV4_ADDR, as this is a host ID. This causes connectivity issues.
If the computer is powered off or loses power during an MSI installation of the VPN Client, the VPN Client may not be registered in Control Panel, and the following may occur when attempting to reinstall:
After clearing the last message box, restart MSI installation. It should successfully install the VPN Client.
The Linux, Solaris, and Mac OS X platforms never seem to time out when left idle with the VPN Client connected, even after they've lost their connection to the concentrator.
The Dead Peer Detection (DPD) implemented on the VPN Client is triggered only if traffic is attempted through the tunnel. Once the client realizes it received no response to this traffic, it enters its worry loop for DPD. An idle platform that does not attempt to use the tunnel cannot detect the loss of a connection, even if the concentrator has been power cycled days before.
Checking the tunnel statistics does NOT alert the user to a lost connection.
Attempt to pass traffic through the tunnel. Once traffic has been generated, the VPN Client connection can determine within 5 - 12 minutes whether the connection is lost.
It might be easier to disconnect and reconnect a connection prior to use if it has remained idle for a prolonged period of time or if known connectivity issues are frequently seen with the user's connection.
The VPN Client's xauth dialog always stays in the foreground so it doesn't get "lost" (on XP it goes to the background and then jumps forward within seconds). The xauth dialog does not have focus, however, and it can be difficult to enter the username/password without first clicking on it with the mouse. This was observed on Windows 2000 and Windows XP; we have not checked Windows 98.
Installing the VPN Client using the Microsoft Windows Installer (MSI) displays "Time Remaining" for the installation. This time is not very accurate and should be ignored.
Microsoft article Q234859 states that for the resiliency feature to work on Windows 4.0, IE 4.01 sp1 and shell32.dll version 4.72.3110.0 or greater must be installed on the computer.
The Microsoft Installer (MSI) resiliency (self healing) feature does not restore all files that are installed with the VPN Client. The files that will be restored are files that are associated with the shortcuts under Start | Program Files | Cisco Systems VPN Client.
An issue can occur when using the Release 4.0VPN Client with Start Before Logon (SBL), after enabling SBL. The first time you log out of Windows, the VPN Client does not load after you press the CTRL+ALT+DEL key combination at the Windows logon prompt.
Reboot the PC after enabling Start Before Logon; after a subsequent logout, the VPN Client should operate properly.
The following error occurs after the resiliency feature has reinstalled a missing file on Windows NT 4.0:
c:\winnt\profiles\all users\start menu\programs\cisco systems vpnclient\xxx.lnk
The Windows installer failed to install the program associated with this file.
Please contact your system administrator.
xxx.lnk is whatever file is being restored.
When you click OK, the PC reboots and the file is restored. The resiliency feature is working, but the error should not appear.
When attempting to launch the dialer when the dialer is already running on the logon desktop (due to SBL or SBL and AI), the following error occurs instead of the VPN Client dialer loading.
"Single dialer instance event creation failed with error 5."
This is most likely to happen when Start Before Logon and Auto Initiate are being used on a Windows NT/2000/XP system.
This is due to the fact that the VPN Client dialer is already running on the "logon desktop". Most likely during Windows logon the dialer launched and posted an error, the Windows logon was completed and the error was never closed. To work around this error, do the following:
Step 2 Look for and close any VPN Client error dialogs.
Step 3 Press ESC to return to the normal Windows desktop; the VPN Client should load normally.
Connecting the Cisco VPN Client (versions 3.5 and later) to an IOS VPN device running 12.2(8)T using digital certificates might disconnect during a rekey. The connection could disconnect sooner if dead peer detection (DPD) is being used. The problem is under investigation.
Keeping the rekey times as high as possible will help avoid the problem.
The other alternative is to use the VPN Client with preshared keys, which does not have the problem.
During installation of the VPN Client on a PC that already has the Enternet v.1.5c or v. 1.5c SP2, the following error might appear:
"SVCHOST.EXE has generated errors and will be closed by Windows."
If this message appears, click OK, then reboot the PC when the VPN Client prompts for the reboot. After this, The message does not reappear and all connections work fine.
While using the Solaris VPN Client and its pppd 4.0 driver over PPPoE, the VPN Client can make a connection, but not pass any traffic.
Due to an initialization issue in the VPN Client code, the Solaris VPN Client cannot pass traffic if it is first used with a PPPoE connection exclusively. It must first have attempted an hme connection (even a failed one) to properly ready itself for the PPPoE connection.
Remove the IP Address of the hme0 interface before attempting a connection using the ifconfig hme0 0.0.0.0 command.
As an alternative solution, after rebooting a Solaris workstation, attempt a VPN Client connection while the PPPoE link is down. The user may have to assign a bogus address to the hme interface if it does not already have some address. The VPN Client connection attempt need not be able to make a successful connection. Once the connection has timed out, restore the PPPoE connection, then the VPN Client connection should be able to pass traffic normally until the device is once again rebooted.
InstallShield's "Tuner" application produces warnings and errors when validating the Cisco MSI installation package.
If a you install the Cisco VPN client and you are not a local administrator, but you are a domain user that has been added to the local administrator group, the install completes successfully, but you may get the error "VPN subsystem unavailable" when trying to use the VPN Client, and you will be unable to use the VPN Client.
If the user installing the VPN Client is a local administrator, then the error does not occur when running the VPN Client.
Log in as a local administrator when installing the VPN client.
On a Windows 98 PC that has the Sygate Personal Firewall, the following message may appear in the VPN Client log file:
"Packet size greater than ip header"
This message does not interfere with the VPN Client's ability to pass data and can be ignored.
A user with the VPN Client cannot establish an IPSec tunnel to a VPN Concentrator running over an Internet satellite connection.
There are three observed results:
This problem occurs only if IPSec over TCP is used.
If using the VPN Client feature Start Before Logon and the Sygate Personal Firewall version 5.0 build 1175 or later, the following Sygate configuration may be required in order to successfully log in to the domain after making a connection.
Step 2 Turn off netBIOS protection in the Tools | Options menu on the Security tab.
Step 3 Disable Driver Level Protection in the Tools | Options menu on the Security tab.
Step 4 Allow the Cisco VPN Client to use the network in the Application dialog.
The following error might occur on Windows 98 when making many VPN connections without closing the VPN Client between connections:
VPNGUI caused an invalid page fault in module MSVCRT.DLL at 0167:78002f52.
To avoid this error, exit the VPN Client after disconnecting.
When installing the Release 4.0 VPN Client on Windows 2000 or Windows XP, a driver signing warning appears, asking whether or not to continue the installation.
The Release 4.0 VPN Client, when installed on Windows 2000 or Windows XP has a new Virtual Adapter feature. The VPN Client installs a Virtual Adapter driver that is not yet signed, so when installing the VPN Client, a warning may appear.
If during client installation a message pops up, click "Yes" to continue on Windows 2000, or "Continue Anyway" on Windows XP.
The VPN Client does not save the location and size of the external Log Window, so you must resize and move the Log Window every time you open it.
The VPN Client on Windows XP using native XP PPPoE client fails to connect when using IPSec/TCP.
Make sure that the Windows XP Internet Connection Firewall is disabled for the PPPoE connection. This feature defaults to enabled when the connection entry is created. To disable it do the following.
Step 2 Right click on the PPPoE connection entry (may be called "Broadband") and select "Properties".
Step 3 Change to the Advanced Tab and uncheck the "Internet Connection Firewall" option.
Some AOL applications may not be usable while a 4.0 VPN Client connection is active. These include the AOL integrated web browser and some internal links. Using external web browsers and other applications should work over the VPN. These issues were seen most recently using AOL version 7.0 and 8.0.
To connect to a VPN 3000 Concentrator requiring Sygate Personal Firewall, Sygate Personal Firewall Pro, using Are You There (AYT), the version of the firewall must be 5.0, build 1175 or later. The VPN Client might not detect an earlier version of the Sygate Personal Firewall and therefore, a connection will not be allowed.
After upgrading, the VPN Client is unable to connect to the VPN 3000 Concentrator. The ability for the VPN Client to negotiate an AES-192 IKE Proposal has been removed. This change affects all VPN Client versions greater than 3.7.2.
Reconfigure the VPN Concentrator so that it does not require an AES-192 IKE Proposal for VPN Client connections.
The Equant remote access dialer does not automatically connect the Release 4.0 VPN Client, as it could when using the Release 3.x VPN Client. If you have the Equant dialer configured to establish your VPN connection, the VPN Client appears, but you must manually click Connect to connect.
Disable the VPN Client log, stops logging to the file and screen. Re-enabling logging first clears the screen and reloads all the text from the file back to the screen. Log output should start to appear on the screen and file.
With the version 4.0 Cisco VPN Client installed, you are unable to browse the web, and when you try, you are redirected to the following URL: http://lockup.zonelabs.com/8083.html. The web browser displays a message like "Notice from Zone Labs Internet Security" and directions about reinstalling Zone Alarm personal firewall.
Cisco VPN client version 4.0 includes firewall functionality from Zone Labs Inc. It is possible that a failed Zone Labs uninstall left an incorrect value in the systems registry and must be changed. To resolve the problem follow these steps.
 |
Caution This procedure contains information about editing the registry. Before you edit the registry, make sure you understand how to restore it if a problem occurs. |
Step 2 At the advanced options screen select "Safe Mode" as a startup method.
Step 3 If prompted, login to the PC once it is booted (you must have Administrator rights to login in Safe Mode).
Step 4 Click Start > Run and type "regedit" in the Open: box (without the quotes) and click OK. This launches the Windows registry editor.
Step 5 In the registry editor, browse to the following path: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\vsdatant and select the Start parameter in the right pane.
Step 6 Right-click Start and select Modify. In the Value data: field enter the number 3.
Step 7 Click OK and exit the registry editor.
Step 8 Restart the computer and boot normally; the problem should be resolved.
The 4.0 VPN Client (on Windows 2000 or Windows XP) connects but is unable to pass data over the VPN tunnel. Viewing the routing table using "route print" at a command prompt shows the default gateway has been modified incorrectly as in the example below.
0.0.0.0 255.255.255.255 n.n.n.n n.n.n.n 1
Where n.n.n.n is the IP address assigned to the VPN.
This is due to a misconfiguration on the VPN3000 at the central site. Make sure that the Group | Client Config settings for Split Tunneling Policy are correct. If the group is set to "Only tunnel networks in the list" and the Split Tunneling Network List is the predefined "VPN CLient Local LAN" list this problem will occur.
If split tunneling is the desired result, change the Split Tunneling Network List to an appropriate list, otherwise make sure that the Split Tunneling Policy is set to "Tunnel Everything" and check "Allow the networks in the list to bypass the tunnel". This allows for proper Local LAN functionality.
The following configuration will allow inbound ICMP packets (pings) when the default firewall rule for the Centralized Protection Policy (CPP) is pushed to the VPN Client.
The parameter, "StatefulFirewallAllowICMP=1" should only be used if it is desired that ICMP traffic be allowed to pass through the firewall.
When the VPN Client is installed and Start before Logon is configured, logging into an Active Directory Domain might take a long time, with or without a VPN connection.
This issue occurs under the following conditions:
This problem occurs because of a fix that was added for CSCdu20804. This fix adds the following parameter to the registry every time Start before Logon is enabled:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\NetLogon\Parameters
Removing "ExpectedDialupDelay" from the registry (then rebooting) should fix the problem with slow logons to an Active Directory Domain.
|
Caution This procedure contains information about editing the registry. Before you edit the registry, make sure you understand how to restore it if a problem occurs. |
|
Note If you disable, then re-enable Start before Logon, this entry is added again and must be removed. |
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.
An exception to this, however, occurs if the VPN Client is installed before Zone Alarm. Then the VPN Client's service must be restarted by rebooting the PC or stopping and restarting the service through Control Panel (on Windows NT-based PCs).
If the Digital Certificate you are using has expired, the Windows VPN Client GUI does not popup with an error message indicating it has expir