WINDOWS can not join the domain talk

When we spend a lot of effort to build a domain controller but can't let the client join the domain, it is a tricky problem. Now I personally summarize the following points:

On the server side, install the domain controller When installing together with the DNS, if you do not synchronize the installation, after installing the DNS server, you should consider whether the DNS and domain controller domain names are registered in the domain controller. If not registered, it may cause problems. Solution: On the domain controller Run ipconfig/registerdns (note that there is no space in between), then run gpupdate /force to force the refresh policy. In some cases, some hosts can join the domain, and some hosts cannot join the domain. In this case, we must fully consider the client. Machine problem. The necessary conditions for joining the domain are:

1. The host name cannot have the same name as the domain controller, and cannot have the same name as other hosts.

2. The host's primary DNS setting should point to the domain. Controller IP. Use NSLOOKUP to test domain name and PING test connectivity.

3. If the GHOST system is installed, note that the SID value cannot be modified.

4.Turn on TCP/IP NetBIOS Helper service, running CMD>SERVICES.MSC.

5. It is also enabled in the properties of the local connection: Microsoft Network Client and Microsoftmq network file and printer sharing.

6. If you can't join the domain with a domain name, you can try to join the domain with NetBIOS name.

I wish you success in the field, hehe!