Error Message: A Controller for This Domain Could Not Be Found
Article ID: 184538
Article Last Modified on 11/1/2006
APPLIES TO
- Microsoft Windows NT Server 4.0, Terminal Server Edition
- Microsoft Windows NT Server 4.0 Standard Edition
- Microsoft Windows NT Workstation 4.0 Developer Edition
- Microsoft Windows NT Server 4.0 Enterprise Edition
This article was previously published under Q184538
SYMPTOMS
When you attempt to add computers to a domain during Windows NT Setup
after you have installed the updated Lsasrv.dll file (Lsa-fixi.exe or Lsa-
ixa.exe) on the Primary Domain Controller (PDC), you may receive the
following error message:
A controller for this domain could not be found.
CAUSE
The behavior occurs because the updated Lsasrv.dll file (Lsa-fixi.exe or
Lsa-fixa.exe) implements the new registry item called RestrictAnonymous
that restricts the use of Null NamedPipes. Windows NT Setup uses a Null
NamedPipe for the connection to the server to verify the domain. The Null
NamedPipe is returned with access denied because RestrictAnonymous has
been used on the PDC.
RESOLUTION
To resolve this problem, obtain the latest service pack for Windows NT 4.0 or Windows NT Server 4.0, Terminal Server Edition. For additional information, click the following article number to view the article in the
Microsoft Knowledge Base:
152734 How to Obtain the Latest Windows NT 4.0 Service Pack
STATUS
Microsoft has confirmed that this is a problem in Windows NT 4.0 and Windows NT Server 4.0, Terminal Server Edition. This problem was first corrected in Windows NT 4.0 Service Pack 4.0 and Windows NT Server 4.0, Terminal Server Edition Service Pack 4.
Keywords: kbbug kberrmsg kbfix kbqfe KB184538