Active Directory and ASU folder permissions...

Dear ASU experts,

We have recently migrated to Windows 2003 Active Directory. One of our
Alpha Clusters (running Tru64 v5.1 and Compaq Advanced Server V5.1A ECO3
for UNIX) has permissions assigned to various shares / folders on these
Unix machines. During this migration, we also changed the ASU role on
the 2 cluster members, from a BDC to be member servers though the
earlier granted permissions have not been affected.

Following this I noticed that though I can view the ASU folder level
permissions using "net access c:....", I cannot change it (grant /
revoke). This is possible only through my PC's Windows 2000 explorer
utility under the security tab.

Also, I noticed that when selecting any of the cluster's Unix folders
and viewing its security properties, it does not display the name of the
user concerned but only the relevant SIDs. Though I am aware of indirect
ways of matching the SID to specific username to grant / revoke
permissions, it is a painful exercise. It may be noted that in case of
other Windows Servers' folders, the usernames are displayed and not the
SIDs.

Are you aware of any setting in ASU (probably using its lanman.ini or
something else), whereby I can see the username displayed instead of its
SID, when accessing the folder security in my client's explorer utility?

Would appreciate a prompt reply. Thanks.


Harihar K



Disclaimer:
[This communication is intended solely for the named recipient and others authorized to receive it. It may contain confidential or legally privileged information. If you are not the intended recipient, please notify us immediately, and note that any disclosure, copying, distribution or action you may take in reliance on this communication is strictly prohibited and may be unlawful. Unless indicated otherwise, this communication is not intended nor should it be taken to create any legal relations, contractual or otherwise. Bahrain Monetary Agency(BMA) is neither liable for the proper and complete transmission of the communication, nor for any delay in its receipt. Whilst BMA undertakes all reasonable efforts to screen outgoing e-mails for viruses, it cannot be held liable for any viruses transmitted by this  e-mail].