Behavior when no user mapping exists

When no appropriate user mapping exists, cross-platform access and presentation is limited. UNIX® access to Windows® objects is granted only when Everyone has access. Windows access to UNIX objects is granted only when the other permission bits allow access. (In this case, there is no practical difference between Everyone and other.) Windows objects appear with a user and group ID of 999999 on UNIX. UNIX objects appear to belong to the null SID (S-1-0-0) on Windows. This behavior is consistent with earlier SAN File System releases that did not support heterogeneous user mapping.

This behavior also occurs when a user mapping exists but the metadata servers are not able to access the LDAP directory service.

Parent topic: Heterogeneous file sharing

Library | Support | Terms of use | Feedback
(C) Copyright IBM Corporation 2003, 2004. All Rights Reserved.
IBM TotalStorage SAN File System v2.2