CACLS Not Resolving Principle Names Correctly

ID: Q183718


The information in this article applies to:
  • Microsoft Windows NT Server version 4.0
  • Microsoft Windows NT Workstation version 4.0
  • Microsoft Windows NT Server version 4.0, Terminal Server Edition


SYMPTOMS

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.


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, please see the following article in the Microsoft Knowledge Base:

Q152734 How to Obtain the Latest Windows NT 4.0 Service Pack


STATUS

Microsoft has confirmed this to be 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 : NT4SP4Fix kbbug4.00 kbfix4.00.sp4 NTSrv
Version : WinNT:4.0
Platform : winnt
Issue type : kbbug


Last Reviewed: April 10, 1999
© 2000 Microsoft Corporation. All rights reserved. Terms of Use.