CACLS Not Resolving Principle Names Correctly

Article translations Article translations
Article ID: 183718 - View products that this article applies to.
This article was previously published under Q183718
This article has been archived. It is offered "as is" and will no longer be updated.
Expand all | Collapse all


A user connects to a untrusted domain using NET USE with the /Username:<domain>\<adminuser> option or through Explorer with ConnectAs. The user then attempts to run CACLS to modify the ACLs on the files located on the remote computer. CACLS returns the following error:

No mapping between account names and security IDs was done.

If the ACL is changed using Explorer, and then the user attempts to view the permissions using CACLS, the following error is received:

Account Domain not found.

This message is followed by the new permission.


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


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.


Article ID: 183718 - Last Review: October 26, 2013 - Revision: 3.0
Applies to
  • Microsoft Windows NT Server 4.0 Standard Edition
  • Microsoft Windows NT Workstation 4.0 Developer Edition
kbnosurvey kbarchive kbhotfixserver kbqfe kbbug kbfix KB183718

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from