Looks like I got it working… partially. I renamed the machine just in case there was an issue with certificates or something. No change in behavior.
Manually removed all things Cisco from the drive and registry, rebooted and reinstalled the client, and rebooted again. If I connect to an available unsecured wireless network and then make the VPN connection, I can map internal resources (but not ping). If I connect to to an available WPA2 wireless network I can make the VPN connection but cannot connect to internal resources. In both cases the default gateway on the Cisco virtual adapter is blank. However, on my personal machine that gateway address is 10.0.0.1. On my home network (WPA2) I connected to the VPN and mapped drives no problem. Apparently there's an issue with the WPA2 network available from my office, but I can't imagine what it is since I can connect and map drives fine using other machines over that wireless network. Still a stumper... Roger Wright ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
