I checked the SSL encryption used by the firewall.Īccept connections using SSLv2, SSLv3 or TLSv1 and negotiate to SSLv3 or TLSv1 I activated the VPN-3DES-AES feature, but still wasn’t able to connect to the firewall with the web interface. The upgrade license for this feature is available for free at. The next step was the enable the VPN-3DES-AES ciphers. I noticed that VPN-3DES-AES was disabled. I started looking at the supported encryption algorithms within the firewall with a show version. In Google Chrome I receive the following error:Įrror 113 (net::ERR_SSL_VERSION_OR_CIPHER_MISMATCH): Unknown error.Īnd of course Internet Explorer didn’t gave any usable information. While working with Mozilla I received the following error:Ĭannot communicate securely with peer: no common encryption algorithm(s). All these options didn’t help, but the strange thing was that the web interface was working remotely. While troubleshooting I first tried the basic settings, like management access-list, regenerate crypto keys and change the management port. I was able to connect to the firewall with my locally installed ASDM client, but I couldn’t access the web interface either. The customer didn’t install ASDM locally, but always starts the Java-based version.Īfter upgrading the Cisco ASA to software version 8.2(1) and a reboot, the client wasn’t able to connect to the web interface anymore. I had to troubleshoot a Cisco ASA today, where the client wasn’t able to connect to the management web interface anymore via https.
0 kommentar(er)
