Managing mapping inconsistencies
Problems found in mapping inconsistencies
If a user cannot access a file that should be accessible, the problem can be one of the following:
- You granted access recently and the WAFL credential cache does not have the new mapping entry.
You can determine mapping inconsistencies between recently granted rights and the WAFL credential cache by comparing CIFS credential mappings. You can display mapping results for either the user's UNIX name or Windows NT account name.
- The NFS client could not obtain CIFS credentials.
You can determine whether an NFS client can perform a CIFS login to the filer by tracing CIFS logins.
- Depending on the NFS client, it may be necessary to wait for the NFS attribute cache to time out before changes to the CIFS credential take effect.
Determining mapping inconsistencies with a UNIX name
To determine mapping inconsistencies with a UNIX name, complete the following steps.
Step
|
Action
|
|
1 |
Display the current CIFS credential mapping of a UNIX name by entering the following command:
wcc -u uname
uname is the UNIX name of a user.
- You can further narrow the specification of the user by adding
-i, followed by the IP address of the host that the user is on.
- You can get more detailed information by appending -v to the command line. You can have up to three instances of the -v option (-vvv) per command.
|
|
2 |
Note the CIFS credential information.
|
|
3 |
Display the CIFS credential mappings in the WAFL credential cache by entering the following command:
wcc -d
You can get more detailed information by appending -v to the command line. You can have up to three instances of the -v option (-vvv) per command.
|
|
4 |
Compare the two CIFS credential mappings.
|
|
5 |
If entries in the WAFL credential cache are incorrect, delete them by entering the following command:
wcc -x name
See Deleting mapping entries from the WAFL credential cache for details about deleting entries.
|
Determining mapping inconsistencies with a Windows NT account name
To determine mapping inconsistencies with a Windows NT account name, complete the following steps.
Step
|
Action
|
|
1 |
Display the current CIFS credential mapping of a Windows NT account name by entering the following command:
wcc -s uname
uname is the Windows NT account name:
- You can further narrow the specification of the user by adding
-i, followed by the IP address of the host that the user is on.
- You can get more detailed information by appending -v to the command line. You can have up to three instances of the -v option (-vvv) per command.
|
|
2 |
Note the CIFS credential information.
|
|
3 |
To display information about all connected users, enter the following command:
cifs sessions -s
Locate the user's information in the output.
|
|
4 |
Compare the two CIFS credential mappings.
|
|
5 |
If the CIFS credential mappings are different, disconnect the client by entering the following command:
cifs terminate workstation
When the client reconnects, the CIFS credential mappings will be correct.
|
Tracing CIFS logins
To monitor an attempt by an NFS client to obtain a CIFS credential, complete the following step.
Caution
Use CIFS login tracing carefully because every CIFS login is traced and constant use can result in multiple console and log messages.
Step
|
Action
|
|
1 |
Enter the following command:
options cifs.trace_login on | off
Use on to enable or off to disable CIFS login tracing.
|
Copyright © 1994-2003, Network Appliance, Inc. All rights
reserved.
Part No. 210-00323
File: multi19.htm
Last updated: 01/15/03 15:46:09