W2K3 WORKGROUP share permissions problem

[Guest dubh@vodafone.ie]

I've set up a lab to do some basic testing involving moving shares to

AD. On the stand-alone (workgroup) server I've set up some shares with

various permissions. The permissions need to satisfy the following

criteria:

 

1. allow only read access to members of certain groups.

2. allow read and write access to members of certain groups.

3. allow full-control to members of certain groups to any files or

folders they create within a specified share.

 

Steps 1 and 2 work fine (as they shoud); however, I cannot get a user

belonging to the 3rd group to control access etc to any folders he

creaes on a share. I've tried every possible combination of Share

Permissions and NTFS Security short of allowing full ANONYMOUS access

to the whole drive. Can anyone shed light on this or am I missing

something obvious???

 

Thanks

 

Brian

[Guest lforbes]

RE: W2K3 WORKGROUP share permissions problem

 

Hi,

 

If you look at the default permissions on C:\ of any Windows XP machine it

will give you an idea.

 

Add the user CREATOR/OWNER and give it Full Control of all subdirectories

and files (usually default permission). This means anyone who creates a file

or folder will get full control of that file/folder.

 

Cheers,

Lara

 

"dubh@vodafone.ie" wrote:

> I've set up a lab to do some basic testing involving moving shares to

> AD. On the stand-alone (workgroup) server I've set up some shares with

> various permissions. The permissions need to satisfy the following

> criteria:

>

> 1. allow only read access to members of certain groups.

> 2. allow read and write access to members of certain groups.

> 3. allow full-control to members of certain groups to any files or

> folders they create within a specified share.

>

> Steps 1 and 2 work fine (as they shoud); however, I cannot get a user

> belonging to the 3rd group to control access etc to any folders he

> creaes on a share. I've tried every possible combination of Share

> Permissions and NTFS Security short of allowing full ANONYMOUS access

> to the whole drive. Can anyone shed light on this or am I missing

> something obvious???

>

> Thanks

>

> Brian

>