5 replies
by jimbb
You're making a very common mistake I'm afraid. Having read/browse rights to the root and to NDS objects has nothing to do with having access to files and directories. Well, and that is not entirely true either. Anyway.
If you're concerned aboutusers having access to certain directories, you should consider that rights are inherited down the "tree" of directories on your volumes. If you have granted all rights on the volume object, those rights are inherited to the folders and files on the volume.
Check the properties of the volume on which your user directories are, and open the "Trustees of the root directory". Don't confuse with right-clicking the volume-object, and checking the trustees of the volume-object in NDS, there is a difference.
In most cases, the best thing to do is to give everyone no rights or very limited, and grant rights to specific directories further down. For example, no rights on the volume object, no rights on VOL:Users, and RWCEMFA on VOL:Users\user-id. This way you avoid that they can even see their "neighbour's" directory.
And about ROOT and its rights and so, it is normal and even desirable that everyone has at least browse and read-rights. This is used "internally" by NDS, to read things like container login scripts, properties of the server you're using etc.
Jim
by bobrace
3 ways
Way1 Give everyone Full access to the root of the volume (Use filer.exe to inspect this)
Way2 Supervisory Trustee to the server Object in the NDS. Browse the server object, no body but you (the admin) should have supervisory to the server object
Way3 Supervisory to the container (OU or ROOT) where the server is installed. Again browse NDS.
Good luck
by bobrace
by bobrace
This discussion is closed to new replies.
Trending Networks posts
Sort by Trending