Users are unable to map drives to directories with explicit rights.

(Last modified: 23May2005)

This document (10097763) is provided subject to the disclaimer at the end of this document.

fact

Novell NetWare 6.5 Support Pack 2

Novell NetWare Cluster Services 1.7

symptom

Users are unable to map drives to directories with explicit rights.

Adding Filescan rights to the Volume object for the user or user's container allows users to map to their directory.

change

Upgraded Cluster from NetWare 5.1 SP6 to NetWare 6.5 SP2.

cause

The volume's Visibility List is invalid. 

fix

 Run NSS /VisibilityRebuild=<volume> on the volume experiencing the failure.  In doing this all visibility lists are erased at each junction and they are repopulated from the trustee list in the beast.

note

Information on Visibility Lists

The Visibility list is only used for making parent directories visible for navigation purposes. If a user has rights to a file, the NCP^TM (via NCP Server for NetWare or NCP Server for Linux) makes all directories above the file visible to the user. This saves the administrator the task of assigning explicit rights to each directory above where the actual rights are assigned.

Visibility entries are stored in a manner similar to explicitly-assigned trustees. The first four entries are in the actual beast object; the rest are stored in overflow beast objects linked from the directory beast object.

Visibility lists only appear on directories. There is one entry for every trustee assigned anywhere in the subtree below the directory. Therefore, the further toward the root you go, the more GUIDs you see against that directory. At the root, the list has GUIDs for every trustee on the volume.

Each visibility entry has an eDirectory GUID and a count of the number of references to that GUID in the entries for the directory (not the subtree) where the Visibility list is assigned. This includes trustees that are explicitly assigned, as well as trustees in Visibility lists.

A Visibility list entry can be created in one of two ways:

• An immediate subordinate directory or file has a trustee that the parent does not.
  
• A visibility entry for a subordinate subdirectory is present.

Visibility counts do not consider trustees from directories or contents of directories that are not immediately subordinate to the considered directory.

The Visibility list is not affected by adding, deleting, or modifying IRMs. These operate in a transverse flow to the Visibility list. In other words, IRMs flow down the directory structure, while the Visibility list works up the structure.

For each request, GUID entries in the connection table are compared for the connection requesting against all GUIDs on the directory in question. If a match is found, the directory is made visible to the user in the Visibility list.

document

Document Title:	Users are unable to map drives to directories with explicit rights.
Document ID:	10097763
Solution ID:	NOVL102191
Creation Date:	23May2005
Modified Date:	23May2005
Novell Product Class:	Netware

disclaimer

The Origin of this information may be internal or external to Novell. Novell makes all reasonable efforts to verify this information. However, the information provided in this document is for your information only. Novell makes no explicit or implied claims to the validity of this information.
Any trademarks referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information.