Description of problem: Hi. We have server (oceanic) with samba samba-4.5.3 as domain controller and two servers (mask and beabourg) with shared resources (wins server set to oceanic, authentication via ldap). On beabourg we have samba-4.2.7-0.fc23.x86_64 (fc23) - all login do domain and access to resources works fine. We have just done upgrade server mask from fc23 to fc25 (samba was upgraded from samba-4.2.7-0.fc23.x86_64 to samba-4.5.3-0.fc25.x86_64). After upgrade users can login to domain but they don't have access to mask resources. Version-Release number of selected component (if applicable): How reproducible: Upgrade samba from samba-4.2.7-0.fc23.x86_64 to samba-4.5.3-0.fc25.x86_64 Steps to Reproduce: 1. 2. 3. Actual results: [root@mask samba]# smbclient -d 3t \\\\mask\\public -U lukasz lp_load_ex: refreshing parameters Initialising global parameters rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384) Processing section "[global]" added interface enp1s0f0 ip=2001:1a68:a::35 bcast= netmask=ffff:ffff:ffff:ffff:: added interface enp1s0f0 ip=213.135.44.35 bcast=213.135.44.63 netmask=255.255.255.224 Client started (version 4.5.3). Enter lukasz's password: Connecting to 213.135.44.35 at port 445 Doing spnego session setup (blob length=74) got OID=1.3.6.1.4.1.311.2.2.10 got principal=not_defined_in_RFC4178@please_ignore GENSEC backend 'gssapi_spnego' registered GENSEC backend 'gssapi_krb5' registered GENSEC backend 'gssapi_krb5_sasl' registered GENSEC backend 'spnego' registered GENSEC backend 'schannel' registered GENSEC backend 'naclrpc_as_system' registered GENSEC backend 'sasl-EXTERNAL' registered GENSEC backend 'ntlmssp' registered GENSEC backend 'ntlmssp_resume_ccache' registered GENSEC backend 'http_basic' registered GENSEC backend 'http_ntlm' registered Got challenge flags: Got NTLMSSP neg_flags=0x62898215 NTLMSSP: Set final flags: Got NTLMSSP neg_flags=0x62088215 NTLMSSP Sign/Seal - Initialising with flags: Got NTLMSSP neg_flags=0x62088215 SPNEGO login failed: No logon servers session setup failed: NT_STATUS_NO_LOGON_SERVERS Expected results: [root@beabourg ~]# smbclient -d 3t \\\\beabourg\\private -U lukasz lp_load_ex: refreshing parameters Initialising global parameters rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384) Processing section "[global]" added interface eth0 ip=2001:1a68:a::55 bcast= netmask=ffff:ffff:ffff:ffff:: added interface eth0 ip=213.135.44.55 bcast=213.135.44.63 netmask=255.255.255.224 Client started (version 4.2.7). Enter lukasz's password: resolve_lmhosts: Attempting lmhosts lookup for name beabourg<0x20> resolve_lmhosts: Attempting lmhosts lookup for name beabourg<0x20> resolve_wins: using WINS server 213.135.44.33 and tag '*' Got a positive name query response from 213.135.44.33 ( 213.135.44.55 213.135.45.251 ) Connecting to 213.135.44.55 at port 445 Doing spnego session setup (blob length=74) got OID=1.3.6.1.4.1.311.2.2.10 got principal=not_defined_in_RFC4178@please_ignore Got challenge flags: Got NTLMSSP neg_flags=0x60898215 NTLMSSP: Set final flags: Got NTLMSSP neg_flags=0x60088215 NTLMSSP Sign/Seal - Initialising with flags: Got NTLMSSP neg_flags=0x60088215 Domain=[WSISIZ.EDU.PL] OS=[Windows 6.1] Server=[Samba 4.2.7] Additional info: I have found similar problems: https://bugzilla.samba.org/show_bug.cgi?id=12200 https://bugzilla.redhat.com/show_bug.cgi?id=1359398 https://bugzilla.samba.org/show_bug.cgi?id=11841 but I don't have any solution for this problem.
This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '25'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 25 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.