CACLS Not Resolving Principle Names Correctly

This article was previously published under Q183718
This article has been archived. It is offered "as is" and will no longer be updated.
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 locatedon 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 viewthe 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 theMicrosoft 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: 10/26/2013 05:27:00 - Revision: 3.0

Microsoft Windows NT Server 4.0 Standard Edition, Microsoft Windows NT Workstation 4.0 Developer Edition

  • kbnosurvey kbarchive kbhotfixserver kbqfe kbbug kbfix KB183718