NOVELL TECHNICAL INFORMATION DOCUMENT

TITLE:  Duplicate RIDs/Names in Domain
TID #:  2952270
README FOR:  DUPRID.EXE

NOVELL PRODUCTS and VERSIONS:
NDS for NT 2.0
NDS for NT 2.01

ABSTRACT:

This is a set of utilities to check for duplicate RIDs and Names on an NDS for
NT domain.  See the issue description for information about when this situation
may occur.  


-----------------------------------------------------------------
DISCLAIMER
THE ORIGIN OF THIS INFORMATION MAY BE INTERNAL OR EXTERNAL TO 
NOVELL.  NOVELL MAKES ALL REASONABLE EFFORTS TO VERIFY THIS 
INFORMATION.  HOWEVER, THE INFORMATION PROVIDED IN THIS DOCUMENT 
IS FOR YOUR INFORMATION ONLY.  NOVELL MAKES NO EXPLICIT OR IMPLIED 
CLAIMS TO THE VALIDITY OF THIS INFORMATION.
-----------------------------------------------------------------


INSTALLATION INSTRUCTIONS:

Extract to a subdirectory.  Run the DUPRID and DUPNAME utilities on the PDC in
the redirected domain.  If there are any duplicate rids or names it will be
necessary to delete these users.  Once all duplicate names and RIDs have been
deleted copy the IWSAM.DLL to the WIN32\SNAPINS directory and the IWSAMR.DLL
and IWSAM.HLP files to the WIN32\NLS\ENGLISH directory of all servers (NT or
NetWare) from which NetWare Administrator may be run.  Then re-add the users to
domain using NetWare Administrator.

SYMPTOM:

Using NetWare Administrator running the NDS for NT Snap-in (IWSAM.DLL) that
shipped with NDS for NT 2.0 to administer users from a workstation running the
Novell Client for Windows NT v 4.6 or higher and the Novell Client for Windows
95/98 3.1 and higher can cause an issue where two users have the same relative
identifier  (RID).  This results in users having access to other user's
resources as well as seeing the first users properties when viewing either user
from User Manager.  In addition duplicate names can exist in the event that you
have two users with the same common name and different lettercase (ie USER and
user) in NDS and you attempt to add them both to the domain.

This problem does not occur with the NDS for NT 2.01 snap-in.  However, if the
NDS for NT administration tools are not updated on all servers to the 2.01
version has a potential for this problem still exists.


SOLUTION: 

If you will be using the latest Novell Client to administer NDS for NT 2.0 then
it is necessary to use the snap-in from NDS for NT 2.01.  This snap-in must be
installed on all NT and NetWare servers where NetWare Administrator is run
from.  NDS for NT 2.01 is a free upgrade available at
http://www.novell.com.download. However in the event that it is not feasible to
upgrade the product at this time these files can be obtained by downloading
DUPRID.EXE from http://support.novell.com.  In addition to the updated snap-in
this file also contains utilities for identifying the issue.  If this set of
utilities identifies duplicate RIDs or Names it is necessary to remove them
from the domain and then re-add them using the new snap-in. 

The cause of this problem is a change in the Novell Client Libraries which
resulted in the snap-in querying replicas other than the Master of the domain
object to obtain the IWS:RID counter attribute during user creation.  The new
snap-in forces the new libraries to retrieve this attribute from the Master
replica.  This has the desired effect of ensuring that the RID counter is
always incremented and that since this is the only replica read it will always
be up to date.
 

Self-Extracting File Name: DUPRID.EXE

Files Included            Size          Date            Time
..\
      DUPRID.TXT   (This file)  
       IWSAM.DLL        622592     4-12-1999      2:12:50 am
..\NLS\
       IWSAM.HLP         98420      4-4-1999     10:42:48 pm
    IWSAMRES.DLL         94720     4-12-1999      2:12:58 am
..\UTILS\
     DUPNAME.EXE        111184      6-4-1999     10:49:46 am
      DUPRID.EXE        110820      6-4-1999     10:38:28 am



-----------------------------------------------------------------
Any trademarks referenced in this document are the property of their respective
owners.  Consult your product manuals for complete trademark information.
-----------------------------------------------------------------