Forum Discussion
windows server 2019: DHCP/DNS/static IP
Possibly there is a problem with the VMware settings - network adapter?
Default was NAT, now I changed to Host-only, but no success.
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.
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.
Some help I found in https://www.youtube.com/watch?v=9GlhcDpH13I Video and in https://gallery.technet.microsoft.com/Windows-Server-2019-Step-4c0a3678 document
In https://www.sysnettechsolutions.com/en/server2019/install-windows-server-2019-vmware-workstation-14/ 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 - ...
cheers folks
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
