[Samba] Samba 4.1.12 NT_STATUS_ACCESS_DENIED messages

[Reindl Harald]

Am 24.03.2016 um 13:33 schrieb mathias dufresne:
> Lot of things can be the reason, or the reasons. More information are
> needed to start thinking about your issue. Giving us your configuration
> files, OS on client, logs (not the whole logs but neither just
> NT_STATUS_ACCESS_DENIED), and anything else which could help one of us to
> understand better your issue, for that person can try to help you.
>
> As a lazy poster I could suggest to get more recent version of Samba

i ask myself from where he got Samba 4.1.12 on CentOS7
a simple typo makes 4.2.1-3 not to 4.1.12

samba-4.2.3-12.el7_2.x86_64

> 2016-03-20 19:37 GMT+01:00 Михаил Прокопенко <ca6aka.bim at mail.ru>:
>>
>> We used successfully samba 3.5.15-74.fc15 in our production (animation
>> studio). It was installed on FC15 on ext4 volume.
>> Now, we got new hardware and tried fresh software installation:
>> it is CentOS7, with Samba 4.1.12 and XFS volumes.
>> So, now we got strange problem. Some production software (Autodesk
>> Maya2016) got errors trying to work with files. There is no such problem
>> with Samba3.
>> For instance, we want to get software render - i.e. generate some files on
>> samba share. But we got error message with “permission error” in Maya log.
>> The files appeared in appropriate folder, but all of them are truncated -
>> about 100 byte length instead of hundred of bytes. The very strange moment,
>> that this error depend on file type to generate. .iff files are ok, but
>> most all others (png, tiff, psd) - generates errors.
>> Samba log files contains some NT_STATUS_ACCESS_DENIED messages. But all
>> the files are available from clients and there is no problem to create
>> folder\files as the software requires.
>> What may be the reason? How can we solve that?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: OpenPGP digital signature
URL: <http://lists.samba.org/pipermail/samba/attachments/20160324/b04cb35d/signature.sig>