Orginally Posted by: Bret Talbot Is anyone aware of the enormous problem that x64 architecture and MS/Cisco is creating for Cisco VPN clients? More importantly, does anyone know of a solution? The VPN implementation that is now used by Microsoft on all it's x64 platforms makes it impossible to use the Cisco VPN client, and if using the AnyConnect client, you can't use IPSec. An engineer at Cisco came up with a Linux solution on his own time, but apparently the way that the MS implementation of VPN on x64 platforms changes the way that the information regarding the connections are stored. Is there a solution for x64 MS and Cisco VPN client out there? I can't believe two such mammoth companies can't get their *** together and not have the VPN user community suffer to this degree, especially given MS's intent on forcing everyone to upgrade to Vista.

Hi, Please refer to the following KB article: 929490Windows Vista-compatible third-party virtual private network (VPN) client scheduleshttp://support.microsoft.com/default.aspx?scid=kb;EN-US;929490 Hope the information is helpful.

Well for x64 about 90% of the status or dates are:"Unknown", "Unknown", "Application under development. No public schedule is available", "Unknown", "Not planned. Upgrade to Cisco AnyConnect VPN Client. --> means no IPSec for x64, AnyConnect is just SSL-VPN", "Unknown", "Unknown", "Unknown"That's not very enlightening and doesn't help people with apps that need the 64 bit and VPN that don't work with it :-(.