I am running Cisco Anyconnect VPN Client version 2.5.3054 on a laptop running Windows Vista Home Premium (version 6.0.6002) Service Pack 2. I am running the VMware Player version 4.0.2 build-591240. The host operating system running under VMware Player is Debian 6.0.2.1 i386. The laptop is connected to a wireless connection, and I can browse the web from Windows Vista using Firefox just fine.
I am able to boot into the Debian VM and open up a browser and access websites on the WAN from within the VM just fine. I can ping real
Linux hosts on my LAN via:
ping <lan_system>.local
where <lan_system> is the hostname returned from uname -a on that system on my LAN.
From a DOS CMD shell, I am able to ping hosts that exist on the remote network served by the Cisco AnyConnect Client's VPN network (and without the .local suffix applied as above):
ping <remote_system>
However, from within the Debian VM, I expect to be able to also ping those same remote hosts (<remote_system>) that are tunnelled over the VPN set up by Cisco AnyConnect Client. Let's say that I can ping a <remote_system> called flubber from a DOS CMD prompt just fine. When I execute
Linux ping command from inside the Debian VM via:
ping flubber
It returns immediately with this output:
ping: unknown host flubber
For reference since I suspect it will be useful, here is the output of the route print command from the DOS CMD prompt:
route print
===========================================================================
Interface List
30 ...00 05 9a 3c 7a 00 ...... Cisco AnyConnect VPN Virtual Miniport Adapter for Windows
11 ...00 1b 9e c4 de e5 ...... Atheros AR5007EG Wireless Network Adapter
26 ...00 50 56 c0 00 01 ...... VMware Virtual Ethernet Adapter for VMnet1
28 ...00 50 56 c0 00 08 ...... VMware Virtual Ethernet Adapter for VMnet8
1 ........................... Software Loopback Interface 1
12 ...02 00 54 55 4e 01 ...... Teredo Tunneling Pseudo-Interface
13 ...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #3
32 ...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #4
27 ...00 00 00 00 00 00 00 e0 isatap.{E5292CF6-4FBB-4320-806D-A6B366769255}
17 ...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #2
20 ...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #8
22 ...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #10
24 ...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #11
25 ...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #12
29 ...00 00 00 00 00 00 00 e0 isatap.{C3852986-5053-4E2E-BE60-52EA2FCF5899}
41 ...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #14
===========================================================================
At the top window border of the VM, clicking on Virtual Machine, then clicking on Virtual Machine Settings, then clicking on Network Adapter, I have these two options checked:
[X] Bridged: Connected directly to the physical Network
[X] Replicate physical network connection state
[ ] NAT: used to share the hosts's IP address
[ ] Host-only: A private network shared with the host
[ ] LAN segment:
[ ]
<LAN Segments...> <Advanced>
I've toyed with the other options such as NAT and Host-only but that had no effect.
Is there some way to allow the VM to access those <remote_system>'s?
