CACLS Not Resolving Principle Names Correctly (183718)
The information in this article applies to:
- Microsoft Windows NT Server 4.0 Terminal Server Edition
- Microsoft Windows NT Server 4.0
- Microsoft Windows NT Workstation 4.0
This article was previously published under Q183718 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.
RESOLUTIONTo 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
STATUSMicrosoft 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.
| Modification Type: | Minor | Last Reviewed: | 9/23/2005 |
|---|
| Keywords: | kbHotfixServer kbQFE kbbug kbfix KB183718 |
|---|
|