umask 0 (in linux) will only set the execute bit on directories. I imagine it works the same with NetApp CIFS. If you really need the file execute bits set, you'll need to do it manually.
Is the volume unix, ntfs, or mixed security?
You say you created the share with umask 000, and it didn't work - what happened instead? If it turned up -rw-rw-rw, then see my first note. Otherwise, if you change the cifs options you'll sometimes need to unmap/map the drive again - I've even seen the windows box need a reboot (windows!).
You say setting the linux umask to 0 didn't work either - again, was the result -rw-rw-rw?
You're saying that I cannot create a file with an administrator user via CIFS in a volume with UNIX or MIXED security, and that this file have rwxrwxrwx permissions when I do a ls -l in a linux host on the same volume?
Like you're saying, with every configuration (cifs shares -change umask, umask at linux level, ....), I only can get rwxr-x-r-x
I cannot get write permissions to the group and to others
My customer has an old Vseries controller, and he have to launch this process manually (chmod 777), and I only want to confirm this problem, because I've been trying for days, and It isn't works