The whole process of a DC time synchronization failure case

Recently, the company requested to set up a separate account for each employee as one of the company's (part-time) network management. This task naturally falls on the author. Considering the different nature of the work of the employees in each department, the acquired information is different. Therefore, a DC server is formed to form a domain, which can meet the requirements of the company's single user account, single login, and can be effectively, centralizedly and conveniently managed and controlled. . After deciding on the plan, the author immediately started to act. But I did not expect the problem to follow.
It was very smooth when upgrading domain controllers, but there was a problem when the client joined the domain controller. The specific situation is as follows: This is the eighth Windows 2000 client to be added to the domain controller. According to the previous steps, after entering the full name of the DNS in the “Logo Change” dialog box, the domain name does not appear. “domain username and password” dialog, but pops up a warning message "Security error ……”". Considering that this machine is the same as the previous ones, and the system has been working so far, it basically eliminates the possibility of hardware and system errors. So is the DNS resolution error? Because according to past experience, the main reason for not being able to join the domain controller is the DNS problem. Enter “cmd” in the “Run” dialog box, then enter “ipconfig/flushdns”Enter, "ipconfig/registerdns” Enter in the “Command Prompt window", the purpose is to clear the DNS And re-apply for DNS. After the operation is complete, the domain has not been successfully joined. Is the DNS server itself a problem? One does not endlessly, this time completely removed the DNS server in the "add/remove program" and re-installed it again. But after the restart was set, the facts made a joke with me.
Helpless, I only have access to the Internet for help, and found the problem with the help of enthusiastic friends. It turns out that the operating system cannot resolve the domain name properly and cannot join the domain controller properly. The solution is to use the NetBIOS method. After knowing the reason, enter “work" in the "Identification Change" dialog"domain” column, you can wait for more than a minute, and the system will jump out of the hateful warning box again. This time I was completely desperate. At this time, the colleague at the side said: "It's almost 12:15, and let's talk about lunch!" "rds." & ldquo; 12:15? & rdquo; No. Although it has been delayed for some time, it is not so fast. Looked at the watch, only 11:50. I smiled and said to my colleague: "Don't be kidding, it's not enough at 12 o'clock." You have to eat first and leave. ” Colleagues are ignorant: "Who is joking with you, are you watching the computer at 12:16?", along the direction of his finger, the time in the lower right corner of the display is 12:16. . I thought my watch was slow, but after seeing other computers, I found it very punctual! At this moment, my mind flashed a ray of light. Could it be that the problem of not being able to join the domain controller is here? I hurriedly adjusted the time of this client. Time to synchronize with the DC server, enter again. Oh! Successful. I did not expect a colleague's unintentional language to solve a difficult problem.
Afterwards, I checked the information and found that the client's time must be synchronized or slower than the DC service for 1 minute (but not more than 10 minutes). It seems that solving problems can't just look at the surface, but also pay attention to some details or places that are easy to be negligent. Of course, it is necessary to read more information.