Cann't find DC in my Domain created in Windows Server 2016.

Question

I am planning a test to handle an application with a domain user under the domain environment.

I don't always use "domains" in my development environment
Install Windows Server 2016 on one computer
We have set it as an Active Directory / Domain Server.

Connect this and one client machine (Windows 10) with PtP
I want to make this client machine a machine belonging to the domain.

(Finally, register the domain user on the server side,
Even if the user is not registered on the client machine
A domain user, can use the application.
It should have been implemented,
but the environment is set for the demonstration experiment.)

!! However, this client machine cannot register the domain.

Control panel
→ system
→ Computer name, domain and workgroup settings
→ Change settings
→ System properties (computer name tag)

→ Click Change to change the computer name or join the domain
→ Click [Change]

Or

→ Click Network ID to use the wizard to join a domain or workgroup
→ Click [Network ID]

I get an error if the domain I configured on the domain server is not found.

The NetSetup.LOG generated in the Windows \ debug folder will have the following results:

(The purpose was to kick out the domain name "MYDOM.LOCAL")
05/22/2020 20:01:20:747 -----------------------------------------------------------------
05/22/2020 20:01:20:747 NetpValidateName: checking to see if 'MYDOM.LOCAL' is valid as type 3 name
05/22/2020 20:01:20:763 NetpCheckDomainNameIsValid for MYDOM.LOCAL returned 0x54b, last error is 0x0
05/22/2020 20:01:20:763 NetpCheckDomainNameIsValid [ Exists ] for 'MYDOM.LOCAL' returned 0x54b

(The domain name is changed to "MYDOM")
05/22/2020 20:01:53:480 -----------------------------------------------------------------
05/22/2020 20:01:53:480 NetpValidateName: checking to see if 'MYDOM' is valid as type 3 name
05/22/2020 20:01:53:537 NetpCheckDomainNameIsValid [ Exists ] for 'MYDOM' returned 0x0
05/22/2020 20:01:53:537 NetpValidateName: name 'MYDOM' is valid for type 3
05/22/2020 20:02:21:380 -----------------------------------------------------------------
05/22/2020 20:02:21:380 NetpDoDomainJoin
05/22/2020 20:02:21:380 NetpDoDomainJoin: using current computer names
05/22/2020 20:02:21:380 NetpDoDomainJoin: NetpGetComputerNameEx(NetBios) returned 0x0
05/22/2020 20:02:21:380 NetpDoDomainJoin: NetpGetComputerNameEx(DnsHostName) returned 0x0
05/22/2020 20:02:21:380 NetpMachineValidToJoin: 'DESKTOP-8F4OJ7E'
05/22/2020 20:02:21:381 NetpMachineValidToJoin: status: 0x0
05/22/2020 20:02:21:381 NetpJoinDomain
05/22/2020 20:02:21:381 HostName: DESKTOP-8F4OJ7E
05/22/2020 20:02:21:381 NetbiosName: DESKTOP-8F4OJ7E
05/22/2020 20:02:21:381 Domain: MYDOM
05/22/2020 20:02:21:381 MachineAccountOU: (NULL)
05/22/2020 20:02:21:381 Account: MYDOM\mori1
05/22/2020 20:02:21:381 Options: 0x23
05/22/2020 20:02:21:387 NetpValidateName: checking to see if 'MYDOM' is valid as type 3 name
05/22/2020 20:02:21:443 NetpCheckDomainNameIsValid [ Exists ] for 'MYDOM' returned 0x0
05/22/2020 20:02:21:443 NetpValidateName: name 'MYDOM' is valid for type 3
05/22/2020 20:02:21:443 NetpDsGetDcName: trying to find DC in domain 'MYDOM', flags: 0x40001010
05/22/2020 20:02:51:460 NetpDsGetDcName: failed to find a DC in the specified domain: 0x54b, last error is 0x0
05/22/2020 20:02:51:460 NetpJoinDomainOnDs: NetpDsGetDcName returned: 0x54b
05/22/2020 20:02:51:460 NetpJoinDomainOnDs: Function exits with status of: 0x54b
05/22/2020 20:02:51:460 NetpJoinDomainOnDs: NetpResetIDNEncoding on '(null)': 0x0
05/22/2020 20:02:51:460 NetpDoDomainJoin: status: 0x54b

Looking at this log, it says "trying to find DC in domain 'MYDOM'".
It seems that the domain controller is kicked out
because it is not in the domain'MYDOM ',

Before that

it say "NetpCheckDomainNameIsValid [Exists] for 'MYDOM' returned 0x0",

This check requires a domain controller, which seems inconsistent.

Until now, even if you set up a domain in such a test environment
It would have been nice to set the default settings according to the wizard without thinking about it.
I'm having trouble finding the way to deal with this time, which one is the policy,
Or it would be helpful if you could give us a reference such as a reference site or literature.

Answer 1

QnA currently supports the products listed here (more to be added) Better to reach out to subject matter experts in dedicated forums over here.

https://social.technet.microsoft.com/Forums/windowsserver/en-US/home?forum=winserverDS

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

--------------------------

Regards, Dave Patrick ....
Microsoft Certified Professional
Microsoft MVP [Windows Server] Datacenter Management

Disclaimer: This posting is provided "AS IS" with no warranties or guarantees, and confers no rights.