Sun Microsystems, Inc.  Sun System Handbook - ISO 3.4 June 2011 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-71-1007154.1
Update Date:2009-04-16
Keywords:

Solution Type  Technical Instruction Sure

Solution  1007154.1 :   Sun StorageTek[TM] 5000 Series NAS: Using the NAS System Log to Troubleshoot Problems Accessing CIFS Shares  


Related Items
  • 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
  •  
Related Categories
  • GCS>Sun Microsystems>Storage - Disk>Network Attached Storage
  •  

PreviouslyPublishedAs
209858


Description
When unsuccessfully attemtping to connect to a share, the system log.frequently can give an indication of the problem and corrective action. This document shows the most common share-related log messages and their meaning.


Steps to Follow
Sun StorageTek[TM] 5000 Series NAS: Using the NAS System Log to Troubleshoot Problems Accessing CIFS Shares

To check the NAS system log, connect to the Web Admin and navigate to Monitoring and Notification / View System Events / Display System Log. After a few seconds, the system log will appear.

The log should be checked as quickly as possible after the attempt to access the share, so that the messages from the attempt are easy to find. In the web admin, the most recent messages are found at the top of the screen. The following are messages that could indicate a problem:

token[DOMAIN\User]: CANT_ACCESS_DOMAIN_INFO

This message indicates that the NAS has lost contact with the Domain Controller, and can no longer authenticate. In this case, it will be necessary to re-enter user credentials to re-join the domain. See <Document: 1008222.1>  for details on this process. If unsuccessful in re-joining the domain, see <Document: 1009917.1> . 

user: Access Granted to /share (but still can't access)

The "access granted" message comes from the fact that the security for shares comes from the underlying directory. The NAS supports credentials only on files and directories. If you cannot access a share after this message, the problem is directory security. Check and/or grant the pemissions from a Windows client using an Admin account. The NAS CLI cacls utility can also be used to view security settings. See <Document: 1008222.1> for details.

mlrpc[0x0F]: error: NO_TRUST_SAM_ACCOUNT (0xC000018B)

This message indicates that a user from outside the Domain cannot access the NAS due to a broken or non-existent trust releationship. Trusts are configured on CIFS Domain Controllers from both to allow inter-domain sharing of resources. If this occurs, the trust relationship must be re-established or created between domains. Also, verify that the remote domain controller is available, because a temporary outage can show similar symptoms.

NOTE: Other Windows servers may continue to allow access for some time due to longer caching of user token information. In this case, the problem may appear to affect only the NAS, but the cause and solution remain as documented above..

Share Database Corrupt

This message indicates a problem with the database that contains the CIFS/SMB shares. Typically this can be fixed by repairing the database. The database consists of two files per volume: .shares.db and .shares.idx. Do not use the dbck command unless the above message is logged, unless under the explicit instruction of a Sun Engineer.

To Repair the Database:

(NOTE: For OS versions prior to 4.21, it will be necessary to enter "admin" at the [menu] prompt before the second step)

  • Open a telnet or ssh connection to the NAS
  • Type the administrator password
  • At the CLI, enter load dbck
  • Enter dbck /<volumename>/.shares.
    The following is displayed:
    *** Checking /vol1/.shares
    Should repairs be needed, do you want them made?
  • Select option N, for No. This allows the database to be checked read-only.
  • If errors are reported, run dbck again as above, this time selecting option Y to perform the repairs.


Product
Sun StorageTek 5320 NAS Gateway/Cluster System
Sun StorageTek 5320 NAS Appliance
Sun StorageTek 5320
Sun StorageTek 5310 NAS Gateway/Cluster System
Sun StorageTek 5310 NAS Gateway System
Sun StorageTek 5310 NAS Appliance
Sun StorageTek 5220 NAS Appliance
Sun StorageTek 5220
Sun StorageTek 5210 NAS Appliance

Internal Comments
This document contains normalized content and is managed by the the Domain Lead(s) of the respective domains. To notify content owners of a knowledge gap contained in this document, and/or prior to updating this document, please contact the domain engineers that are managing this document via the “Document Feedback” alias(es) listed below:

storage-nas-domain@sun.com


The Knowledge Work Queue for this article is KNO-STO-NAS
NAS, CIFS, shares, access denied, audited
Previously Published As
90735

Change History
Date: 2007-12-11
User Name: 7058
Action: Approved
Comment: Fixed asset key type for 89144 from 9 (infodoc) to 37 (troubleshooting doc).
Version: 4
Date: 2007-12-11
User Name: 7058
Action: Update Started
Comment: Fix link to 89144
Version: 0
Date: 2007-10-03
User Name: 31620
Action: Approved
Comment: Verified Metadata - ok
Verified Keywords - ok (normalized)
Checked status of dependent articles:
89214 - published
89144 - published
Verified still correct for audience - currently set to contract
Audience left at contract as per FvF at
http://kmo.central/howto/content/voyager-contributor-standards.html
Checked review date - currently set to 2008-09-22
Checked for TM - added appropriate for STK product
Publishing under the current publication rules of 18 Apr 2005:
Version: 3




Attachments
This solution has no attachment
  Copyright © 2011 Sun Microsystems, Inc.  All rights reserved.
 Feedback