1- The vfiler name
2- CIFS shares and path affected
*commands to be run to collect the outputs*
vfiler run vfiler_name cifs shares
vfiler run vfiler_name options cifs
vfiler run vfiler_name qtree status
vfiler run vfiler_name fsecurity show /vol/vol5/doc (/vol/vol5/doc is the share location and/or folder being accessed)
vfiler run * vscan
vfiler run * vscan options
vfiler run * fpolicy
vfiler run vfiler_name sectrace add -ip client_IP_address
Note: The next two options, when changed to “on” generate a lot of console output related to the number of CIFS users currently logged in. If a large number of users are active consider turning these on during off hours.
vfiler run vfiler_name options cifs.trace_dc_connection on
vfiler run vfiler_name options cifs.trace_login on
reproduce the problem from the client side, console messages will be generated from the sectrace filter
vfiler run vfiler_name cifs sessions -p smb
vfiler run vfiler_name cifs sessions -p smb2
vfiler run vfiler_name sectrace delete all
vfiler run vfiler_name options cifs.trace_dc_connection off
vfiler run vfiler_name options cifs.trace_login off
options autosupport.doit cifs_permissions
capture a screenshot of the error received on the Windows client.