Nltest Tool Does Not Work When You Reset the Secure Channel Using NetBIOS Computer Name

This article was previously published under Q260889
This article has been archived. It is offered "as is" and will no longer be updated.
When you attempt to reset the secure channel by using the NetBIOS name of the domain controller, the Nltest tool (Nltest.exe) does not work with the following syntax:
nltest /sc_query:domainname[\Dcname]
In addition, the following error message is displayed:
I_netlogonControl Failed: Status=1311 0x51f ERROR_NO_LOGON_SERVERS
You can reset the secure channel by using the Fully Qualified Domain Name (FQDN) of the domain controller. This prevents the ability to reset a secure channel to Microsoft Windows NT 4.0 domain controllers.
When you reset the secure channel, Windows 2000 only checks the FQDN of the domain controller and not the NetBIOS name.
To resolve this problem, obtain the latest service pack for Windows 2000. For additional information, click the following article number to view the article in theMicrosoft Knowledge Base:
260910 How to Obtain the Latest Windows 2000 Service Pack

Microsoft has confirmed that this is a problem in Windows NT 4.0. Microsoft has confirmed that this is a problem in Microsoft Windows 2000.

This problem was first corrected in Windows 2000 Service Pack 1.
For additional information about how to install Windows 2000 and Windows 2000 hotfixes at the same time, click the article number below to view the article in the Microsoft Knowledge Base:
249149 Installing Microsoft Windows 2000 and Windows 2000 Hotfixes

Article ID: 260889 - Last Review: 12/05/2015 19:56:07 - Revision: 3.2

Microsoft Windows 2000 Server, Microsoft Windows 2000 Advanced Server, Microsoft Windows 2000 Professional Edition

  • kbnosurvey kbarchive kbbug kbenv kberrmsg kbfix kbqfe kbwin2000sp1fix KB260889
ERROR: at System.Diagnostics.Process.Kill() at Microsoft.Support.SEOInfrastructureService.PhantomJS.PhantomJSRunner.WaitForExit(Process process, Int32 waitTime, StringBuilder dataBuilder, Boolean isTotalProcessTimeout)