Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 265
  • Last Modified:

Basic file sharing question for W2K3 Server

I feel like an idiot asking this question but something so simple and basic is driving me insane.

I come from a Netware world where creating a "GROUPS" folder and then creating/sharing the individual group's folders is very easy. It's all done from the top down so that I can map a drive the the top of the directory structure (e.g. G:\GROUPS) and then depending on the users rights they will see other folders for their specific group inside the G:\ drive.

With Windows Server 2003 Standard using AD I am having a hell of a time recreating this setup. All I want to do is map a drive for each user to the top of the directory structure (G:\GROUPS) and let them see what is inside. If they belong to an AD group that has permissions to the folders beneath they can either read only or read/write to them. I have spent the past few hours trying every combination of share permissions, security permissions, inheritance crap and so forth.

Here is what I am trying to do:

C:\FILESERV - is the top of my shared directory structure

C:\FILESERV\GROUPS - is shared with "Everyone" having read only rights

C:\FILESERV\GROUPS\Accounting - is not specifically shared but has rights for the "Accounting" group to read/write (even tried full access)

What is happening is that members of the "Accounting" group and everyone else can see the folder but if you try to write to it, it fails. if I go back up to the "GROUPS" folder and give "Everyone" the "change" permission under sharing, everyone can write to it.

What on Earth am i doing wrong? This should be so simple!
0
jasonsfa98
Asked:
jasonsfa98
  • 6
  • 4
  • 3
  • +2
1 Solution
 
tigermattCommented:
You're not assigning Full Control permissions to the Everyone group on the Share permissions level. Since the most restrictive permissions will always apply - and you get a lot more control over what actions a user can take by using NTFS permissions - using share permissions is virtually useless.

Give the Everyone group full control in the Share permissions on EVERY share you create is the easiest way to do it. The permissions on the Security tab will still be applied to connections to the share, despite making this change.

-tigermatt
0
 
jasonsfa98Author Commented:
Ok. So I added the Full Control permission at the top (C:\FILESERV\GROUPS). Then, I created a folder inside that one named "Accounting". I didn't assign any share permissions but added the Accounting group to the Security tab. I gave the Accounting group full control and "Users" read only.

I am still able to write to the directory no matter who I am.

-C:\
 |_
     C:\FILESERV
     |_
          C:\FILESERV\Accounting <--- This one should be read by all but only written to by the Accounting group.
0
 
tigermattCommented:
Sorry I misread it and thought it said you couldn't write!

Can you please list all the users/groups on the Security tab along with a brief summary of the permissions they are granted. Don't forget that if a user is a member of two groups, their permissions are based on the permissions granted to both those groups.
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

 
QlemoBatchelor, Developer and EE Topic AdvisorCommented:
I agree. Only if you want to have ReadOnly-Shares versus ReadWrite-Shares (same folder, different names), there might be a sense in setting up share permissions. In any other case it is like begging for trouble ...
0
 
Andres PeralesCommented:
You also have to remember if you are a Domain admin, or have admin right you will be able to do all of it with that account...you should also be testing it from the sharing unc not the directory so

\\fileserv\
\\fileserv\accounting

then check from a normal account.
0
 
jasonsfa98Author Commented:
peralesa: I am using an account that is a member of the Accounting group to test all this. I then remove them from the group to see if the ability to write is taken away and it's not.

Responding to Tigermatt shortly ...
0
 
jasonsfa98Author Commented:
tigermatt,

C:\FILESERV\GROUPS:

Security Tab
Administrators - Allow Full Control
CREATOR OWNER - Allow Special
SYSTEM - Full Control
Users - Read & Execute, List Folder Contents, Read


C:\FILESERV\GROUPS\Accounting:

Security Tab
Administrators - Allow Full Control
Accounting Group - Allow Full Control
CREATOR OWNER - Allow Special
SYSTEM - Full Control
Users - Read & Execute, List Folder Contents, Read


Current Situation: Anyone and their mother can write to the Accounting directory.

Needed Situation: Only the Accounting group should be able to write/change while all other users should be able to read.
0
 
virtuatechCommented:
Your share, like tigermatt said, should have "Full Control" permissions.  What really matters is the Security tab of the properties of the Accounting folder.  Keep in mind that the Security settings of the C:\ and C:\FileServ...if any of the users have access to those, it will inherit to the subfolders, the Accounting folder.  To get around this you should go to the Security tab of the Accounting folder properties, then click the "Advanced" button and uncheck the "Inherit from parent..." box.  That will exclude all the other users, and only admit the users specified.

I hope that helps :)
0
 
tigermattCommented:
OK, let's start a permission at a time. On the Accounting folder, remove inheritance in Advanced Security permissions, and select the option to Copy permissions. Then, remove each permission one at a time and test using a non-Administrator, non-Creator, non-Accounting user account. When you find the permission entry you remove which stops these people writing files, post back here.
0
 
Andres PeralesCommented:
man you guys are fast was just going to say what tiger and virtuatech were going to say...

share permissions full,

security or NTFS permissions make sure to turn of the inheritance, then remove from there except the groups you want to have full access.
0
 
virtuatechCommented:
Typing Tutor baby, Typing Tutor ;)
0
 
jasonsfa98Author Commented:
tigermatt,

So I did exactly what you said (something I tried many times) and this time I added a Logoff/Logon to the mix and it worked. The user was no longer able to write to the directory. Then, I added the user back to the Accounting group in AD. After that, I logged in as the user and was now able to write again. Even I after I tested it some more with a Logoff/Logon there seemed to be some lag as to how much time passed before permissions were applied. Is this normal?

Do I have to have users Logout/Login every time a group membership is changed?
0
 
Andres PeralesCommented:
There is a lag time sometimes in permissions, there are times where we have changed permissions so many times on a folder, that AD does not have time to catch up...we get up for a break come back and it all works like magic...or the gremlins come and help
0
 
jasonsfa98Author Commented:
peralesa, that is annoying!

I know people think Netware is dead but when it comes to basic file/print services ... MUCH EASIER to work with. Even without the fancy GUI's.

Tigermatt ... thanks man.
0
 
jasonsfa98Author Commented:
This is by the book. This is the same information you can find in the manuals but tigermatt took it step by step and allowed me to discover the problem. He pointed me in the right direction and now all is well. Sometimes you just need another set of eyes.
0
 
Andres PeralesCommented:
<shrugs>
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

  • 6
  • 4
  • 3
  • +2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now