SOLVED: Cisco VPN Doesn't connect

[jackmetal]

Hi All, I've begun testing VirtualBox and so far I LOVE it. I am having one issue though. I need to be able to connect to my companies VPN from within the Guest OS. I am running Windows Vista as the Host and Windows XP SP 2 as the Guest. Everything installed and all windows updates applied to guestOS. The Cisco client installs fine but I can not get it to connect to the VPN server.

VPN works fine from a standalone XP server, but not within the guest OS. Unfortunately the VPN client doesn't work under Vista, so I need to get it to work under the guest OS. Any ideas?

Thanks in advance, and thanks for the excellent product. If I can get this working, I'm definitely recommending it to everyone else in our company.

[jackmetal]

I've continued to work on this and I've also tried it in VMWare with the same results.

Has anyone been able to get VPN running correctly under a Guest OS?

The VPN I'm currently needing to work is the Contivity VPN Client from Nortel Networks. Version is 04_15.14

I've tried it as NAT and Host Interface, with and without MS Firewall enabled and I get the same results. It resolves the VPN server, attempts to connect and then never does. Running it under standalone XP, it resolves, and then connects properly.

Anyway, just wondering if anyone has been able to get VPN working under the Guest OS and if so, do you have any tips that might help?

Thank You for any help you can give.

[jackmetal]

I have seen numerous posts requesting help for this and I've seen NO-ONE help. So I thought I would post my findings in hopes of helping others, since I received NO Help here.

I've decided to use another VM product since there was no support here, but at least I hope this helps others who need it, if they decide to stick with VirtualBox

To get VPN working under your Guest OS, it's actually simple:
1) Create a Host Interface either manually or through the GUI
2) Select Host Interface instead of the Default of NAT in the Guest OS
3) On your HOST OS, Bridge the new VirtualBox Interface it created and the LAN Interface you are currently using on your host for network access.
4) Configure the new MAC of the Bridged Interface for your network
5) Install, configure and use your VPN client.

That's it..

Have fun with your VPN and VirtualBox if you stick with it. It seems to be pretty decent, but we prefer to go the route of a product with better support (either via more active user forums, or Enterprise support).

[hege]

To get VPN working under your Guest OS, it's actually simple:
1) Create a Host Interface either manually or through the GUI
2) Select Host Interface instead of the Default of NAT in the Guest OS
3) On your HOST OS, Bridge the new VirtualBox Interface it created and the LAN Interface you are currently using on your host for network access.

This has really nothing to do with VPN. You are describing the standard procedure to do networking correctly and it's all there in the documentation. Everyone would assume that you have it done already, so no wonder you receive no help.

[Turntwo]

If that is the "standard procedure to do networking correctly" then why isn't it the default. If someone is asking the question, then they obviously don't know that they need to change their networking config to get VPN working.

I am still unable to get Cisco VPN working properly - I've tried Host-Only networking with the Host-Only network bridged on the Host OS. doesn't work. I've tried Bridge networking to the host network adapter - doesn't work (this is the only method that allowed a ping to the VPN IP). So while "it may be all there in the documentation" - the documentation isn't all that clear for someone who doesn't already know what they want to do, or how all the networking concepts work.

But I do appreciate the kind person who posted the solution that worked for them - instead of assuming that people posting issues already knew the answer...

[vbox4me2]

So while "it may be all there in the documentation" - the documentation isn't all that clear for someone who doesn't already know what they want to do, or how all the networking concepts work.

Yes you are right, but there are 2 different issues when it comes to manuals, 1) people don't read them and 2) those who do read them don't understand most of it.

But this isn't really the main issue of the problem at hand, the main problem is feedback. For example I submit about 10 pages of correcting material to MS each year about mistakes in manuals and other online documentation. The moral here is if you don't understand a manual there is no point bitching about it, contribute and get it cleared up or corrected or write your own and submit it, IT in every form or format is not a one way street, especially when it comes to manuals.

[cats_five]

The moral here is if you don't understand a manual there is no point bitching about it, contribute and get it cleared up or corrected or write your own and submit it

Many manuals are impenetrable because the people writing them are far too close to what they are writing about so cannot understand how anyone else can't understand the software. I have no idea if the VB documentation suffers from that or not, but it's a common problem with documentation. Another is that where the obvious is explained but finding the answer to a specific question is nigh on impossible, even if the whole manual is a PDF that therefore can be searched.

[gimel]

Old thread but anyway.
There is a manual but I can't see anything there that explains correctly how to setup the network

What does this mean? "1) Create a Host Interface either manually or through the GUI"
Should I select "Host-only adapter" in the VM settings?

[mpack]

Well, if you are going to take your instruction from 3-4 year old messages then don't be surprised that some of the software features and terminology has changed.

It's really quite simple: you should select "Host Only" if the VM only needs to communicate with your host, and not the outside world. The purpose of each of the networking modes is discussed in the user manual, chapter 6.

[gimel]

@mpack

There's no clue about the release date of the manual.

Ok, I selected "NAT" as it's the only way to use my VM. The VPN opens but I can't ping a remote address. I guess some data packet don't get through

[mpack]

There's no clue about the release date of the manual.

The release date of the manual is not important. The only important thing is that should describe the version of VBox you are using. That shouldn't be hard, given that the manual is bundled in PDF form in your Oracle\VirtualBox\Doc folder, and is also available from the VBox "Help" menu. Both are included in a standard VBox download.

Re your problem, most people who want internet access will use NAT or Bridged. NAT is safe, easy to set up, ok for simple browsing, but can't handle network apps that need full two way comms such as servers of various kinds. Bridged provides full access but needs a router to serve up an IP address. I don't use VPN myself, so I can't tell you what it requires. However, I expect that bridged would be best.

[James Houston]

This is very typical for me, but i myself learn a lot from your discussions.