Conditional Theory of WINDOWS Joining Domains

With the popularity of the network, more and more computers are running on the network, while domain names are managed and maintained in the logical environment required by large networks. We spent a lot of effort to build a domain controller, but we can't let the client join the domain. What should we do at this time? Some of our own experiences today are summarized as follows:

When the domain controller is combined with the DNS The server side is installed together, not synchronized, the domain name of the DNS and domain controller installed on a separate DNS server is not registered on the domain controller, if not registered, it may cause problems.

Solution: Ipconfig will /registerdns (note no spaces in the middle), run on the domain controller, and then run gpupdate /force to force the refresh policy. In some cases, the host can join the domain, individual host Cannot join the domain. At this time, we should fully consider the client.

Required conditions for joining to the domain:

1. The host name and domain controller cannot be the same name, and the same name cannot communicate with other hosts.

2. The host's primary DNS is set to point to the domain controller's IP and NSLOOKUP test domain name PING test connectivity.

3. If you install the GHOST system, be aware that the SID values ​​to be modified cannot be the same.

4 open TCP /IP NetBIOS support services running CMD SERVICES.MSC.

5. Secondly, even if the local connection property is enabled: Microsoft Network Client, and Microsoftmq network file and printer sharing.

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

Everything has its advantages and disadvantages, and improper use can bring irreparable damage. To this end, if you want to know the domain, in addition to refer to this tutorial, you can also learn more domain content.