Cluster Administrator Incorrectly Rejects Trusted Domain SIDs as Local SIDs
This article was previously published under Q262705
This article has been archived. It is offered "as is" and will no longer be updated.
In a multi-domain environment with a one or two-way trust, the lookup on account SID may not work when you try to add a global group while you are using a workstation to administer the cluster. Also, validation does not work on existing SIDs in the existing ACL even if you do not add another user or group.
Windows 2000To resolve this problem, obtain the latest service pack for Windows 2000. For additional information, click the following article number to view the article in theMicrosoft Knowledge Base:
260910 How to Obtain the Latest Windows 2000 Service Pack
Windows NT 4.0A supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that are experiencing this specific problem.
To resolve this problem, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:NOTE: In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
The English version of this fix should have the following file attributes or later:
Date Time Size File name Platform ------------------------------------------------------------- 01/02/2000 04:23pm 134KB Cluadmex.dll x86 01/02/2000 04:26pm 730KB Cluadmin.exe x86 01/02/2000 04:22pm 212KB Cluadmex.dll Alpha 01/02/2000 04:25pm 972KB Cluadmin.exe Alpha
Windows 2000Microsoft has confirmed that this is a problem in Windows 2000. This problem was first corrected in Windows 2000 Service Pack 1.
Windows NT 4.0Microsoft has confirmed that this is a problem in Windows NT 4.0.
Article ID: 262705 - Last Review: 11/02/2013 21:48:00 - Revision: 4.0
Microsoft Windows 2000 Server, Microsoft Windows 2000 Advanced Server, Microsoft Windows 2000 Professional Edition, Microsoft Windows NT Server 4.0 Enterprise Edition
- kbnosurvey kbarchive kbhotfixserver kbqfe kbbug kbfix kbwin2000sp1fix KB262705