Issues with CSD Versions 3.5.x and Java 7 The hostscan issue has been resolved by Cisco bug ID CSCuc48299, "IE with Java 7 crashes on HostScan Weblaunch." Hostscan is susceptible to crashes similar to those described previously for An圜onnect in Windows (Cisco bug ID CSCuc55720). Use DART in order to collect the CSD/Hostscan logs.Turn up CSD logging to debugging on the Cisco Adaptive Security Device Manager (ASDM).Navigate to ASDM > Configuration > Remote Access VPN > Secure Desktop Manager > Global Settings.In order to obtain the DART logs, the CSD logging level must be turned to debugging on the ASA: Note: This procedure has been tested with Java 7 updates 9, 10, and 11.įor CSD/Hostscan-related issues, collect the DART logs as well as the Java console logs. Log in with An圜onnect, and the Java apps should work.
Tests with An圜onnect 3.1 (with the WebLaunch / Safari / Mac 10.7.4 / Java 7.10 configuration) show no errors. This issue was fixed by Cisco bug ID CSCub46241, "An圜onnect weblaunch fails from Internet Explorer with Java 7." However, Oracle changed that value as described in JDK7: Java vendor property changes.
Issues with An圜onnect WebLaunch After Java 7 UpgradeĬisco JavaScript code previously looked for Sun as the value for the Java vendor.
How to force java to use ipv4 instead ipv6?Ī third solution is to disable IPv6 completely on Windows machines edit this registry entry: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\TCPIP6\Parametersįor additional information, see How to disable IP version 6 or its specific components in Windows.How to set 4Stack=true in the java code?.Set the environment variables _JPI_VM_OPTIONS and _JAVA_OPTIONS in order to include the system property:.Add code for the system property from the command line:.Add code for the system property to the Java code (for Java applications written by the customer):.Set the system property '4Stack' to 'true' as shown in these examples: One solution for this issue is to disable IPv6 (if it is not in use) on the Ethernet adapter and the An圜onnect Virtual Adapter (VA):Ī second solution is to configure Java to prefer IPv4 over IPv6.
These log entries indicate that the client/application makes IPv6 calls. If An圜onnect does not connect even after you upgrade the Java Runtime Environment (JRE) to Java 7, or if a Java application is unable to connect over the VPN tunnel, review the Java console logs and look for these messages: : Permission denied: connectĪt (Native Method)Īt (Unknown Source) For further information, see Cisco bug ID CSCue48916, "Java App(s) Break when using An圜onnect 5 or 6 & Java v7." You might encounter issues when you use some versions of An圜onnect and Java 7 with Java apps.
If Java is enabled properly, review the Java console logs in order to analyze the problem. Run the Java Verifier in order to check if Java is supported on the browsers in use. If you face issues with Java 7, ensure that you upgrade the An圜onnect client version to the latest client version or to at least the 3.1 maintenance release 3 version available on Cisco Connection Online (CCO). Note: Cisco bug IDs marked as investigative are not restricted to the symptoms described. This document describes how to troubleshoot issues with Java 7 on Cisco An圜onnect Secure Mobility Client, Cisco Secure Desktop (CSD)/Cisco Hostscan, and clientless SSL VPN (WebVPN).