virtualbox.org

I have an installation of Windows Server 2016 running as a VirtualMachine within Oracle's VirtualBox all on my Windows 10 notebook. Set up as a test environment so I can learn about how server software works and how to use it.

After getting through the initial installation, I decided to try and change the IP address assignment from DHCP to static.

I'm not exactly sure what all I need to do in order to get this to work.

I have gone through Network Connections -> IPv4 -> Use the following IP address:...

But once I swap to static, I lose connectivity.

I am basically looking for help on figuring out what I need to do/change on the host side as well as on the VM settings side for the static assignment to work.

Thank you for any guidance.

-Chris

Have you ever done this sort of thing on a physical machine? How you do it doesn't change just because you are using a vm.

How have you configured the networking in the vm? Where is it getting its DHCP allocated address from? It should work fine if you are using bridged and the vm is getting its config from a DHCP server on the LAN.

Changing from DHCP to static should work as long as you only change the IP address to something else in the same subnet (only change the last octet) and don't change any of the other values, such as netmask or gateway address. You don't need to change anything on the host.

Bill,

Thank you for the response.

The only experience I have is from downloading and playing around with different software; emc isilon, ESXi, and different applications for testing around with routers and switches.
I definitely do not have any experience with physical server machines.

I have the VM network settings configured to use the 'bridged-adapter' with my notebook wireless card.
On my host network settings, I have checked "Allow other network users to connect through this computer's internet connection" within the "VirtualBox Host-Only Network."

I think the reason I am looking to change from DHCP to static is so that I can have the dedicated address to talk back and forth with from different machines. No real reason why; just so that I can.

My ultimate goal is to figure out how to use SMI-S with the Windows Server; it is an assignment from a mentor of mine. To be able to figure out how to use SMI-S.

-Chris

wisemanchris92 wrote:On my host network settings, I have checked "Allow other network users to connect through this computer's internet connection" within the "VirtualBox Host-Only Network."

There's absolutely no need to do that. And you did it wrong in any event. You're not using the Host-Only network, you're using Bridged. Two completely unrelated options. Please undo what you did...

I suggest you start with the DHCP option. Then open a Command Prompt in your Win2016 guest and note the output of the following command:

• 
  ipconfig /all

I've included a sample output, with only the parameters that you should be focusing on, for the network card that interests you (its physical address starts with 08-00-27):

> ipconfig /all
   Physical Address. . . : 08-00-27-36-28-0C            <-- VBox NICs start with 08-00-27
   IPv4 Address. . . . . : 192.168.100.103(Preferred)
   Subnet Mask . . . . . : 255.255.255.0
   Default Gateway . . . : 192.168.100.1
   DNS Servers . . . . . : 1.1.1.1
   Primary WINS Server . : 192.168.100.1

Then, if you decide to manually set the IP address, you'll need to set the rest of the parameters as well: SubnetMask, Gateway, DNS server. The WINS server is optional, but it may help in your Windows network...