Discussion Locked

2k Perms vs Netware

0 helpful
5 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Howdy folks.

Got a question on permissions in Win2k vs Netware. It seems tha Netware denies people access from the share level by default, and that a person must be granted access explicitly. While Microsoft does the opposite and allows everyone full control by default at the share level. To clarify: In Netware, if I want to create the following share: serverX\vol1, people can map to this share, but their access is restricted by default. Whereas with Microsoft, the share name serverx\programs must be shared with everyone-fullcontrol permissions in order for them to gain access to it, which would seem open the share up to all sorts of access to the users. The appropriate step to take after the sharing obviously is to restrict the directories under the share on a case by case basis.

Is this correct?

5 replies

by pgm554

By default, the only directories that Novell will give a user access to are their home directory with full rights and Sys: public with read, write and file scan. The default map command gives the users those mapped drives when they initially log in (usually H :( home dir) and F :( SYS: public)).

All other directories and files are hidden unless you specifically give them rights which are subject to your interpretation (usually read, write and file scan).

Rights flow down from the top of the directory in Novell unless you specifically mask them out.

Take as an example a human resources directory, depending upon who is using the application, you want to give them access to the data, but you don?t want them to modify it unless they are a member of a specific group, so you would mask out the modify right to that sub-directory, and unless they belonged to that specific group ,they would not be able to modify anything in that sub-directory.

by curacao_dejavu

with MS the default share permission is indeed everybody full control, but the share perissions can be change to what you need.
Then you have to restrict the underneath permissions indeed. Also a trick that most people forget to use is the list permission. If you have a share and underneath a lot of folders but the user don't need access to all of them, if you apply the list permission to their group, they see only what they need to see/use. And of course those your restict.
Remember the sum of a user access is the the least restrictive between a share and a folder permission access.
for example a share access of read and a full folder access, sums to be a read access.

Leopold

This discussion is closed to new replies.