![]() ![]() Domain controller and all members must use domain DNS only on connection properties and no others such as router or public DNS. For the DC remove the google public DNS from connection properties. Please post an uedited ipconfig /all of DC and problem client. Maybe I do have to change some settings for HyperV-Switch? Or add static routes on HyperV? The configuration of the DC should be correct, because connections are successfull from other VMs, I think. ![]() I spent a lot of time for Google-searching for a solution, but I only found some solutions with disabling IPv6, but I dont want to disable IPv6. IPv6 is configured on HyperV and all VMs and working. ![]() Same result with disabled firewall on DC. The request has been executed with the domain controllers IPv4 address, not FQDN. UDP port 389 (unknown service): LISTENING or FILTERED PortQuery-Error (executed on my local PC): Same test on an non-domain-member VM on Hyper-V-Host is still successful. I tested the connectivity with PortQuery and got an error on port 389 UDP. VMs on the same HyperV-Host can join the domain as well. The domain controllers are working as expected, but I can't add clients from outside Hyper-V. All Servers are installed with Windows Server 2016. I created two new VMs with domain controller role on a HyperV-Host. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |