02-27-2019 11:22 PM
02-27-2019 11:22 PM
I'm using VMware and made a fresh install of windows server 2019 Version 1809. It is still configured as Workgroup and I want to migrate to Domain. I searched some tutorials but there is always one issue:
When I open the "network adapter - TCP/IPv4 - extended" it's not clear to me which IP-addresses to enter. I've tried some combinations and after closing all network adapter windows it always ends with a new window:
Windows network diagnosis - found problems - DHCP is for Ethernet0 not activated - solved
As my IP-settings are somehow based on beginners level I don't know the correct values.
An AVM Fritz!Box is my router with IP 192.168.100.10 so this is to enter as gateway (?) The router works as DHCP-Server and so DHCP is not needed in windows server 2019, right?
As I understand some posters it is recommended to set a static IP for the server, like 192.168.100.33 which is still free.
Please have a look at my 3 screenshots.
02-28-2019 03:10 AM - edited 02-28-2019 03:12 AM
Possibly there is a problem with the VMware settings - network adapter?
Default was NAT, now I changed to Host-only, but no success.
02-28-2019 04:05 AM - edited 02-28-2019 05:12 AM
one step further:
I changed network settings to Bridged -> network is now ok.
Still trouble with IP settings as network diagnosis starts after closing TCP/IP window.
02-28-2019 07:34 AM - edited 02-28-2019 08:19 AM
so far my WS2019 works now as domain server/controller.
It seems important to set VMware Network Adapter to Bridged.
Now I can successfully ping from the host-OS to WS2019 in the VM.
In this site they use NAT as network connection so its not clear how this works
As described in document "Windows Server 2019-Step by Step Installation of Domain Controller"
finish your work:
Server Manager - Tools - DNS - Reverse lookup zone - New Zone - ...
02-28-2019 08:09 AM
Yes, setup the guest as bridged. Then domain controller and any members should have the static address of DC listed for DNS and no others such as router or public DNS
by Ned Pyle on August 23, 2019
by Ned Pyle on April 10, 2019