If CIFS clients get access, but it's read-only, try checking your cifs share permissions. filer> cifs shares <share_name> and if you don't know sharename just do filer> cifs shares

That will show you the permissions. Check to see what you have.

You can also trace who's (userID) coming in. do filer> options cifs.trace_login on Do this when you have no known open connections to the filer. Connect to storage with this option on, then turn it OFF when you're done. Capture the userID that is seen connecting.

If all shows up as you're expecting (even the cifs shares output) and you're still denied, check for NTFS permissions (but unless you have specified anything, it will be default everyone=full control).

NB: every file on the filer is case sensitive - it depends on who's doing the translating. ie: everything Ontap is case sensitive, but in your case of usermap.cfg, ABC\Administrator will be eventually passed to the CIFS protocol for resolution, and CIFS will treat it as case-INsensitive.

If you're getting those syntax error's in usermap.cfg, then check your syntax with a sample from NOW site. Or I'd suggest opening a case as multiprotocol access is typically easily setup, but you can end up running down fox-hole's if you're not sure what you're looking for. Good luck!

Best regards, ~~~~~~~~~~~~~~~~ Kevin Parker http://theparkerz.com ~~~~~~~~~~~~~~~~

_____

From: owner-toasters@mathworks.com [mailto:owner-toasters@mathworks.com] On Behalf Of Xishan Sent: Sunday, June 01, 2008 3:18 AM To: Toasters List Subject: Multiprotocol - file handles problem

Hello all... I am using my filer in a multiprotocol environment, where the same qtree is being accessed through CIFS as well as NFS. Recently i ran into this problem that whenever the file in the qtree was accessed by an application, it was opened as READ-ONLY. The CIFS user were unable to change/re-write the file. I changed the security style from UNIX to NTFS but the issue was not resolved. I re-verified the entries in /etc/usermap.cfg and added few entries in the usermap.cfg like

abc*==* abc.def \ Administrator == root

But the problem remains unresolved. when CIFS is terminated and re-started, the filer gives the following messages: =========================================================== Sat May 31 15:43:44 PKT [befas21: cifs.umap.cfgFile.badEntry:error]: CIFS: Invalid entry in /etc/usermap.cfg, line 29: Invalid syntax. Sat May 31 15:44:05 PKT [befas21: nbt.nbns.registrationComplete:info]: NBT: All CIFS name registrations have completed for the local server. =========================================================== So is there any issue with the /etc/usermap.cfg ??? Earlier the same file access worked fine with this entry in usermap.cfg

ABC*==*

Any ideas/solutions are welcome...is usermap.cfg case sensitive???

The output of CIFS domaininfo and CIFS prefdc print is =========================================================== befas21> cifs domaininfo NetBios Domain: ABC Windows 2000 Domain Name: abc.def Type: Windows 2000 Filer AD Site: none

Current Connected DCs: \DC01AD Total DC addresses found: 2 Preferred Addresses: 10.90.11.12 DC01AD PDC Favored Addresses: None Other Addresses: 10.9.11.12 PDC

Connected AD LDAP Server: \dc01ad.abc.def Preferred Addresses: 10.90.11.12 dc01ad.abc.def Favored Addresses: None Other Addresses: 10.9.11.12 dc01ad.abc.def =========================================================== befas21> cifs prefdc print Preferred DC ordering per domain:

ABC: 1. 10.90.11.12 ===========================================================