Comment 23 for bug 210741

tonyw,

I'm glad to hear that you were able to get your application working!

Based on your output, I'm not convinced that your problem is the same as <https://bugzilla.samba.org/show_bug.cgi?id=2512>. For one thing, you mention that you're able to access the files from a text editor, so there at least doesn't seem to be a lack of read permissions; and in my experience, when unix extensions are used, whatever file permissions are shown on the client side are the ones that are actually enforced - and in your case the client permissions look ok.

One way to test whether permissions are the source of the problem, or whether it's some other aspect of Unix extensions causing the problem, would be to re-enable the Unix extensions on the server side and then use the 'noperm' option when mounting. If TAS Books works, then it's a permissions problem; if it doesn't work, then the problem lies with Unix extensions but not with the Unix permissions handling.

Finally, since this problem only occurs with a closed source application, it would be helpful to have some sort of client trace here: either a kernel client trace like the one Jan generated using the /proc/fs/cifs/traceSMB and /proc/fs/cifs/cifsFYI variables, or the output of 'strace -efile' showing what sort of file access the application is doing.