virtualbox.org

VBox 5.0.2
Host is Windows 10
Guest Windows Server 2012 R2

When I set the network mode to NAT, it gets a DHCP ip address fine and networking is happy.

When I configure WS2012 with static ip address, there is no connection to the network (ping to default gateway is unreachable).

Help?

Does it get an IP OK from DHCP in bridged mode? Does that work? Perhaps you could tell us why you want change to static and what the static config is?

It gets an IP just fine from DHCP when in NAT mode. I want to run the VM with a static IP as I'm running a fairly small network with a small home office router with little intelligence (i.e. can't be a DHCP name server).

In bridged mode it's just dead.

Hmm reading the VBox user manual, Windows 10 isn't listed as a supported host OS.

When will it be? Is there a workaround for bridged static IP address in the meantime?

After tweaking for a while, this worked for me, YMMV though.

From inside the VM:
1. Control Panel -> Hardware -> Device Manager
2. Uninstall the Intel ethernet network card driver (there should be only 1 network adapter shown, which is what I chose)
3. Click on Scan for hardware changes and let the network card driver get reinstalled
4. Configure network mode for the VM to bridged
5. Configure the VM to have its static ip address (note that I needed static IPs, for DHCP YMMV)

So far seems to work well

Whew, Caesar.

I know I'm a bit late to the party, but I had the same problem with Server 2012 (*not* R2.) I simply could not set a static IP with DHCP active on the NAT network. I checked with ipconfig and found that Win2012 was getting an autoconfig IP address (169.254.xx.xx) even though I had specified a completely different static IP. My solution was to disable DHCP from the VirtualBox side (with VBoxManage) and then make 2012 a DHCP server.

Not sure if this is a VirtualBox NAT networks bug (after all, it is experimental) or a Windows 2012 "feature".

I installed 5.0.8 the bridge problem went away.