Page 1 of 1
Connecting to Virtualbox Windows VM
Posted: 6. Nov 2014, 19:21
by Javia1492
I am currently using a 64-bit Windows 7 virtualbox VM with a Windows CE 7 design environment setup for firmware application development. This design environment allows me to use CoreCon for Windows CE to do download and debugging to my device via Ethernet connection. This is where my issue comes into play. I currently have the laptop the VM is running on on the same network as the device, so I am able to ping the host and device, but for the virtual machine, to get access to the network, i can only use NAT, which gives it an ipv4 address of 10.0.2.15.
Using NAT, i can ping the host machine from the VM, but i cannot ping the VM. Request timed out.
Using Host-Only Adapter, I can ping bidirectionally but the VM is not on the main network.
I need my device and VM to be on the same network and to be able to ping both devices bidirectionally, but I am not familiar enough with configuring virtualbox to understand how i can setup this network. Can someone provide guidance on this, or is it just a limitation due to the scenario?
Thank you in advance.
Re: Connecting to Virtualbox Windows VM
Posted: 6. Nov 2014, 21:42
by scottgus1
"Bridged" mode will put your guest on the same network as your host is on, everyone neighbors in the same IP address space.
Also, if you tried Bridged and it doesn't work, and you're trying to use wifi, you may have an incompatibility between your laptop's wireless card and the Virtualbox drivers - some cards don't like Virtualbox Bridged mode. If so, try the wired ethernet port if there is one.
Re: Connecting to Virtualbox Windows VM
Posted: 6. Nov 2014, 21:57
by Javia1492
scottgus1 wrote:"Bridged" mode will put your guest on the same network as your host is on, everyone neighbors in the same IP address space.
Also, if you tried Bridged and it doesn't work, and you're trying to use wifi, you may have an incompatibility between your laptop's wireless card and the Virtualbox drivers - some cards don't like Virtualbox Bridged mode. If so, try the wired ethernet port if there is one.
I tried using bridged network and using the laptops interl 82579lm gigabit netowkr connection card but it does not work. Unable to ping successfully and webpages do not load. Shows no connection to the internet. Did some searching and saw many issues, mainly on OSX hosts involving manually setting MTU registry size, but this was also unsuccessful as my symptoms seem to be more severe since i cannot even perform simple pings.
I have not tried using the wireless card since the laptop is connected to the network via ethernet, which is separate from the wireless network.
Re: Connecting to Virtualbox Windows VM
Posted: 6. Nov 2014, 22:03
by scottgus1
When you installed Virtualbox, did you right-click the installer and choose "Run as Administrator"? Some of the Virtualbox stuff doesn't load properly if Run As Admin isn't used.
Re: Connecting to Virtualbox Windows VM
Posted: 6. Nov 2014, 22:12
by Javia1492
scottgus1 wrote:When you installed Virtualbox, did you right-click the installer and choose "Run as Administrator"? Some of the Virtualbox stuff doesn't load properly if Run As Admin isn't used.
Yes, VirtualBox was installed using administrative privileges.
Re: Connecting to Virtualbox Windows VM
Posted: 7. Nov 2014, 00:19
by BillG
Since this is a networking problem, we really need a bit more networking info. "Doesn't work" isn't much to go on.
As scottgus1 said, If you use bridged networking, the guest should behave just like any other machine on the LAN. Set the vm to bridged mode, boot the vm and have a look at its network config. It should get its config from DHCP (if you have one). If you don't have a DHCP server on the LAN, you will need to manually configure it with a LAN IP and the necessary gateway and DNS addresses.
If you have a DHCP server but the vm is not getting its config from it, you can still configure it manually. Sometimes a problem with the NIC driver in the vm can cause problems with DHCP.
Re: Connecting to Virtualbox Windows VM
Posted: 7. Nov 2014, 02:17
by Rootman
I had a similar issue with a laptop, it would not work on the units onboard ethernet, I simply could never get it to work when bound to this NIC. Nothing I did would ever allow it to see the network.
My solution was an inexpensive USB ethernet adapter which would work when bound from the VB adapter. I successfully used it using bridged mode for a few years till I got a new laptop and it's NIC would work when bound in VB. I still have it and use it on another small form factor PC I use to have two nics I have them on two different networks and use both to connect to alternate networks depending on what I need to connect the VM to.
Not elegant but it worked for me.