fcaat
asked on
Resolving Account Unknown
Hello,
When going through the security permissions on some of the objects in AD seeing some Account Unknown(S-1-5-21-*). My question is how can i resolve these to readable account names so i can find out whether there is a purpose to having these in there.
Easiest way possible would be great.
Thanks.
When going through the security permissions on some of the objects in AD seeing some Account Unknown(S-1-5-21-*). My question is how can i resolve these to readable account names so i can find out whether there is a purpose to having these in there.
Easiest way possible would be great.
Thanks.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
you cannot find because it doesn't exist any more
surely you won't need it :)
surely you won't need it :)
ASKER
i know there is a way you can resolve sids to common names. i am not sure how to do it though. that is the question that i asked.
http://www.securityfocus.com/tools/544 for exemple
there are 2 tools named sid2user and user2sid
there are 2 tools named sid2user and user2sid
as map000 sayd, you cant resolve deleted accounts.
these tools are only for active user accounts.
if you give access for a user, his sid is entered in the access list of the directory/file.
if you delete this user, it will not delete this entry in the access list.
this is what you are seeing.
non of this tools will give you an account for this sid.
these tools are only for active user accounts.
if you give access for a user, his sid is entered in the access list of the directory/file.
if you delete this user, it will not delete this entry in the access list.
this is what you are seeing.
non of this tools will give you an account for this sid.
If the user account has been deleted, there will be no mapping to a common name - thus, your SID entry.
Two reasons you see this are because a user account was added directly to an ACL on an object instead of using groups. By assigning permissions to groups you eliminate this problem.
and
If the SID cannot resolve to a name due to network issues - an example is a user from another domain and for some reason it cannot contact the PDC for that domain to resolve it's common name.
Two reasons you see this are because a user account was added directly to an ACL on an object instead of using groups. By assigning permissions to groups you eliminate this problem.
and
If the SID cannot resolve to a name due to network issues - an example is a user from another domain and for some reason it cannot contact the PDC for that domain to resolve it's common name.
ASKER
is there any way to find out what the sid was ... can you translate the sid even if the user account has been deleted. Just so you can know for sure whether or not its a network issue or just the user has been deleted.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER