Previously, on Simulcron...
I'm giving up on the VPN thing for now. I suspect my "double NAT" setup is causing problems for IPSec. (Also, I just checked, and for some reason Windows is back to forwarding packets
Anyways. Thus far on my Win2016 VM, I had ActiveDirectory services and DNS installed. I set up DNS under the "outpost.amateria" domain ("Amateria" is an age from Myst III that I like.)
Next order of business was to set up a DHCP server so I can hand out IP addresses to the VMs on my VMWare LAN.
Oddly, when I went to configure the DHCP server, it failed out with the error "The DHCP service could not contact Active Directory." This error was a little misleading - after doing some digging, I discovered that I'd forgotten to add my user account (that I was using to add DHCP to AD) to the Domain Admins account and that I actually just didn't have permissions. Added myself to Domain Admins and rebooted, and the problem solved itself.
Next step was to actually configure a DHCP scope. The only options I really cared about were the Router (default gateway) and DNS Server options.
With all this done, I decided to go ahead and add a Windows 8 VM to my new domain. Done, and done. I tested and confirmed my new VM has access to the Internet. (I also tested to see if it could send traffic to my VPC. No dice.)
Undecided what to do next...
No comments:
Post a Comment