[Samba] smb2_validate_sequence_number: bad message_id 2

Niumar André Klein niumar at solis.com.br
Fri Jul 14 12:13:44 UTC 2023


Hi, 
I would like to share a situation we are facing when managing users over RSAT tools or when acessing the sysvol share over explorer. 
First, we have a samba4 domain with two DCs and about 9K objects in the database. Recently we updated these DCs from version 4.16.0 to 4.18.2. 
Before upgrading to 4.18.2 everything worked fine! After, also, however we started to frequently experience a delay of around 30 seconds on managing users properties or accessing \\dc01 or \\dc02 from the windows RSAT station. 
After the delay, it works fine again, but some time later, it happens again, and so on. No error screens are presented during or after this delay. 

We found this log messages on both DCs watching the RSAT station specific file log. 
This specific messages appears only when the delay happens. 

[2023/07/13 09:01:10.307842, 0] ../../source3/smbd/smb2_server.c:677(smb2_validate_sequence_number) 
smb2_validate_sequence_number: smb2_validate_sequence_number: bad message_id 2 (sequence id 2) (granted = 1, low = 1, range = 1) 
[2023/07/13 09:14:03.951134, 0] ../../source3/smbd/smb2_server.c:677(smb2_validate_sequence_number) 
smb2_validate_sequence_number: smb2_validate_sequence_number: bad message_id 2 (sequence id 2) (granted = 1, low = 1, range = 1) 
[2023/07/13 09:14:04.365207, 0] ../../source3/smbd/smb2_server.c:677(smb2_validate_sequence_number) 
smb2_validate_sequence_number: smb2_validate_sequence_number: bad message_id 2 (sequence id 2) (granted = 1, low = 1, range = 1) 
[2023/07/13 09:16:50.551731, 0] ../../source3/smbd/smb2_server.c:677(smb2_validate_sequence_number) 
smb2_validate_sequence_number: smb2_validate_sequence_number: bad message_id 2 (sequence id 2) (granted = 1, low = 1, range = 1) 
[2023/07/13 10:01:59.368604, 0] ../../source3/smbd/smb2_server.c:677(smb2_validate_sequence_number) 
smb2_validate_sequence_number: smb2_validate_sequence_number: bad message_id 2 (sequence id 2) (granted = 1, low = 1, range = 1) 
[2023/07/13 10:22:03.537948, 0] ../../source3/smbd/smb2_server.c:677(smb2_validate_sequence_number) 
smb2_validate_sequence_number: smb2_validate_sequence_number: bad message_id 2 (sequence id 2) (granted = 1, low = 1, range = 1) 
[2023/07/13 10:22:20.868229, 0] ../../source3/smbd/smb2_server.c:677(smb2_validate_sequence_number) 
smb2_validate_sequence_number: smb2_validate_sequence_number: bad message_id 2 (sequence id 2) (granted = 1, low = 1, range = 1) 
[2023/07/13 10:27:15.948022, 0] ../../source3/smbd/smb2_server.c:677(smb2_validate_sequence_number) 
smb2_validate_sequence_number: smb2_validate_sequence_number: bad message_id 2 (sequence id 2) (granted = 1, low = 1, range = 1) 
[2023/07/13 10:29:30.958987, 0] ../../source3/smbd/smb2_server.c:677(smb2_validate_sequence_number) 
smb2_validate_sequence_number: smb2_validate_sequence_number: bad message_id 2 (sequence id 2) (granted = 1, low = 1, range = 1) 
[2023/07/13 10:30:40.073762, 0] ../../source3/smbd/smb2_server.c:677(smb2_validate_sequence_number) 
smb2_validate_sequence_number: smb2_validate_sequence_number: bad message_id 2 (sequence id 2) (granted = 1, low = 1, range = 1) 
[2023/07/13 10:32:22.408909, 0] ../../source3/smbd/smb2_server.c:677(smb2_validate_sequence_number) 
smb2_validate_sequence_number: smb2_validate_sequence_number: bad message_id 2 (sequence id 2) (granted = 1, low = 1, range = 1) 
[2023/07/13 10:35:27.458666, 0] ../../source3/smbd/smb2_server.c:677(smb2_validate_sequence_number) 
smb2_validate_sequence_number: smb2_validate_sequence_number: bad message_id 2 (sequence id 2) (granted = 1, low = 1, range = 1) 
[2023/07/13 10:36:11.183172, 0] ../../source3/smbd/smb2_server.c:677(smb2_validate_sequence_number) 
smb2_validate_sequence_number: smb2_validate_sequence_number: bad message_id 2 (sequence id 2) (granted = 1, low = 1, range = 1) 
[2023/07/13 10:39:48.355103, 0] ../../source3/smbd/smb2_server.c:677(smb2_validate_sequence_number) 
smb2_validate_sequence_number: smb2_validate_sequence_number: bad message_id 2 (sequence id 2) (granted = 1, low = 1, range = 1) 
[2023/07/13 11:30:59.167177, 0] ../../source3/smbd/smb2_server.c:677(smb2_validate_sequence_number) 
smb2_validate_sequence_number: smb2_validate_sequence_number: bad message_id 2 (sequence id 2) (granted = 1, low = 1, range = 1) 
[2023/07/13 12:20:50.282234, 0] ../../source3/smbd/smb2_server.c:677(smb2_validate_sequence_number) 

There is also a similar post on [ https://lists.samba.org/archive/samba/2023-January/243564.html | https://lists.samba.org/archive/samba/2023-January/243564.html ] , but i don't know if is the same case. 

Below our smb.conf file: 

# Global parameters 
[global] 
bind interfaces only = Yes 
interfaces = lo ens160 
log file = /var/log/samba/log.%m 
log level = 3 auth_audit:3@/var/log/samba/log.auth_audit 
max log size = 5000 
netbios name = DC01 
realm = XXX.AAA.BB 
server role = active directory domain controller 
server services = s3fs, rpc, nbt, wrepl, ldap, cldap, kdc, drepl, winbindd, ntp_signd, kcc, dnsupdate 
workgroup = XXX 
idmap_ldb:use rfc2307 = yes 
dns update command = /usr/sbin/samba_dnsupdate --use-samba-tool 

[sysvol] 
path = /var/lib/samba/sysvol 
read only = No 

[netlogon] 
path = /var/lib/samba/sysvol/pml.lajeado.rs.gov.br/scripts 
read only = No 


So I hope someone can contribute. 

Thanks, 
Niumar Klein 

	
Niumar Andre Klein 
Infraestrutura 
[ http://www.solis.com.br/ | www.solis.com.br ] 
	@solissolucoes 

	( 51) 3748-6565 
[ https://www.solis.com.br/#solucoes | Conheça nossas soluções: ] 
- Gestão Educacional 
- Diploma Digital 
- Central de Serviços Digitais 
	
- Gestão de Bibliotecas 
- Infraestrutura de TI 
- Gestão Eletrônica de Documentos 



More information about the samba mailing list