Re: question on SIDs and file rights

From: BS (bs_wtf_123_at_yahoo.com)
Date: 02/12/04


Date: Thu, 12 Feb 2004 11:07:46 -0800

Chris-

Sounds like a big mess. You are probably looking at SIDs because the
associations/mappings were lost. You will need to reconfigure the security
by adding the users and permissions again.

My recommendations:

1. Change the main folder to share to Authenticated Users and keep read
only.

2. The subfolders don't need to inherit in this case. Instead, manually
specify the permissions you need and uncheck the inherit box.

3. Instead of adding users to each of the folder permissions, you should
create some local groups that can contain the users. For instance, create a
"Sales" group and give the "Sales" group rights to a subfolder.

Based on the information you provided, it sounds like you'll have to be
assigning permissions all over again.

"chris" <anonymous@discussions.microsoft.com> wrote in message
news:eb2001c3f0f1$3f67aed0$a001280a@phx.gbl...
> We have a 2000 server sp4 that has 2 drives, both NTFS, C
> and D.. C was the OS and D has all the data. We had to
> reinstall the OS on the box but was able to leave all of
> the data intact. When we try to assign rights to the data
> after the reinstall we are having all kind of problems
> that we didn't have before.
> The server is setup in a workgroup with accounts created
> locally for all of the users.
> We shared a folder with everyone group read only on the D
> drive with sub folders in it.
> each sub folder has different security so we removed the
> rights to everyone and only gave rights to users who
> needed it.
> when we went to map the drive non of the users had any
> rights to the main shared folder. we had to add the
> Everyone group and then that messed up the access to the
> rest of the folders. If we removed the inherited rights to
> the other folders they lost access again.
> When we tried to remove the everyone group we saw the RAW
> SIDs instead of names of accounts.
> how do we
> #1. fix it so we are not looking at the SID but a user
> name.
> #2. What could the issue be with the security? why do I
> have to have the group Everyone on all the shared sub
> folders.
> This is a clean install of 2000 with all the latest
> updates.



Relevant Pages

  • Re: Network access not working
    ... your posting again now i understand:-) ... confers no rights. ... are your root folder permissions the same on ... private at all and only copied the security info for public for the ...
    (microsoft.public.windows.server.security)
  • Re: Network access not working
    ... This posting is provided "AS IS" with no warranties, and confers no rights. ... are your root folder permissions the same on ... private at all and only copied the security info for public for the ...
    (microsoft.public.windows.server.security)
  • Re: Network access not working
    ... Maybe the account doing the robocopy does not have sufficient rights. ... are your root folder permissions the same on both sides of the copy? ... The first was that is did not copy the security information for private at ... subfolders were copied but it did not copy any files. ...
    (microsoft.public.windows.server.security)
  • Re: Network access not working
    ... This posting is provided "AS IS" with no warranties, and confers no rights. ... are your root folder permissions the same on both ... private at all and only copied the security info for public for the ...
    (microsoft.public.windows.server.security)
  • Re: Network access not working
    ... no rights. ... The first was that is did not copy the security information for ... I was testing with a much smaller folder set. ... In some of the subfolders of this folder are files and subfolders ...
    (microsoft.public.windows.server.security)