Setup windows server and few client win 10. Virtual box IP issues . Setup

Discussions related to using VirtualBox on Windows hosts.
Post Reply
Mrdev2
Posts: 1
Joined: 2. Nov 2020, 10:12

Setup windows server and few client win 10. Virtual box IP issues . Setup

Post by Mrdev2 »

Hello, hope you are well and can help. I am a new starter at virtualbox, but I do assist in supporting a real network at a small school.

I have watched various YouTube videos, I want to setup a Windows server 2016 or 2019 with 2 to 3 windows 10. With my server being AD, DNS, DHCP.

But in all these videos people use 192.168.1.100 or 10.0.1.15 or something.

I follow these guides but always fail, I am sure it's because Virtual box network setup or virtualbox dhcp maybe wrong or something.

But what way can I set this up so I can use correct static IP or choose whatever IP sub etc. Because it just doesn't ping or join my test domain.

I am a new user and generally just reset passwords and install stuff by group policy at work, so want to setup something similar.

But I don't know where to find these IP addresses people keep using.

I do have team viewer if anyone can could help, thanks
Mrdev2
scottgus1
Site Moderator
Posts: 20945
Joined: 30. Dec 2009, 20:14
Primary OS: MS Windows 10
VBox Version: VirtualBox+Oracle ExtPack
Guest OSses: Windows, Linux

Re: Setup windows server and few client win 10. Virtual box IP issues . Setup

Post by scottgus1 »

An AD Windows server wants to be big kahuna on network, so any Virtualbox or other DHCP is going to get in the way. Virtualbox networks by default have active DHCP, except for Internal.

For an AD lab with internet try Virtualbox Networks: In Pictures: "Sandbox"

The server must be static IP. Static IP is OK for the clients, as long as it's in the server's IP range, or take an IP address from the server's DHCP. The server can have its DHCP serve a subset of its whole IP range. Example:
Network internet gateway 192.168.10.1 (if you use a pfSense sandbox router guest, this would be the LAN port, static IP. The WAN side can't be 192.168.10.0/24)
Server static 192.168.10.2
Server IP range 192.168.10.0/24 (net mask 255.255.255.0)
Server DHCP 192.168.10.100-192.168.10.150
Static Client 192.168.10.12
DHCP Client gets 192.168.10.101
etc.
All of this should make a valid AD.
Post Reply