Could it be that the router at home is using the same ip address as the VPN at work?
I ran into strange problem when using 192.168.0.X at home and work. Changed one to 192.168.100.x and no problems. From: Roger Wright [mailto:[email protected]] Sent: Friday, September 04, 2009 1:59 PM To: NT System Admin Issues Subject: Re: Cisco VPN Client Weirdness The most recent analysis shows that the issue only shows up when making a VPN connection through a Linksys WRT54G2 router. If I remove the router from the path I'm able to map drives just fine. I have an older WRT54G at home - no issues. Belkin or DLink router - fine. Gee... you'd think a Linksys by Cisco router would be fully compatible with the Cisco VPN client but apparently not! Roger Wright ___ On Thu, Sep 3, 2009 at 9:16 PM, Roger Wright <[email protected]> wrote: 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/> ~
