Hello all...<br>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.<br>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<br><br>abc\*==*<br>abc.def \ Administrator == root<br> <br>But the problem remains unresolved. when CIFS is terminated and re-started, the filer gives the following messages:<br>===========================================================<br>Sat May 31 15:43:44 PKT [befas21: cifs.umap.cfgFile.badEntry:error]: CIFS: Invalid entry in /etc/usermap.cfg, line 29: Invalid syntax.<br>Sat May 31 15:44:05 PKT [befas21: nbt.nbns.registrationComplete:info]: NBT: All CIFS name registrations have
 completed for the local server.<br>===========================================================<br>So is there any issue with the /etc/usermap.cfg ??? Earlier the same file access worked fine with this entry in usermap.cfg<br><br>ABC\*==*<br><br><span style="font-weight: bold;">Any ideas/solutions are welcome...is usermap.cfg case sensitive???</span><br><br>The output of CIFS domaininfo&nbsp; and CIFS prefdc print is<br>===========================================================<br>befas21&gt; cifs domaininfo<br>NetBios Domain:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ABC<br>Windows 2000 Domain Name: abc.def<br>Type:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Windows 2000<br>Filer AD Site:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; none<br><br>Current Connected DCs:&nbsp;&nbsp;&nbsp; \\DC01AD<br>Total DC addresses found: 2<br>Preferred
 Addresses:<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 10.90.11.12&nbsp;&nbsp;&nbsp;&nbsp; DC01AD&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; PDC<br>Favored Addresses:<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; None<br>Other Addresses:<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 10.9.11.12&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; PDC<br><br>Connected AD LDAP Server: \\dc01ad.abc.def<br>Preferred Addresses:<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
 10.90.11.12&nbsp;&nbsp;&nbsp;&nbsp; <br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; dc01ad.abc.def<br>Favored Addresses:<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; None<br>Other Addresses:<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 10.9.11.12&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; dc01ad.abc.def<br>===========================================================<br>befas21&gt; cifs prefdc print<br>Preferred DC ordering per domain:<br><br>ABC:<br>&nbsp;&nbsp;&nbsp; 1.
 10.90.11.12<br>===========================================================<br><p>&#32;