Handling the world's first odd plus domain fault

Colleagues have been on a business trip for a long time. Recently I came back and found me and asked to rejoin the company's domain. I immediately asked my colleagues to open our company's internal remote assistance system and remotely connect his desktop to my PC. Come up, then get used to it, right click: "My Computer"---"Properties"--"Computer Name"---"Change", and then follow the company's new naming convention Enter a computer name, fill in the company's domain, click "OK", then enter: delegate the username and password with domain privileges... pop up in a few seconds:

Because the user is anxious to use the computer, I am too lazy to think about the problem, I will give the user a new computer name, and then re-operate the process of adding the domain,

This time pops up the following prompt:

A happy time. OK~~ Remotely restarted the user's computer and disconnected from the user.

This has come to an end.

But after a while, the user called and said that after the computer restarted, Interface, enter his own domain account and password, log in to the domain, after confirmation, pop up: Error message:

“windows cannot connect to this domain because the domain controller is faulty or unavailable, or No computer account found, please try again later. If this message continues to reproduce. Please contact the system administrator for help.

I have just shown that the domain has been successful. In theory, there is no problem. I am meeting the Liberia online and immediately get a call with the next Liba. Contact, explain the fault.

Let me know, calm down.

First go to the computers group in the domain to see this guy:

As shown above, a red pants fork, where is the problem? Because the user is anxious to use the computer, according to the old Method, right click on the top: enable! Then, restart the computer, successfully log in with my account and user account, thank you, thank you, and then, because the new strategy is not applied to the user's computer, I will give the user by the way: gpupdate /force a bit, restart, the login screen appears again:

“windows can't connect to this domain because the domain controller is faulty or unavailable, or the computer account is not found, please try again later. If this message continues to reproduce. Please contact the system administrator for help.

At this time, the user is in a hurry to use the computer, so he hastened to unplug the network cable, restart the computer, and use the local cache that was successfully logged in. The user successfully logged in. Hastily returned the computer to the user, and also said BYE with the old side.

After 1 hour, the user sent the computer to me to continue processing. I thought it would take off the domain just added, but the following error occurred:

After calm, I A dead conclusion is drawn:
There is no problem in adding domain to other people today. In the process of adding domain to this user, the prompt of adding domain success is also obtained. As shown in the second picture, the problem must still be in the user. On this computer, this is definitely not wrong. Let's start from the log in the process of adding the domain: From the user's location: C:\\WINDOWS\\Debug\\NetSetup.LOG Open this LOG~ As in the first line: SCManger? No Open service agreement management? As above, the second line, Netlogon has a problem? I started to check: NetLongon service, I encountered a strange thing: As shown above, I tried to stop and even reported an error, as shown above? Strange, this service is enabled by default and started correctly. But it can be stopped manually. Start repairing: From the registry on the computer next to a normal plus domain, the following location: HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Services\\Netlogon\\Private HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Services\\Netlogon\\Security Export the above two points~~ ~1.reg; 2.reg Get this computer, double-click to import these two registry files. Restart the computer again. Re-exit the domain, add the domain ~~~ even everything is OK!

----- - To solve this problem successfully -------------

Postscript: The first feeling is the world's first strange, the former knows that this NetLongon will not be able to add the domain ~~~ I have never heard of it, the surface is successfully started, the actual operation cannot be deactivated, and the domain cannot be added.

What caused this failure, I still don’t know, if you know, please tell I thank you~

small A:

When I first encountered this problem, my mind was a little confused, until I called the old party, and I calmed down under the old man’s enthusiasm. Oh, ginger is still hot, I am still young. Ha.

Calmly thinking, calmly analyzing, calming!!!!!!! is the magic weapon for my last success.

After the problem was solved, I tried to find it online. In the official technical community of Microsoft. Some people have encountered the same problem, but they didn’t solve it until the end.

Finally:

In order to facilitate my friends with similar faults, I have written the solution of this article as a fault repair patch, put it below, for you to choose ~~~ if you encounter the same Problem, please download the program below to execute..~~

Program Patch Description:

Complete the following two functions:

1. Fix the above description Two registry keys;

2, set the service status of LmHosts, Netlogon, seclogon, Browser, lanmanworkstation, lanmanserver to automatic

The repair will pop up the following window prompt: