We are having trouble accessing a cifs share (with ntfs security style) from a Sun box.
An F720, (6.0.1R3) exists in an NT "resource" domain that is trustING. The trustED master domain (with all user account information) is called "dwkcb". There is a One-way trust between domains ie. we don't trust the resource domain. (Don't ask why its a long story.)
A cifs share is called "test_ntfs" with ntfs security style. From a Sun box as walt a cd into it gets permission denied.
Here is an overview: nas01> qtree Volume Tree Style Oplocks -------- -------- ----- -------- sys unix enabled sys jobs unix enabled sys projects unix enabled sys scans ntfs enabled sys software unix enabled sys test_mixed mixed enabled sys test_ntfs ntfs enabled sys test_unix unix enabled
Account "walt" exists identically in both the NT domain "dwkcb" and a NIS domain. However here is the error we get (NetApp support has never seen this):
nas01> wcc -u walt Thu Nov 29 10:08:01 EST [rc:info]: Located account "DWKCB\walt" in domain "DWKCB". Thu Nov 29 10:08:01 EST [rc:error]: SamrConnect2: Exception rpc_s_call_id_not_found caught. Error 0xc002001b mapping UNIX name walt nas01> Thu Nov 29 10:08:01 EST [rc:info]: Error c002001b looking up domain groups
nas01> wcc -s walt Thu Nov 29 10:08:07 EST [rc:error]: SamrConnect2: Exception rpc_s_call_id_not_found caught. Error 0xc002001b mapping SID S-1-5-21-234058047-1151164854-1844936127-1008 nas01> Thu Nov 29 10:08:07 EST [rc:info]: Error c002001b looking up domain groups
Has anyone seen this or anything similar? We won't consider a two-way trust nor can we change the domain of the filer.
Any thoughts appreciated.
Anyone have any words of wizdom for implemeting VSCAN?
How about thoughts on Carrier Scan vs. Trend Server Protect vs. McAfee?
Larry