, another Windows 7, too, to join the domain process is the same, have normal operation, on the other two xp DNS also points to the DC machine, on the Internet to find some kind of, what the TCP/IP Helper service, RemoteRegist services, set in the Microsoft client, network CARDS, all open, and the local DNS cache is cleared (ipconfig/flushdns), submit an application to join after the prompt have permission to join the domain administrator account and password, I think this step, should be network Settings, there is no problem, (password is no input errors, otherwise the prompt will be account error) Please help analysis, is a cause, where the problem is the Windows 7 and 2008 machines, xp but don't worry,
CodePudding user response:
Domain controller in the process of ascension is easy to appear problem, the most problematic is the DNS, it is come out when we do the experiment, the solution is as follows: on the domain controller run ipconfig/registerdns no space (note that in the middle), and then run gpupdate/force to enforce the refresh strategy, basically can solve the problem,The most important of all, your client's DNS server address to enter the IP address of the domain controller, this must not be wrong!
CodePudding user response:
Look at the log C: \ Windows \ debug directory netsetup. Log detailed information,CodePudding user response:
problem has been solved inadvertently,Search on the net for many days, various measures have been tried, and finally there is a post referred to in the "network sharing center" open "network discovery", combined with error: can't find the network name, also related to "network discovery" feature, try to open the "network" look for network resource, bring up a red fork error, the effect is "can't find the network resources, such as" prompt, then opened up the function, but also opened the file and print sharing, (as if he had been to restart the domain controller, do not know to have relationship) to join the domain again incredibly successful,
Later want to restore the error, in order to confirm the reason, but found that even turn "network discovery" feature, "network browsing is not affected," didn't pop up the red fork mistake, once again at the same time to join the domain of time also is very normal,
And on the virtual machine installed a Windows 7, preview, "network discovery" feature is open, try to join the domain, the result at a time,
Taken together, should is the "network" function is not open to "can't find the network name" mistakes, but the function which is the corresponding service? Also is why turn off this feature, but they cannot restore the mistake? Is it "discovered" a cache the results? I don't know what idea you have,