thr3ads.net - samba - [Samba] smb_set_file_dosmode error: BUG after update to samba4-4.4.2 [May 2016]

If this information is useful, please help other people find it:
Share via:

Robert K. Nelson

2016-May-18 13:39 UTC

[Samba] smb_set_file_dosmode error: BUG after update to samba4-4.4.2

We are using samba4 as an AD controller under OpenSuSE 13.2 using the 
repository at:

http://download.opensuse.org/repositories/network:/samba:/TESTING/openSUSE_13.2 


After an update to Version 4.4.2, we began getting error from our CAD 
program (SolidWorks). This happens under both Windows 7 and Windows 10.

The messages in the Samba log file are:

[2016/05/17 10:49:02.822522,  2] ../source3/smbd/open.c:1006(open_file)
   ASC\jnitz opened file 
Projects/ALI/CAD/~$ALI_Pit-8-Concept_Assy-0_MAIN_00.SLDASM read=No 
write=No (numopen=2)
[2016/05/17 10:49:02.823553,  2] 
../source3/smbd/trans2.c:6144(smb_set_file_dosmode)
   smb_set_file_dosmode: file_set_dosmode of 
Projects/ALI/CAD/~$ALI_Pit-8-Concept_Assy-0_MAIN_00.SLDASM failed 
(Operation not supported)

This file is both readable and writable using the Windows NotePad 
accessory.

There were no configuration file changes made before or after the update 
to samba4-4.4.2, and there were no changes to the CAD program, so the 
problem would seem to be associated with the update. I notice in the 
Release Notes that there were several Samba patches associated with 
preventing MITM attacks. I wonder if the problem may come from one of 
those changes.

Has anyone else seen this issue? Is there a workaround? May I provide 
more information.

Here are the results of rpm -qa | grep samba
_____________________________________________
libsamba-passdb0-4.2.3-5.1.x86_64
libsamba-passdb0-32bit-4.2.4-34.1.x86_64
libsamba-util0-32bit-4.2.4-34.1.x86_64
samba4-4.4.2-1.1.x86_64
libsamba-hostconfig0-32bit-4.2.4-34.1.x86_64
libsamba-credentials0-32bit-4.2.4-34.1.x86_64
samba-libs-32bit-4.2.4-34.1.x86_64
samba-libs-4.2.3-5.1.x86_64
samba-winbind-32bit-4.2.4-34.1.x86_64
libsamba-util0-4.2.3-5.1.x86_64
yast2-samba-server-3.1.11-2.8.1.noarch
samba-client-32bit-4.2.4-34.1.x86_64
samba-winbind-4.2.3-5.1.x86_64

Here is the header part of our smb.conf file:
____________________________________________
# Global parameters
[global]
         workgroup = ASC
         netbios name = ASCPC21
         server role = active directory domain controller
         realm = ASC.AIRFLOWSCIENCES.COM
         #dns recursive queries = yes    # although documented in a few 
places, this stanza is apparently not parsed or implemented
         allow dns updates = nonsecure
         dns forwarder = 8.8.8.8
         log file = /var/log/samba/samba4.log
         log level = 2
         idmap gid = 10000-20000
         idmap uid = 10000-20000
         security = user
         usershare allow guests = No
         usershare max shares = 100
         add machine script = /usr/sbin/useradd  -c Machine -d 
/var/lib/nobody -s /bin/false %m$
         domain logons = Yes
         domain master = Yes
         ldap admin dn          ldap suffix          local master = Yes
         os level = 65
         passdb backend = smbpasswd
         preferred master = Yes
         wins server          wins support = No
         vfs objects = acl_xattr
         map acl inherit = Yes
         store dos attributes = Yes
         unix extensions = no
         wide links = yes
         time server = yes

-- 
Robert K. Nelson
Airflow Sciences Corporation
12190 Hubbard Street, Livonia, MI  48150-1737
(734) 525-0300   FAX (734) 525-0303 www.airflowsciences.com

Rowland penny

2016-May-18 14:27 UTC

head link

[Samba] smb_set_file_dosmode error: BUG after update to samba4-4.4.2

