|I'm sure many have posted concerning this issue, but I'm using VirtualBox for my server, and have set it's IPv4 address to 192.168.1.2, and it's default gateway to 192.168.1.1. I've bridged my network connection through Settings of VirtualBox; I've restarted the server and activated the scope of addresses to hand out. |
The host machine workstation/Windows/client-side (same machine hosting the Server 2012 installation) is not pulling an IP from the DHCP server. The VirtualBox network adapter has an auto-configured IP address of 169.etc.etc.. I also have another workstation machine connected to the same switch as the server, and it also is not pulling IP addresses (same auto-resolved 169 address). The switch is not connected to any networks or the internet; it's simply connecting the server and the workstation together.
Do I need to set a static IP and other settings for the VirtualBox virtualized network adapter? Beforehand, the adapter was set to NAT in VirtualBox, but I've switched this to Bridged and pointed to the main Ethernet network controller appropriately.
Any help would be greatly appreciated from anyone, thank you!