Shulou(Shulou.com)06/02 Report--

The computer cannot join the domain | cannot contact the domain controller

1. You cannot join the domain with the NetBois domain name.

2. Group policy cannot be applied properly.

3. Unable to open online housekeeping and access shared files.

This problem may be caused by the incorrect configuration of the Wins server or the failure to start the TCP/IP NetBIOS. I suggest you do the following check:

Recommendation 1: if you have a Wins server in your domain, check the client's Wins configuration to see if it points to the Wins server. In addition, please open the Wins server and see the yourdomain.com record for correct registration.

Recommendation 2: this problem may occur if TCP/IP NetBIOS Helper Service (TCP/IP NetBIOS support Service) is not running on the client computer. To resolve this issue, start the TCP/IP NetBIOS support service. To start the NetBIOS support service, follow these steps:

1. Log in to the client using an account with administrator privileges.

two。 Click start, click run, type services.msc in the Open box, and then click OK.

3. In the list of services, double-click TCP/IP NetBIOS Helper Service.

4. In the Startup Type list, click automatic, and then click apply.

5. Under Service status, click start to start the TCP/IP NetBIOS support service.

6. When the service starts, click OK, and then exit the Services snap-in.

Recommendation 3: please check whether "File and Printer sharing on Microsoft Network" is installed on the client.

1. Click start menu → Control Panel → Network connection.

2. Right-click the local area network connection (such as Local connection) in the window that appears, and select Properties.

3. Check the item "File and Printer sharing on Microsoft Network" under the general label.

*

The ultimate solution that the client cannot join the domain

There are a variety of errors when the client joins the domain, but in general, the solutions for clients not joining the domain are as follows:

1. Set the first DNS of the client to the IP of AD. Generally, DNS is installed in integration with AD. Empty the cache and re-register:

Ipconfig / flushdns clear DNS

Ipconfig / registerdns re-apply for DNS

2. Turn off the client firewall

3. Only leave IP as the first DNS of AD, and the second DNS is empty

4. Set up the SRV record of the client in the DNS of the AD server

5. Start DNS and TCP/IP NetBIOS Helper Service services

6. Change the hostname and delete the existing DNS record on the server, and restart

7. The system time of the client in the domain must be synchronized or slower than that of the DC server by 1 minute (no more than 10 minutes)

8. If the AD server operates a firewall for address translation, you need to modify the server address corresponding to [A] of DNA to the translated address, otherwise the terminal cannot enter the domain management.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.