Hi, I cannot get Windows 10 to connect to my Samba server without SMB1. I get the following error when I try to join Windows 10 client to Samba 4.11.13 AD. I get the following error on the client: "The following error occurred attempting to join the domain 'local.richardshapiro.com': You can't connect to the file share because it's not secure. This share requires the obsolete SMB1 protocol, which is unsafe and could expose your system to attack. Your system requires SMB2 or higher. For more info on resolving this issue, see https://go.microsoft.com/fwlink/?linkid=852747" I get? the following on the server: "Feb 27 20:43:06 ss-prod smbd[7323]: [2021/02/27 20:43:06.043958,? 0, pid=7323, effective(0, 0), real(0, 0)] ../../source3/smbd/negprot.c:593(reply_negprot) Feb 27 20:43:06 ss-prod smbd[7323]:? negprot got no protocols" If I enable SMB1 on the Windows? 10 client it can join the domain just fine. Without SMB1, it fails every time. I have tried numerous Samba configuration options on the Samba server, but none work. Server info: CentOS Linux release 7.9.2009 [root at ss-prod packages]# uname -a Linux ss-prod.rsa.richardshapiro.com 3.10.0-1160.15.2.el7.x86_64 #1 SMP Wed Feb 3 15:06:38 UTC 2021 x86_64 x86_64 x86_64 GNU/Linu Samba 4.11.13 built from source I have tried numerous options on the server: ??????? server max protocol = SMB2 ??????? #min protocol = SMB2 #?????? min protocol = SMB2 #?????? server min protocol = NT1 ??????? #server min protocol = SMB2_10 ??????? #server max protocol = SMB3 ??????? #protocol = SMB Shouldn't 4.11.13 support SMB2 or higher? -- Regards, K. R. Foley
Sebastian Lisic
2021-Feb-28 10:21 UTC
[Samba] Time outs and high cpu usage after upgrading to 4.12.11
Hi, I recently upgraded two Centos 8 domain controllers from 4.11.15 to 4.12.11 and am now getting periodic issues with high cpu usage and io time outs every other day. Restarting Samba temporarily fixes the problem for another day or so. Replication works fine before the problem manifests and after I restart Samba. I am seeing the following errors in log.samba on DC1: [2021/02/27 13:20:44.283975, 0] ../../source4/rpc_server/common/forward.c:51(dcesrv_irpc_forward_callback) IRPC callback failed for DsReplicaSync - NT_STATUS_IO_TIMEOUT [2021/02/27 16:52:08.011225, 0] ../../source4/dsdb/dns/dns_update.c:86(dnsupdate_nameupdate_done) dnsupdate_nameupdate_done: Failed DNS update with exit code 110 [2021/02/27 19:57:52.397404, 0] ../../source4/dsdb/kcc/kcc_periodic.c:768(samba_kcc_done) ../../source4/dsdb/kcc/kcc_periodic.c:768: Failed samba_kcc - NT_STATUS_IO_TIMEOUT [2021/02/27 20:02:52.551916, 0] ../../source4/dsdb/kcc/kcc_periodic.c:768(samba_kcc_done) ../../source4/dsdb/kcc/kcc_periodic.c:768: Failed samba_kcc - NT_STATUS_IO_TIMEOUT During the same day I am seeing the following errors in log.samba on DC2: [2021/02/26 17:58:42.117403, 0] ../../source4/dsdb/repl/drepl_out_helpers.c:1301(dreplsrv_update_refs_done) UpdateRefs failed with NT_STATUS_IO_TIMEOUT [2021/02/26 18:08:53.563593, 0] ../../source4/dsdb/repl/drepl_out_helpers.c:1301(dreplsrv_update_refs_done) UpdateRefs failed with NT_STATUS_IO_TIMEOUT [2021/02/27 22:58:39.993614, 0] ../../source4/dsdb/repl/drepl_out_helpers.c:1301(dreplsrv_update_refs_done) UpdateRefs failed with NT_STATUS_IO_TIMEOUT [2021/02/27 23:08:47.766855, 0] ../../source4/dsdb/repl/drepl_out_helpers.c:1301(dreplsrv_update_refs_done) UpdateRefs failed with NT_STATUS_IO_TIMEOUT [2021/02/27 23:29:17.597409, 0] ../../source4/dsdb/repl/drepl_out_helpers.c:1301(dreplsrv_update_refs_done) UpdateRefs failed with NT_STATUS_IO_TIMEOUT [2021/02/27 23:58:38.307600, 0] ../../source4/dsdb/repl/drepl_out_helpers.c:1301(dreplsrv_update_refs_done) UpdateRefs failed with NT_STATUS_IO_TIMEOUT
On 28/02/2021 03:47, K. R. Foley via samba wrote:> Hi, > > I cannot get Windows 10 to connect to my Samba server without SMB1. > > > I get the following error when I try to join Windows 10 client to > Samba 4.11.13 AD. I get the following error on the client: > > "The following error occurred attempting to join the domain > 'local.richardshapiro.com': > > You can't connect to the file share because it's not secure. This > share requires the obsolete SMB1 protocol, which is unsafe and could > expose your system to attack. Your system requires SMB2 or higher. For > more info on resolving this issue, see > https://go.microsoft.com/fwlink/?linkid=852747" > > > I get? the following on the server: > > "Feb 27 20:43:06 ss-prod smbd[7323]: [2021/02/27 20:43:06.043958, 0, > pid=7323, effective(0, 0), real(0, 0)] > ../../source3/smbd/negprot.c:593(reply_negprot) > Feb 27 20:43:06 ss-prod smbd[7323]:? negprot got no protocols" > > > If I enable SMB1 on the Windows? 10 client it can join the domain just > fine. Without SMB1, it fails every time. I have tried numerous Samba > configuration options on the Samba server, but none work. > > Server info: > > CentOS Linux release 7.9.2009 > > [root at ss-prod packages]# uname -a > Linux ss-prod.rsa.richardshapiro.com 3.10.0-1160.15.2.el7.x86_64 #1 > SMP Wed Feb 3 15:06:38 UTC 2021 x86_64 x86_64 x86_64 GNU/Linu > > Samba 4.11.13 built from source > > I have tried numerous options on the server: > > ??????? server max protocol = SMB2 > ??????? #min protocol = SMB2 > #?????? min protocol = SMB2 > #?????? server min protocol = NT1 > ??????? #server min protocol = SMB2_10 > ??????? #server max protocol = SMB3 > ??????? #protocol = SMB > > > Shouldn't 4.11.13 support SMB2 or higher? >It does, can you post your smb.conf Rowland