Sun Storage 5210 NAS Appliance
 
Sun Storage 5220 NAS Appliance
 
Sun Storage 5310 NAS Appliance
 
Sun Storage 5320 NAS Gateway/Cluster System
 
Sun Storage 5320 NAS Appliance
 
Sun Storage 5310 NAS Gateway System
 

GCS>Sun Microsystems>Storage - Disk>Network Attached Storage
 

• "Cannot access shares"
• "Cannot see shares"

1.  <Document: 1007154.1> Check the NAS system log for messages immidiately after unsuccessfully attempting to access the share. The NAS system log is the best place to start looking for the cause of this issue.
2.  <Document: 1005602.1> Use the autohome feature for user home directories. For environments with user home directories, Autohome shares make the NAS easier to use for both administrators and users.
3.  <Document: 1013073.1> If using Workgroup mode (non-domain), understand the NAS-specific password security. Workgroup mode uses a simpler, password and UID-based system to secure shares. Domain mode is strongly recommended for secure environments.
4.  <Document: 1008490.1> Understand how the default administrative shares are used. For Windows compatibility, a hidden share is created at the root of every user volume on the NAS, plus the system volumes /cvol and /dvol. Users logged in as members of the Domain Admins group can access these shares without any shares being created. A benefit of this is that it is not necessary to create shares at the root of volumes. Creating root level shares is dangerous, as it relies on administrators to secure every directory with permissions to protect them from unwanted access. With this model, shares are created only at the lower level directories needed for each user or group.
5.  <Document: 1011364.1> Troubleshoot individual file and directory access issues with the cacls utility. This command line utility shows CIFS permissions, NFS permissions and extended attributes for files and directories. Also, check the file permissions from a Windows client, as a Domain Admin if possible.
6.  <Document: 1005474.1>  Understand how CIFS access tokens work. If you change group membership or primary group for a CIFS user account, the user must completely disconnect from the NAS in order for the changes to take effect. This is sometimes a challenge. The linked document also describes some useful troubleshooting data that can be collected from the user tokens on the NAS.
7. Understand that the NAS cannot authenticate to an LDAP server in place of a CIFS doamin controller. The NAS LDAP support is currently limited to NIS+ type lookups; e.g. hostgrps, netgroups, etc. A workaround for this is to use a Samba-based domain controller. The NAS is able to use the Samba server for authentication, and newer Samba versions are able to authenticate users via LDAP.
8.  <Document: 1005474.1>  Collect the NAS extractor and diagnostic to prepare for a support case or escalation. The diagnostic collection should be done as soon as possible after the attempt to join the domain.
9.  <Document: 1004130.1> Collect the network trace. Follow the instructions to set up a trace, set the filter to capture traffic between the client attempting to access the share, the NAS and Domain Controller(s). Start the trace, repeat the attempt to access the share, then stop the trace.
10. At this point, if you not been able to resolve the issue with the troubleshooting steps above, further troubleshooting is required. Contact Sun Support and be prepared to provide the data collected in the above steps.

The NAS extractor can be downloaded from PTS web pages and mailed to customer. If your customer experience trouble with NAS extractor you might collect some debugging information and provide feedback to Wayne Taranto who has developed this data collector.

This solution has no attachment