Resolved Sharing Root Dir vs SubDir Issue (XPWin)

Hi mates

Situation
1 PC1 is in a WorkGrp running on XPWin Prof SP3 with simple sharing off.
2 Other PCs in the same WkGrp runs on XPwin Home SP2/3.
3 Root of PC1 (CR) is shared for reading only by EveryOne
4 Sub Folder of CR (SF) is shared for full control by EveryOne.

Thus
When users of other PCs remote accessing PC1, they can see all the folders in CR and since CR is readonly, no writing is possible on CR. The subFolder SF if access from CR, writing is also not allowed.
HOWEVER
if SF is access directly (since it is shared as full Control), writing is allowed.

QUESTION
How can i make SF writeable if access from within CR?

 

You make the share access read/write and then set up file permissions so that other users only have write access to the SF folder.

However, giving everyone remote access to the root is always a bad idea. It is always better to dedicate areas for sharing and only share those areas of the file system.

 

Thanks ReggieB again

Fully agree that Root should not be shared; this principle is frequently posted on this forum. I have my reasons to allow ONLY viewing of the root; thus any writing, deletion, etc are forbidden. Are you suggesting that PC1's root be read/write ( *u write 'You make the share access read/write'); if so then it is not acceptable.

 

When you right click on the properties of a folder, you'll find there are two places where you can set permissions:

1. The Sharing Tab: This controls what permissions are allowed via a share.
2. The Security Tab: This controls the permissions at the file level.

The easiest way to explain the difference between the two, is to think of your hard drive as if it was a warehouse.

In this analogy, the share permission is the control set on people as they pass through the door into the warehouse.

The file permission determines what access each person has to each container within the warehouse.

So someone wanting to access something in the warehouse must first have permission to enter the warehouse (the share permission), and then have the specific permission to access the thing they want (the file permission)

What I am suggesting is that you set the share permission to read/write. So people entering the warehouse will be able to leave with objects they have permission to take (if you set the share permission to read only, they would not be able to retrieve items even though the file permission was sent to read/write - they could pick it up in the warehouse, but the guard on the door would not allow them to take the object through the door.)

Then control which file/folders (objects) they can access via the file permission. So set the file permission at root level to read only. Then set the file permission to read/write only on the folder you want to allow them to write to.

One proviso: this will only work if remote users are not using the same user account as the person who logs onto the PC directly. If a remote user only has read file access to a PC, when they log into the PC directly they will have problems running the PC.

The best solution would be to create a user group containing all the remote user accounts. Then set file and share permissions for this group as I describe above.

 

Big Thank you. Period!

MANY THANKS for the CLEAR enlightment.

A further variation which i have since adopted is to name folder in C:\ root eg \\Srv\SF as "C ". Then all other folders that need to be shared by other users is kept as sub folders in this SF. Thereafter apply the sharing & file permissions you highlighted in your last message.

With this, users accessing "C" will think they have access the server's root drive while infact they only access \\Srv\SF.

Cheers!

 

You're welcome