- VSPACE SERVER 8.4 WITH WINDOWS SERVER 2016 INSTALL
- VSPACE SERVER 8.4 WITH WINDOWS SERVER 2016 UPDATE
- VSPACE SERVER 8.4 WITH WINDOWS SERVER 2016 WINDOWS 10
- VSPACE SERVER 8.4 WITH WINDOWS SERVER 2016 PASSWORD
I know Hyper-V, I’m not new to the existence of Hyper-V, but I’ve only ever briefly touched it in lab environments, until recently. Ugh.I realise I’ve not posted for a while, and I’ll try and atone for that going forward, I’ve been a busy server guy at work, but onto the good stuff. So it seems I am not reaching my DHCP server on the DC, or I have something configured wrong with the VM host. After a Reboot I am getting an IP of 169.254.#.#, which is not the range I set in DHCP.
VSPACE SERVER 8.4 WITH WINDOWS SERVER 2016 UPDATE
UPDATE 4: I added DHCP to the DC, and I set both VMs to use Host Only network, then configured the VM host NOT to provide DHCP services for host only networks. So, DNS on the DC is not properly configured somehow. And the DC is now using 8.8.8.8 as the secondary, so it seems the workstation IS using the DC as the DNS, and DNS IS using 8.8.8.8 to resolve web site names. But, I can reach web sites on the workstation, even though DNS is ONLY set to the IP of the DC. On the DC I can ping DOMAIN.local, on the workstation that fails. UPDATE 3: I have now set the NIC on the server to use itself as the primary DNS and 8.8.8.8 as secondary, and the workstation uses the IP of the DC. So I turned off the firewall completely for Domain networks and rebooted again. I do notice that the network did NOT change to a Domain network, so I changed it manually in the registry and rebooted.
VSPACE SERVER 8.4 WITH WINDOWS SERVER 2016 INSTALL
UPDATE 2: I did a fresh install of Windows Server 2019 Essentials, and addressed things in this order.ģ: Set static IP address (I did NOT set the DNS server to this static IP, I set it to 8.8.8.8)ħ: Verified that DNS has an entry under the server name for the domain. Suggesting that the DNS server IS being reached.
VSPACE SERVER 8.4 WITH WINDOWS SERVER 2016 PASSWORD
But if I use TESTDOMAIN instead, I get a user name and password prompt and then a DNS error. UPDATE: When I use TESTDOMAIN.local as the domain name, I immediately get the An Active Directory Domain Controller. So, is there something obvious I am missing? Is a Windows Server demo not actually useful for joining a client? In which case, what IS it useful for, since clients joining the domain is what Windows Server is for? I just need to be able to test some PowerShell Remoting behavior with 5 or so connected clients, and then only for a week or so. But that's exactly why I chose Essentials. I assume I am doing something wrong in the configuration, especially since I don't have much experience configuring domains. I had the same issues with a Windows Server 2019 Essentials install.
I have verified that the network connection on the server is a Domain Network, and I have turned off the firewall for domain networks. I have also tried using which results in a Can't reach this page error. I have tried all caps, all lower case, and the mixed case shown in Active Directory Domains and Trusts on the server. However, trying to join the domain results in An Active Directory Domain Controller.
VSPACE SERVER 8.4 WITH WINDOWS SERVER 2016 WINDOWS 10
I have a Windows 10 Enterprise client, with the DNS server manually set to the IP of the Windows Server 2016 Essentials box.ĭHCP is being handled currently by Parallels. It is the DC, it has a static IP address, DNS is running. I have a freshly installed 180 day demo of Windows Server 2016 Essentials, which has been through the wizard setup procedure and has all current updates.
I am trying to set up a small test domain using Parallels Desktop VMs.