Reasons and solutions for slow computer login domain

Windows 2000/XP client is very slow when logging in to the Windows 2000 domain. The main reason is that when the domain user enters the username and password in the login dialog, the login dialog is gray, and it will last for a long time, like losing response ( Normally, the login window flashes. The login process and startup process are significantly longer than normal.

Analysis of the problem

From the performance of the phenomenon, it seems that the client did not contact the domain controller very quickly, because after entering the user name and password, there is no reaction, so why is it not? Soon to contact the domain controller? Because the Windows 2000/XP client logs in to the domain, it first finds the DNS server according to its DNS settings to find the SRV record in the DNS server, and finds the location of the domain controller (so there is no direct setting of the domain controller address in the client). The place)) From this login process, the client did not contact the domain controller in time because it did not find the SRV record of the domain controller in the Dns server.

Then why is Windows 98 not so slow when logging into the domain? Originally Windows 98 (also including Windows NT 4.0 and Windows 95) does not rely on DNS name resolution services like Windows 2000/XP. It still uses NetBIOS for name resolution to find domain controllers, but still recommends you. Point all computers to the Windows 2000 DNS server for name resolution so that the boot process and login process are faster.

According to the above analysis, my client's DNS address is definitely not the Windows 2000 DNS server for the domain controller (this domain controller is also the Dns server in the domain), and so is the case. I set the client's DNS to be a web server, because I can share the Internet, but there is a problem when logging into the domain.

Problem Solving

Since the cause of the problem has been found (now I think it is the reason ^o^), how can I solve it? Because the DNS setting when surfing the Internet is different from the DNS setting when logging in to the domain, the DNS needs to be set as the Internet server when logging in. When logging in to the domain, it needs to be set as the domain controller, and we cannot combine the Internet server and the domain controller. First, is there no other way?

Although the two servers can't be combined into one, can you bridge the bridge between them? This thought, I reminded of the DNS forwarding function, so as long as the client's DNS points to the domain controller that Dns server, the domain name resolution windows 2000 DNS itself is fixed, and the Internet can not be resolved on the Internet Give the Internet server, is this not enough?

Then enter the setting page of the windows 2000 Dns server on the domain controller, and want to add the IP address of the Internet server to the forwarder list. The result is that the "forwarder" label is gray and cannot be set. ! My God, it seems that the sky is going to die, and I am not using it! But if you don't think about it again, Microsoft will not be idle and give it to this setting page. Since he gave it, it has its usefulness. So I calmly looked at this gray page and found a diplomatic statement: "Because this is the root server, there is no forwarder"; the "root hint" label is also gray, suggesting that "because this computer is A root server does not require root hints." That's it! Actually, the Windows 2000 DNS server installed by default is a root server. It is really a village. It seems that the solution is to make it not the root server, but it can not affect the DNS query in the domain, so delete the "." Area, restart the Dns server, and then pass the simple query and recursive query, it seems that the domain outside the domain analysis is no problem, immediately test on a client, can also normal Internet access, OK, the problem is solved, reach The login domain and the Internet are correct.

Summary of Points

First, the DNS service is an essential service of the Windows 2000 domain, and it is an integral part of it. The DNS of the computers in the domain should point to the domain. Service windows 2000 DNS server.

Second, when we install the first domain controller, it will automatically ask to install the DNS service, but the default installed DNS service contains the "." area existing under the forward search area, usually It should be removed, otherwise the external name resolution of the root server could not be performed on the Internet. In this case, the domain controller's DNS should be set to itself.

Third, the relationship between the preferred service DNS server and the alternate Dns server: If there is only one network connection (such as a network card), then only the preferred DNS server will respond to the alternate DNS server if it does not respond, if DNS is preferred The server responds, even if it is the wrong response, it will not request the alternate DNS server. This is why when I did not delete the "." area, I set the preferred DNS server as the domain controller and the standby DNS server as the backup. The reason why the Internet server is not successful - if the domain controller is not turned on at this time, that is, when it does not respond, the client will request the alternate DNS server, and then the Internet can be accessed. If there are two network connections—such as two network cards or one network card and one dial-up connection—the preferred DNS server will not be able to resolve it and will query the alternate Dns server.

Fourth, another solution to this problem is that you do not need to set up a forwarder, but set the gateway of the domain server (also Dns server) as the Internet server. This is because when you want to resolve a name on the Internet, it can't find the record on this server, it will automatically enable the root hint, and then find the root server through the gateway, so that it can be parsed, no matter which kind Method, the DNS settings of the domain controller should point to themselves (running DNS itself).