On 18/05/16 14:39, Robert K. Nelson wrote:> We are using samba4 as an AD controller under OpenSuSE 13.2 using the 
> repository at:
>
>
http://download.opensuse.org/repositories/network:/samba:/TESTING/openSUSE_13.2
>
>
> After an update to Version 4.4.2, we began getting error from our CAD 
> program (SolidWorks). This happens under both Windows 7 and Windows 10.
>
> The messages in the Samba log file are:
>
> [2016/05/17 10:49:02.822522,  2] ../source3/smbd/open.c:1006(open_file)
>   ASC\jnitz opened file 
> Projects/ALI/CAD/~$ALI_Pit-8-Concept_Assy-0_MAIN_00.SLDASM read=No 
> write=No (numopen=2)
> [2016/05/17 10:49:02.823553,  2] 
> ../source3/smbd/trans2.c:6144(smb_set_file_dosmode)
>   smb_set_file_dosmode: file_set_dosmode of 
> Projects/ALI/CAD/~$ALI_Pit-8-Concept_Assy-0_MAIN_00.SLDASM failed 
> (Operation not supported)
>
> This file is both readable and writable using the Windows NotePad 
> accessory.
>
> There were no configuration file changes made before or after the 
> update to samba4-4.4.2, and there were no changes to the CAD program, 
> so the problem would seem to be associated with the update. I notice 
> in the Release Notes that there were several Samba patches associated 
> with preventing MITM attacks. I wonder if the problem may come from 
> one of those changes.
>
> Has anyone else seen this issue? Is there a workaround? May I provide 
> more information.
>
> Here are the results of rpm -qa | grep samba
> _____________________________________________
> libsamba-passdb0-4.2.3-5.1.x86_64
> libsamba-passdb0-32bit-4.2.4-34.1.x86_64
> libsamba-util0-32bit-4.2.4-34.1.x86_64
> samba4-4.4.2-1.1.x86_64
> libsamba-hostconfig0-32bit-4.2.4-34.1.x86_64
> libsamba-credentials0-32bit-4.2.4-34.1.x86_64
> samba-libs-32bit-4.2.4-34.1.x86_64
> samba-libs-4.2.3-5.1.x86_64
> samba-winbind-32bit-4.2.4-34.1.x86_64
> libsamba-util0-4.2.3-5.1.x86_64
> yast2-samba-server-3.1.11-2.8.1.noarch
> samba-client-32bit-4.2.4-34.1.x86_64
> samba-winbind-4.2.3-5.1.x86_64
>
> Here is the header part of our smb.conf file:
> ____________________________________________
> # Global parameters
> [global]
>         workgroup = ASC
>         netbios name = ASCPC21
>         server role = active directory domain controller
>         realm = ASC.AIRFLOWSCIENCES.COM
>         #dns recursive queries = yes    # although documented in a few 
> places, this stanza is apparently not parsed or implemented
>         allow dns updates = nonsecure
>         dns forwarder = 8.8.8.8
>         log file = /var/log/samba/samba4.log
>         log level = 2
>         idmap gid = 10000-20000
>         idmap uid = 10000-20000
>         security = user
>         usershare allow guests = No
>         usershare max shares = 100
>         add machine script = /usr/sbin/useradd  -c Machine -d 
> /var/lib/nobody -s /bin/false %m$
>         domain logons = Yes
>         domain master = Yes
>         ldap admin dn >         ldap suffix >         local master =
Yes
>         os level = 65
>         passdb backend = smbpasswd
>         preferred master = Yes
>         wins server >         wins support = No
>         vfs objects = acl_xattr
>         map acl inherit = Yes
>         store dos attributes = Yes
>         unix extensions = no
>         wide links = yes
>         time server = yes
>
This is possibly caused by one of the regressions fixed in 4.4.3, see 
release notes here:

https://www.samba.org/samba/history/samba-4.4.3.html

Can I also suggest you remove everything in your smb.conf after the 'log 
level =2' line, they are either default lines, lines that shouldn't be 
in an AD DC smb.conf, lines that do nothing on an AD DC, or lines that 
over-ride required settings.

Rowland

Markus Dellermann

2016-May-18 15:16 UTC

head link

[Samba] smb_set_file_dosmode error: BUG after update to samba4-4.4.2

Hi,
Am 18.05.2016 um 15:39 schrieb Robert K. Nelson:> We are using samba4 as an AD controller under OpenSuSE 13.2 using the
> repository at:
>
>
http://download.opensuse.org/repositories/network:/samba:/TESTING/openSUSE_13.2
>
>Not related to your Problem, but are you sure, that this repo really
provide ad-dc - funktionality??
>From the spec-file:"%global with_mitkrb5 1"
"%global with_dc 0"

"%if ! %with_dc
    --without-ad-dc \"



