Custom Query (16363 matches)
Results (1489 - 1491 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #3526 | obsolete | Juniper VPN client on Guest messes up the connection of both Guest&Host at some point | ||
| Description |
I created a Windows XP guest virtual machine on a Windows XP host machine which works excellent as all my VirtualBox installations but I have encountered the following problem: I set the network interface to be attached to the host interface in order to have a virtual IP which worked great. On the guest machine I connected to a VPN using the Juniper Networks VPN client called "Network Connect"(dsNetworkConnect.exe). Everything worked perfect as I expected with my Guest VM being connected on the VPN but still being visible to our local network. At some point though the guest and the host machines lose the connection. They look connected but they are not. The only way to remedy the problem but again temporarily was to shut down the guest VM, kill the VirtualBox box service process, disable/enable the host connection several times until it gets an IP from our router and then start the guest VM again, connect to the VPN etc. But at some point it does the same thing again. Both host and guest lose their connection. In the end we used the VMWare which I didn't want from the start and it seems to work fine. Both machines never lose their connection so I suppose it's some bug with VirtualBox. Thank you guys for the excellent product VirtualBox is. I am sure you are gonna tackle this one soon. Thank you again! |
|||
| #1152 | fixed | Virtualbox Closes without warning or error when launching VM | ||
| Description |
I'm not sure what caused this, but here's the backstory: Vbox has been installed on my machine for a couple of months. Recently, we had a power failure at the office while virtualbox was running. When the power came back on, vboxdrv had vanished. I attempted to reinstall vboxdrv.ko from the virtualbox archive, and it partially fixed the problem. However, instead of getting an error about a missing kernel driver, the vm simply closes without warning or error message, and the status of the VM shows 'Aborted'. I have check everything I can think of. I have tried removing and reinstalling Vbox, to no avail. One thing I did notice is that when I attempted to install the vboxdrv.ko file, I accidently obtained it from the regular release of vbox, while I was running the ose version. I don't know if that would be part of the problem. I realized this and attempted to remove the vboxdrv.ko file and replace with the one from the ose archive, but I couldn't find the vboxdrv.ko file in the ose archive. Any help would be appreciated. I can submit any files you require. Please contact me if you need more information. My email address is thndrchld at gmail dot com (gotta keep the spam at bay, you know) |
|||
| #16315 | invalid | Not working bridging with Intel Corporation Centrino Advanced-N 6205 | ||
| Description |
VirtualBox any version doesn't support bridging with Intel Corporation Centrino Advanced-N 6205 (Wireless). I have confirmed this on all guest and all hosts. Im install last drivers for |
|||

