On this page
Recent Posts on Technozone
This site
Calendar
<February 2012>
SunMonTueWedThuFriSat
2930311234
567891011
12131415161718
19202122232425
26272829123
45678910
Archives
Categories
Microsoft MVP
Blogroll OPML
Disclaimer

Powered by: newtelligence dasBlog 2.0.7226.0

The opinions expressed herein are my own personal opinions and do not represent my employer's view in any way.

Send mail to the author(s) E-mail

Theme design by Craig Pringle

Based on the essence theme by Jelle Druyts

Cisco VPN Client on Windows 7 x64#

For reasons that escape me Cisco have chosen not to release a 64-bit version of the IPSec Cisco VPN Client.

This is a problem for me since I installed the 64-bit version of Windows 7 RC on my Toshiba M750.

To get around this without rebuilding with the 32-bit version I employed Windows 7’s new XP Mode – aka Virtual XP.

First I followed the steps on the download page:

  1. Enabled virtualisation extensions in the BIOS.
  2. Download and install the Virtual PC Beta.
  3. Download Windows XP Mode.

That done I fired up the Virtual Windows XP from my Start Menu:

image

This loaded up a Virtual Machine already running Windows XP.  I installed the Cisco VPN Client and verified that it could connect to the VPN. 

This is where it gets a little tricky.  At this point I have my Toshiba, which is the host and an XP machine which is a guest.  The XP Guest has a virtual adaptor that leverages the host’s network adaptor and can connect to the remote network.  But the host has not way to connect through the guest to get to the remote network.

For initial testing I created a static route for one of the subnets and pointed it to the IP Address of the guest.  This worked, but it is a bit fiddly as the guest IP address is assigned by DHCP and as such will change depending on where I am.

I wanted something that required a little less work to get connected.  To achieve this I needed to create a virtual adaptor on the Host.  This is done by adding a loopback adapter to the host.

Adding a Loopback Adapter to the Host

In Device Manager right click the root node and select Add Legacy Hardware

image

On the welcome screen click Next.

Then select Install the hardware that I manually select from a list (Advanced) and then click Next

image

Scroll down and select Network Adapters and then click Next

image

Then select Microsoft as the Manufacturer and Microsoft Loopback Adapter and then click Next

image

On the confirmation screen click Next.  Then when the installation finishes click Finish.

Once this has completed you will find a new network adapter in the Network Connections.

image

I configured this adapter with a private IP address in a range that I don’t use at home or work. 

Next I added a second Virtual Adapter to the Virtual Windows XP machine and bound this to the new Loopback Adapter.  I assigned a static address to this in the same range as the Loopback adapter.

Because the network I am connecting to uses a number of subnets I wrote two quick CMD scripts.  One adds the routes on the host, the other removes them.

Virtual PC also creates shortcuts for applications installed in the guest on the Start Menu of the host. 

image

To connect to my VPN I can run this and it hides Virtual Machine’s desktop and the VPN client looks like it is running on the Windows 7 machine.  I then run my script to create the routes and I can work away.  When I disconnect the VPN I run another script to delete the routes again.  Of course I can add shortcuts to all three actions to my desktop to ease the process.  Not quite as clean as installing the client directly on the machine, but it works.

Update: For details of the command scripts see this post.

Sunday, May 10, 2009 10:16:04 PM (AUS Eastern Standard Time, UTC+10:00) #   
Comments [9]  | 

 

Wednesday, May 13, 2009 4:45:13 AM (AUS Eastern Standard Time, UTC+10:00)
This look great, but can you add a sample of your "two quick CMD scripts"
Leigh
Tuesday, May 19, 2009 11:03:08 PM (AUS Eastern Standard Time, UTC+10:00)
This is an interesting solution. Can you give examples of the cmd files you created? I got as far as creating the vpn in the virtual machine and starting it using XP mode. But I couldn't figure out how to access the vpn from the host.

My first thought was to map drives on the virtual machine to locations in the vpn's system. But then I couldn't figure out how to share that mapping with the host.

Thanks for the information.
Darrel
Wednesday, May 20, 2009 10:29:14 PM (AUS Eastern Standard Time, UTC+10:00)
Howdy,

I had the EXACT same issue as you. (getting the Cisco VPN software to work under the Windows XP VM running under Windows 7 x64) I am running the RC - Build 7100.

All I did was shutdown the VM and change the network adapter from the 'Shared Networking (NAT)' to the physical network driver itself. I then restarted the VM and the Cisco client works wonderfully now.

I wonder if that might work in your case?

Regards
Matt
Friday, May 22, 2009 10:56:57 AM (AUS Eastern Standard Time, UTC+10:00)
You probably already know this Craig - but a beta "NCP Secure Client" is available that works a treat on Windows 7 x64.
yaz
Tuesday, June 02, 2009 2:19:47 PM (AUS Eastern Standard Time, UTC+10:00)
Hi, there!!
Craig, your tutorial was the light at the end of the tunnel. As you said, I created 1 Loopback Adapter for the Windows 7 (using ip 192.168.0.248, sub-mask 255.255.255.0) and another Loopback Adapter for the Windows XP (using ip 192.168.0.249, sub-mask 255.255.255.0).
As friend Matt said, I also changed the network adapter from the 'Shared Networking (NAT)' to the physical network driver itself (my Wireless adapter, in the case).
I was able to successfully connect using the VPN link created on Windows 7, but it is still not working.
The VPN connects and seems to be OK, but when I try to ping one of the servers at my work, it is not finding the server.
Could you give me some advice? I think you guys are the ONLY people that were able to successfully make it work.
My contact is: marcus_navarro@hotmail.com

Thanks!!
Marcus
Sunday, June 21, 2009 10:37:41 PM (AUS Eastern Standard Time, UTC+10:00)
VPN client is apparently up on Win7, but I'm no able to route private connection through virtual vpn. :(
>route add 10.0.0.0 mask 255.0.0.0 192.168.168.2 metric 1
Ok!
>route print
IPv4 Route Table
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.168.0.1 192.168.0.240 20
10.0.0.0 255.0.0.0 192.168.168.2 192.168.168.1 31
....


What's wrong ?
Mateusz
Wednesday, July 01, 2009 10:39:19 AM (AUS Eastern Standard Time, UTC+10:00)
This is awesome, thanks! Can you please provide us with the CMS Scripts?
Thanks!
perera
Wednesday, July 01, 2009 10:41:21 AM (AUS Eastern Standard Time, UTC+10:00)
This is awesome. thanks. Can you please provide us with the CMD Scripts? Thanks!
Sunday, July 05, 2009 4:06:38 PM (AUS Eastern Standard Time, UTC+10:00)
Hi Craig,

Thanks for posting your routing scripts. I have re-read your instructions several times and there is one thing I do not understand. I understand Win7 will try to route traffic (that has a destination of my work network) to my Virtual XP instance. What I do not understand is - what makes the Virtual XP instance route that traffic out of the VPN?

Based on your instructions, I don't see what makes XP act as a gateway. XP certainly receives the traffic, but I don't see why it would want to do anything with that traffic. The only way I could get it to work was to enable Internet Connection Sharing on the Cisco Systems VPN Adapter (which makes XP act as a gateway). Please give me some insight.


Thanks
John
Comments are closed.
All content © 2012, Craig Pringle