08-13-2007 12:30 AM - edited 03-09-2019 06:34 PM
the release notes for vpn client 5 states that one of the workarounds for CSCsi26229, CSCsf07334 is:
"Clear a custom DLL check looking for the Microsoft Firewall DLLS."
how exactly would i do this. our vpn uses the vpn 3000 concentrator with ACS 4.0. is this implemented thro Posture Validation or a script running on the client. can someone point me in the right direction?
thanks
andy
08-15-2007 06:51 AM
I'm wanting to know the same thing, because we have the same problem.
02-21-2008 03:59 AM
We've using the workaround âUse an alternative Firewall that is supported on Vista and by the VPN applianceâ to reolve the Cisco VPN Client caveat CSCsi26229, CSCsf07334 (integrated firewall not installed with Vista). We're using Zone Alarm and Zone Alarm Pro and we've configured 2 tunnel groups with the following attributes:
Cisco VPN 3000/ASA/PIX v7.x+ RADIUS Attributes
[3076\045] Required-Client-Firewall-Vendor-Code (0..65535) 2
[3076\046] Required-Client-Firewall-Product-Code 1
[3076\047] Required-Client-Firewall-Description Zone Alarm
[3076\045] Required-Client-Firewall-Vendor-Code (0..65535) 2
[3076\046] Required-Client-Firewall-Product-Code 2
[3076\047] Required-Client-Firewall-Description Zone Alarm Pro
My question is does anyone know when this caveat will be resolved by Cisco? Is there anything in the pipeline or any plans to resolve it at all?
Thanks
Andy
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: