Binding a pc to AD through Hyper V

Question

I have been learning how to set up and use AD by watching some videos on skillshare.com. While it is a bit out of the scope of the tutorial I'm watching, I'm trying to bind another pc to AD & I can't get it to work.

I'm running Windows Server 2022 in Hyper V. I can ping the IPv4 address of the Domain Contorler, but it doesn't recognize the host name. I've looked up & tried to figure out the problem but I can't find an answer, & some of the things I'm reading I don't understand.

Here's some relevant details:

Domain Controller Name: a.com

Hyper V is using default switch

Hyper V domain controller IPv4 - 192.168.0.1

Hyper V default gate - 192.169.8.1

Hyper V DNS server set to - 192.168.0.1

PC to Bind:

Ethernet (default switch)

IPv4 - 172.21.0.1

Default Gateway - 192.168.8.1

Preferred DNS - 192.168,0.1

Any help would be greatly appreciated.

Answer 1

Additional Info, when I into go into:,

System > Advanced System Settings > Computer Name > Change...

and I try to change it switch over & enter my domain name, a.com, I get the following error message:

The error was: "This operation returned because the timeout period expired."

(error code 0x000005B4 ERROR_TIMEOUT)

The query was for the SRV record for _ldap._tcp.dc._msdcs.a.com

The DNS servers used by this computer for name resolution are not responding. This computer is configured to use DNS servers with the following IP addresses:

192.168.1.2

Verify that this computer is connected to the network, that these are the correct DNS server IP addresses, and that at least one of the DNS servers is running.

Answer 2

Default gateway looks problematic. Also make sure the domain controller and problem member both use the static ip address of DC listed for DNS and no others such as router or public DNS. Try disabling all but a single adapter or problem member.

--please don't forget to upvote and Accept as answer if the reply is helpful--

Answer 3

Sorry it took me so long to reply. I've been working on this problem on & off at my paid internship.

The Host PC running Windows Server 2022 in a VM is connected to the client PC via a switch & there is no router between them. There is also no internet for any of the computers. I'm not sure if that is needed but my supervisor/teacher says it shouldn't matter.

The address for the DNS is 192.168.1.2. I made a new virtual switch called AD External to make sure it could bridge to the network on the host computer. Within the VM the network adapter is referred to as just Ethernet. I don't know if this is relevant, but I think it should be called AD External, but maybe it doesn't matter.

The host machine recognizes the virtual switch where it is called Ethernet (AD External). The host machine doesn't have any information for the IPv4 address. It is set to automatic. I checked the box that is says "validate upon exit". When it tries to validate it says that it can't find the problem. I'm not sure if that means there is a problem but it can't be found or there just isn't any problem.

I think the settings for the host machine's Ethernet (AD External) need to match the settings that are in its Ethernet adapter, but again I'm not sure. It occurred to me that I should try to ping the domain controller (a.com) within the VM, but even inside the VM it can't ping a.com.

So from what I can gather there is a problem with name resolution, but there shouldn't be because Service Manager says the DNS is online and has the address 192.168.1.2 which is what I enter for the preferred DNS server on every computer, virtual or otherwise.

The tutorial I was watching made it look so easy but I've been trying to figure out a solution for this problem for days now. If possible, maybe someone can point me to a tutorial where they do the exact same thing I'm attempting to do.

Answer 4

Here's some screen clips of the network settings a should have added.

This one is the VM:

This is the host machine:

The is the external client machine I'm trying to get AD to recognize:

The default switch on this one is from the Hyper V I have on that computer.

Answer 5

Use the switch address on both for default gateway. Also please run;

Dcdiag /v /c /d /e /s:%computername% >C:\dcdiag.log (run on PDC emulator)
repadmin /showrepl >C:\repl.txt (run on any domain controller)
ipconfig /all > C:\%computername%.txt (run on EVERY domain controller)
ipconfig /all > C:\problemworkstation.txt (run on problem pc)

Also check the domain controller System and Replication (DFS or FRS) event logs for errors since last boot. Post the Event Source and Event IDs of any found. (no evtx files)

then put unzipped text files up on OneDrive and share a link.