THIS IS UNFINISHED
UNDER CONSTRUCTION

I got the solution here:
http://geekswithblogs.net/evjen/archive/2007/01/01/102429.aspx
(just search for the post that mentions “192.168.0.1″ in it).

This drove me crazy.

Cisco must really hate their customers. Windows Vista came out in 2006, and we’re heading into 2009 and they still don’t fully support Windows Vista.

Stuff I used:

VMware Player, free and works with Vista x64
http://www.vmware.com/products/player/

VMX Builder, free tool to create VMware images. Works in Vista x64.
http://petruska.stardock.net/Software/VMware.html

Daemon Tools Lite. Free CD Image mounting tool. Free and works in Vista x64. Make sure you don’t install the adware stuff during its installation unless you really want it.
http://www.daemon-tools.cc/

Here is my crummy guide. I will try to update it later. It’s like 5AM now, and I’ve spent too much time with this.

Create a VM for Windows XP (or Windows 2000) as the guest. I recommend giving them 256 Megs RAM.
Set it to have TWO network adapters. One “Bridged” one “Host Only”.

If you have it, install VMware Tools for best performance with the VM (VMware Tools are included in the free VMware Server download, but not with VMware Player).

Once the VM/Guest OS is running, verify your network and Internet connection is working and then install the Cisco VPN software. Reboot the guest after install. Once you are back in Windows, make your connection with the Cisco VPN software and verify that works.

In the HOST OS (Windows Vista x64):

You will have two VMware network adapters installed from VMware Player:
Mine were named something like this:

“VMware Network Adapter VMnet1″
“VMware Network Adapter VMnet8″

To shorten their names and make them easier to recognize, I renamed them to this:

“VMware VMnet1″
“VMware VMnet2″

Go to their properties:

I changed their IPs:

VMnet1: 192.168.10.1 / 255.255.255.0
VMnet2: 192.168.20.1 / 255.255.255.0

In the GUEST OS (Windows XP or 2000)

You may have network connections like these:
“Local Area Connection” (for the bridged VMnet)
“Local Area Connection 2″ (for the host only VMnet)
“Local Area Connection 3″ (from the cisco vpn)

I found it was easier to rename them to something like this:
“LAN1 (Bridged)”
“LAN2 (Host)”
“Cisco VPN Connection”

* Connect the Cisco VPN software and make sure your VPN connection works! *

“LAN1″ is what the guest OS connects to the network/internet through.

“LAN2″ is what we want to change:

Give it an IP on the same network as VMnet2, such as: 192.168.20.2 / 255.255.255.0
(don’t set Gateway or DNS).

Now go to Cisco VPN Connection’s Properties, click Advanced, and then share it, and pick the “LAN2 (Host)” connection.

Windows will warn you that it is changing the IPs of some adapters to 192.168.0.1. Dismiss that dialog.

Go back to “LAN2″ and change it from the 192.168.0.1 Windows just set it to back to 192.168.20.2.

If the Cisco VPN connection is established, disconnect and reconnect.

In the HOST OS (Vista)

Go to the properties of your main network connection,

Manually set a static IP, Subnet, and Gateway

For DNS1, put in 192.168.20.2 (the GUEST LAN2)
For DNS2, put in your normal one.

Disable and re-enable the VMnet2 adapter.
Once re-enabled, see if you can PING the host-only adapter LAN2 in the Guest (192.168.20.2) from the Host.

If you are able to ping it, then you are connected to the guest properly.

Now you have to add a route (tell the Host to look to the Guest for connection).

I used this command to connect to MY network:

route -p add 10.10.1.0 mask 255.255.255.0 192.168.20.2

Change the 10.10.1.0 and 255.255.255.0 parts to the IP and subnet of the network you are wanting to connect to through VPN.

I got the information here:
http://geekswithblogs.net/evjen/archive/2007/01/01/102429.aspx