The easy way to verify if this is simply a duplicate of the similar sounding already fixed problem - see if relaxing the permissions on the share and directory (to wide open - full control or equivalent) fixes it.   The procedure varies a bit depending on server type.    Alternatively enabling debugging will get me 90% sure if the log shows that it fails on SMB NTCreateX

1) echo 1 > /proc/fs/cifs/cifsFYI
     echo 1 > /proc/fs/cifs/traceSMB
2) try to open a file (touch /mnt/dir_name/file_name or "echo 1 > /mnt/dir_name/file_name")
3) send me the excerpt from the dmesg output (kernel message log info)

In any case I expect the merge of a more current version of cifs vfs which includes this fix along with about a dozen key bug fixes to happen before 2.6.5

Steve French
Senior Software Engineer
Linux Technology Center - IBM Austin
phone: 512-838-2294
email: sfrench at-sign us dot ibm dot com

_______________________________________________
linux-cifs-client mailing list
linux-cifs-client <at> lists.samba.org
http://lists.samba.org/mailman/listinfo/linux-cifs-client