Bring up the ASA GUI and go into Configuration and into sub-tab Device Setup Go over to Routing and down to Static Routes. Add a route to your inside interface ip address: 0.0.0.0 netmask: 0.0.0.0 Gateway IP: (the gateway address of your inside interface) Under options select "Tunneled, default tunnel gateway for VPN traffic) Click apply, then save the config. Disconnect and reconnect your vpn. PS: Also upgrade your ASA code. Version 7.x is horrible. Don't even bother trying to work with the ASA until you move into version 8.x
... View more
My Email From TAC.. >> Hi Michael, No problem that is ok, I completely understand you, but, unfortunately I can not help you with this information, I did some research and I found that it is not a plan to support Windows Vista 64 bits with the original ipsec vpn client, but I do not have more information, and I do not have a way to get it, the TAC is just "break and fix", so I involved mi manager to canalize you with the correct person to provide you this information, and he said that the good one must be your account manager =). I hope this can help you. I will be waiting for your response back, and please let me know if there is something else that I could do for you related to the same issue, as a TAC engineer. Best regards... << Unfortunately I wish my Cisco rep had told me they did not support IPSEC Vista 64 when I purchased my gateways. At the time of purchase the ASA5540 listed Windows IPSEC VPN client support but failed to mention they do not plan to support Vista 64. (Thanks Cisco) They are forcing you to move to the AnyConnect client for an additional SSL License cost. I wonder if they are slowly killing off IPSEC clients or just trying to push their SSL solution into companies so they can compete with other SSL VPN Vendors (Ex: Netilla) A VPN client development roadmap would be nice from Cisco but TAC was unable to provide me one.
... View more