Bridge issue/route/vpn..

[Bling8d]

Ok so I have bridge issue, I don't know why but when bridged the only type of adaptater working is the Intel PRO/1000T Server. But when I connect to my vpn inside my vm I'm not connected anymore... I guess it's a routing issue. It works fine in vmware, and it works fine in a windows guest under Virtual Box..
If you have any idea please let me know, I have to use vmware for now and it sucks : (

[mpack]

Think of it this way: VirtualBox (the host software) can connect to the wider network by "bridging" to a physical host NIC. It can represent that network connection to the guest by simulating any NIC type that the guest can use. So, if you want your guest to work, make sure you pick a NIC simulation that your guest has drivers for.

"It works fine in VMWare" is not useful information - VMWare is a different VM platform, with its own set of hardware simulations. The guest OS must have the right set of drivers installed. If it does, then it will work. If it doesn't then it won't.

[Bling8d]

Yes but I'm not sure it's this kind of issue because the bridge works with the right adaptater (it just seems strange that it's the "server" one) but not the vpn connection and also I've tried to give the VM it's own wifi adaptator, so it's not connected to the host anymore and same problem, I have a connection but no vpn connection :/

[mpack]

The fact that bridged networking is in use on the host has nothing to do with the simulated adapter presented to the guest. Bridged networking can and does work with any guest adapter type. However the guest may not be so tolerant of different adapter types. In fact the problem here must be in the guest, because any "hardware" defect in the simulated PC would be experienced by all guest OS, not just the one you are using: and I have not noticed a rash of complaints of that nature.

[Bling8d]

So any idea about how I could solve this? Btw if someone wants to teamviewer with me we can, juste answer here. I'll be here all day long

[martyscholes]

it works fine in a windows guest under Virtual Box..

In my experience, vpn software is notoriously picky. I connect to my job via some Checkpoint software running on an XP guest under VirtualBox inside a Solaris host. Since you vpn works inside a Windows guest but not a Linux guest, my next question would be: Have you gotten it to work in Linux on bare metal (i.e. not as a guest)?

While I have not tried very hard, I have never succeeded in getting Linux anything to connect to my corporate vpn, so I would guess that you have not succeeded either. If it won't run on bare metal, then it probably will not run under virtualization.

Does that make sense?