Hyper-V Guest win server 2019 unindentified network issue

Question

My host machine is running Windows 10 Pro and is hosting Server 2019 to get some practice on Active Directory and Powershell. But I am having issues getting the guest to connect to the internet through the Hyper-V external network adapter. So here are my IP config outputs for the host and guest machines. Any help or advice on how to resolve this issue would be greatly appreciated.

Windows IP Configuration Host machine

Unknown adapter Local Area Connection:<--- This is my VPN when on.

Connection-specific DNS Suffix . :
IPv4 Address. . . . . . . . . . . : 10.29.0.6
Subnet Mask . . . . . . . . . . . : 255.255.255.255
Default Gateway . . . . . . . . . :

Unknown adapter Local Area Connection: This is my VPN when off

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :

Ethernet adapter vEthernet (Default Switch):

Connection-specific DNS Suffix . :
IPv4 Address. . . . . . . . . . . : 172.24.64.1
Subnet Mask . . . . . . . . . . . : 255.255.240.0
Default Gateway . . . . . . . . . :

Ethernet adapter vEthernet (INTERNET):

Connection-specific DNS Suffix . : neo.rr.com
IPv4 Address. . . . . . . . . . . : 192.168.132.106
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.132.1
PS C:\windows\system32>

I also have an Ethernet 4 controller that did not show up on the IP config
it only had Microsoft LLDP Protocol Driver and Hyper-V Extensible Virtual Switch enabled.

Windows IP Configuration of Guest machine

Ethernet adapter Ethernet:

Connection-specific DNS Suffix . :
Link-local IPv6 Address . . . . . : fe80::5d48:9324:624d:6cbe%13
Autoconfiguration IPv4 Address. . : 169.254.108.190
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :
PS C:\Users\Administrator>

Answer 1

Do not install VPN role on a domain controller. Multi-homing a domain controller always causes no end to grief for active directory DNS

When NLA starts to detect the network location, the machine will contact a domain controller via port 389. If this detection is successful, it will get the domain firewall profile (allowing for correct ports) and we cannot change the network location profile.
If the domain was not found or process failed, NLA will let you to determine which firewall profile will be used, private or public.

The Network Location Awareness (NLA) service expects to be able to enumerate the domain’s forest name to choose the right network profile for the connection. The service does this by calling DsGetDcName on the forest root name and issuing an LDAP query on UDP port 389 to a root Domain Controller. The service expects to be able to connect to the PDC in the forest domain to populate the following registry subkey:
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\NetworkList\Nla\Cache\IntranetForests
If something hinders the DNS name resolution or the connection attempt to the DC, NLA is not able to set the appropriate network profile on the connection.

So I'd check the domain controller has the static address of DC listed for DNS and no others such as router or public DNS

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

Answer 2

@Anonymous The VPN is on the Host machine and is used when I surf the internet and is not on when I am using the VM's. Are you saying when I am using windows 10 as a host I can not have a third-party VPN host installed?

Answer 3

Please run;

Dcdiag /v /c /d /e /s:%computername% >C:\dcdiag.log
repadmin /showrepl >C:\repl.txt
ipconfig /all > C:\dc1.txt

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

Answer 4

Just checking if there's any progress or updates?

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