Markus
> After an update to Version 4.4.2, we began getting error from our CAD
> program (SolidWorks). This happens under both Windows 7 and Windows 10.
>
> The messages in the Samba log file are:
>
> [2016/05/17 10:49:02.822522,  2] ../source3/smbd/open.c:1006(open_file)
>   ASC\jnitz opened file
> Projects/ALI/CAD/~$ALI_Pit-8-Concept_Assy-0_MAIN_00.SLDASM read=No
> write=No (numopen=2)
> [2016/05/17 10:49:02.823553,  2]
> ../source3/smbd/trans2.c:6144(smb_set_file_dosmode)
>   smb_set_file_dosmode: file_set_dosmode of
> Projects/ALI/CAD/~$ALI_Pit-8-Concept_Assy-0_MAIN_00.SLDASM failed
> (Operation not supported)
>
> This file is both readable and writable using the Windows NotePad
> accessory.
>
> There were no configuration file changes made before or after the
> update to samba4-4.4.2, and there were no changes to the CAD program,
> so the problem would seem to be associated with the update. I notice
> in the Release Notes that there were several Samba patches associated
> with preventing MITM attacks. I wonder if the problem may come from
> one of those changes.
>
> Has anyone else seen this issue? Is there a workaround? May I provide
> more information.
>
> Here are the results of rpm -qa | grep samba
> _____________________________________________
> libsamba-passdb0-4.2.3-5.1.x86_64
> libsamba-passdb0-32bit-4.2.4-34.1.x86_64
> libsamba-util0-32bit-4.2.4-34.1.x86_64
> samba4-4.4.2-1.1.x86_64
> libsamba-hostconfig0-32bit-4.2.4-34.1.x86_64
> libsamba-credentials0-32bit-4.2.4-34.1.x86_64
> samba-libs-32bit-4.2.4-34.1.x86_64
> samba-libs-4.2.3-5.1.x86_64
> samba-winbind-32bit-4.2.4-34.1.x86_64
> libsamba-util0-4.2.3-5.1.x86_64
> yast2-samba-server-3.1.11-2.8.1.noarch
> samba-client-32bit-4.2.4-34.1.x86_64
> samba-winbind-4.2.3-5.1.x86_64
>
> Here is the header part of our smb.conf file:
> ____________________________________________
> # Global parameters
> [global]
>         workgroup = ASC
>         netbios name = ASCPC21
>         server role = active directory domain controller
>         realm = ASC.AIRFLOWSCIENCES.COM
>         #dns recursive queries = yes    # although documented in a few
> places, this stanza is apparently not parsed or implemented
>         allow dns updates = nonsecure
>         dns forwarder = 8.8.8.8
>         log file = /var/log/samba/samba4.log
>         log level = 2
>         idmap gid = 10000-20000
>         idmap uid = 10000-20000
>         security = user
>         usershare allow guests = No
>         usershare max shares = 100
>         add machine script = /usr/sbin/useradd  -c Machine -d
> /var/lib/nobody -s /bin/false %m$
>         domain logons = Yes
>         domain master = Yes
>         ldap admin dn >         ldap suffix >         local master =
Yes
>         os level = 65
>         passdb backend = smbpasswd
>         preferred master = Yes
>         wins server >         wins support = No
>         vfs objects = acl_xattr
>         map acl inherit = Yes
>         store dos attributes = Yes
>         unix extensions = no
>         wide links = yes
>         time server = yes
>

Rowland penny

2016-May-18 16:10 UTC

head link

[Samba] smb_set_file_dosmode error: BUG after update to samba4-4.4.2

On 18/05/16 16:16, Markus Dellermann wrote:> Hi,
> Am 18.05.2016 um 15:39 schrieb Robert K. Nelson:
>> We are using samba4 as an AD controller under OpenSuSE 13.2 using the
>> repository at:
>>
>>
http://download.opensuse.org/repositories/network:/samba:/TESTING/openSUSE_13.2
>>
>>
> Not related to your Problem, but are you sure, that this repo really
> provide ad-dc - funktionality??
>
>  From the spec-file:
> "%global with_mitkrb5 1"
> "%global with_dc 0"
>
> "%if ! %with_dc
>      --without-ad-dc \"
>
>
>
> Markus
>
>
It looks like you are right, there is also these lines:

%exclude %{_mandir}/man8/samba-tool.8.*
%exclude %{_mandir}/man8/samba.8.*

It seems the manpages for samba-tool and the 'samba' binary aren't 
installed and the only reason for that would be if 'samba-tool' and the 
'samba' binary aren't installed.

I should have engaged brain before posting, Suse, just like RHEL uses 
MIT instead of Heimdal kerberos and therefore doesn't have the AD DC 
stuff in its Samba packages.

Rowland

Seemingly Similar Threads

Search for more seemingly similar threads

samba - May 2016 - smb_set_file_dosmode error: BUG after update to samba4-4.4.2

[Samba] smb_set_file_dosmode error: BUG after update to samba4-4.4.2

[Samba] smb_set_file_dosmode error: BUG after update to samba4-4.4.2

[Samba] smb_set_file_dosmode error: BUG after update to samba4-4.4.2

[Samba] smb_set_file_dosmode error: BUG after update to samba4-4.4.2

Seemingly Similar Threads