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
 

Token Caching

The access token is stored on the NAS for up to thirty seconds after the user logs out. In most cases, it is sufficient for the user to disconnect from the NAS, wait thirty seconds, then reconnect. However, there are some situations where this does not work. For example, if the user connects from multiple systems, multiple connections from the same system or does not correctly perform the disconnection properly it sometimes becomes necessary to examine the tokens on the NAS for troubleshooting purposes.

The following steps can be taken as an alternative to looking at the tokens themselves, though some of them may be undesirable to the customer:

• Disconnect the share and wait 30-60 seconds before reconnecting. (net use X: /DELETE)
• Log out of the workstation.
• Reboot the workstation
• Reboot the NAS. This is generally not done except during scheduled maintenance, after many user accounts have been changed and some may still be connected.

Viewing User Access Tokens

This step must be performed from the NAS CLI. To access the token information, follow these steps:

(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 ls /proc/cifs

This will provide a listing of all tokens for connected users. This is sample output:

NAS1 > ls /proc/cifs

BIGDOMAIN.nobody.00000000.083D5001
BIGDOMAIN.nobody.00000000.083D51F2
BIGDOMAIN.nobody.00000000.083A53E1
BIGDOMAIN.nobody.00000000.083D55D1
BIGDOMAIN.nobody.00000000.083D53C3
BIGDOMAIN.nobody.00000000.063D59B0
BIGDOMAIN.joem.00000000.063D5BA0
BIGDOMAIN.janez.00000000.C0A85B4A
BIGDOMAIN.bobr.00000000.0F0B5000
BIGDOMAIN.samf.00000000.0F0B53E0        autohome        files
groups          ntdomain        pdc             services        sessions
shares          workers

Disregard the files containing nobody and the entries with no dots. The remaining files are user tokens. The filenames begin with the domain name, then the user name, then some hexadecimal digits. The hexadecimal digits are a representation of the IP address, which can be converted to decimal and used to discern between multiple logins for a user or detect unauthorized logins. The token is stored in plain text and contains useful.information about currently connected users. Here is an example:

User Sid:   S-1-5-21-1329958366-319369312-1704127429-241
Account:    janez
Domain:     BIGDOMAIN
Client:     192.168.91.74
Logon Time: Thu Sep 20 06:52:57 2007
Groups: 1
S-1-5-21-1329958366-319369312-1704127429-513
S-1-5-21-1329958366-319369312-1704127429-1999
S-1-5-21-1329958366-319369312-1704127429-2114
Privileges: 0
Default Owner:    S-1-5-21-1329958366-319369312-1704127429-241
FullName:   janez
PrimaryGrp Sid:   S-1-5-21-1329958366-319369312-1704127429-513
PrimaryGrp Name:  Domain Users
Unix credentials
Effective: 222 100
Real: 222 100
User RID: 241 (BIGDOMAIN)
LocalIP=0.0.0.0
TTL=0
References=1
Flag=0x2

The most useful fields are Account, Client, Groups, PrimaryGrp Name, and Unix credentials. These can be used to determine group membership, primary group and effective UNIX user and group information. This information should be helpful in troubleshooting security and credential mapping issues.

NOTE: Some of the information above is displayed as SIDs. To translate these to names, determine whether it is a group or user object, and check either /dvol/etc/group.map or /dvol/etc/users.map, which will have this number (the RID) in the fifth column.

This solution has no attachment