virtualbox.org

I'm running the Windows 10 Tech Preview on a Windows 8.1 Host. I cant access local network computers. My VM IP is 10.0.2.15 witch doesn't make sense because my local network is 192.168.?.?. The VM , named Virtual-Ozzie, doesn't even show in my router setup. Please help! I need to have full control of this OS in order to sufficient evaluate it and provide feedback to Microsoft.

Switch the guest to bridged. See http://www.virtualbox.org/manual/ch06.html

I tried to choose "Bridged" but it says invalid settings. Also it wants me to select a name in the list but there are no names listed.

theozzlives wrote:I'm running the Windows 10 Tech Preview on a Windows 8.1 Host. I cant access local network computers. My VM IP is 10.0.2.15 witch doesn't make sense because my local network is 192.168.?.?. The VM , named Virtual-Ozzie, doesn't even show in my router setup. Please help! I need to have full control of this OS in order to sufficient evaluate it and provide feedback to Microsoft.

Of course it doesn't. The default setting for a vm is NAT. This means that the vm runs in its own network and uses NAT to share the host's network connection. This is chosen as the default because many VB users run standalone machines connected directly to the Internet, not to a LAN.

To have the vm network like a LAN machine you need to use bridged mode. This allows the guest to share the physical NIC and behave like a LAN machine, getting its network config from DHCP and using the router directly.

BillG wrote:

theozzlives wrote:I'm running the Windows 10 Tech Preview on a Windows 8.1 Host. I cant access local network computers. My VM IP is 10.0.2.15 witch doesn't make sense because my local network is 192.168.?.?. The VM , named Virtual-Ozzie, doesn't even show in my router setup. Please help! I need to have full control of this OS in order to sufficient evaluate it and provide feedback to Microsoft.

Of course it doesn't. The default setting for a vm is NAT. This means that the vm runs in its own network and uses NAT to share the host's network connection. This is chosen as the default because many VB users run standalone machines connected directly to the Internet, not to a LAN.

To have the vm network like a LAN machine you need to use bridged mode. This allows the guest to share the physical NIC and behave like a LAN machine, getting its network config from DHCP and using the router directly.

if you'd read the whole thread, you would've seen that VB won't let me do that!

theozzlives wrote:if you'd read the whole thread, you would've seen that VB won't let me do that!

That doesn't make BillG's answer incorrect.

You need to use "Bridged". That means you'll need a host NIC you can bridge to. If none are listed then it means that you didn't install the VBox bridged networking filter driver, which was an option during installation.

mpack wrote:

theozzlives wrote:if you'd read the whole thread, you would've seen that VB won't let me do that!

That doesn't make BillG's answer incorrect.

You need to use "Bridged". That means you'll need a host NIC you can bridge to. If none are listed then it means that you didn't install the VBox bridged networking filter driver, which was an option during installation.

Thank you, I just re-installed VB and selected that option. It works now.