Bug 57076 - Windows login delay, apparently due to smb issue in Samba 4.18.3
Windows login delay, apparently due to smb issue in Samba 4.18.3
Status: NEW
Product: UCS
Classification: Unclassified
Component: Samba
UCS 5.0
Other Linux
: P5 normal (vote)
: ---
Assigned To: Samba maintainers
Samba maintainers
https://bugzilla.samba.org/show_bug.c...
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2024-02-21 16:22 CET by Arvid Requate
Modified: 2024-03-04 12:21 CET (History)
2 users (show)

See Also:
What kind of report is it?: Bug Report
What type of bug is this?: 5: Major Usability: Impairs usability in key scenarios
Who will be affected by this bug?: 1: Will affect a very few installed domains
How will those affected feel about the bug?: 3: A User would likely not purchase the product
User Pain: 0.086
Enterprise Customer affected?: Yes
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number: 2023092621000086
Bug group (optional):
Max CVSS v3 score:
requate: Patch_Available+


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Arvid Requate univentionstaff 2024-02-21 16:22:05 CET
For Ticket# 2023092621000086 we analyzed a report of reproducably slow logins to a MS terminal server joined into UCS Samba/AD DCs. The customer reported that this effect started after updating from 5.0-0 to 5.0-4 (i.e. from Samba 4.18.0 to Samba 4.18.3).

The customer was so kind and able to generate wiresharks for A/B comparison of slow (> 1 Minute) vs fast (~ 4 sec) logins. After following some red herrings we found that in the slow case, an SMB2 read to some gpt.ini of some policy lacked a response packaged from the SMB server.

log.smbd around that time (08:14:39) shows error message of this kind:
===
[2024/02/20 08:14:17.720475,  0, pid=32501] ../../source3/smbd/smb2_server.c:685(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)
[2024/02/20 08:14:18.238613,  0, pid=32525] ../../source3/smbd/smb2_server.c:685(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)
[2024/02/20 08:14:39.749050,  0, pid=32554] ../../source3/smbd/smb2_server.c:685(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)
[2024/02/20 08:17:09.884848,  0, pid=937] ../../source3/smbd/smb2_server.c:685(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)
===
Comment 1 Arvid Requate univentionstaff 2024-02-21 16:22:17 CET
Looks like https://bugzilla.samba.org/show_bug.cgi?id=15346 , fixed in Samba 4.18.6
Comment 2 Arvid Requate univentionstaff 2024-02-21 17:39:16 CET
Workaround according to upstream Bug report:

echo -e "## Workaround for UCS Bug #57076\n[global]\n\tserver multi channel support = no\n" >> /etc/samba/local.conf
ucr commit /etc/samba/smb.conf
/etc/init.d/samba restart
Comment 3 Christina Scheinig univentionstaff 2024-03-04 11:51:01 CET
Workaround fixes the logon delay. So we should get the fix into the product
Comment 4 Mirac Erdemiroglu univentionstaff 2024-03-04 12:21:02 CET
Created an article for that:
https://help.univention.com/t/problem-windows-login-delay-2-3-minutes-smb-issue-in-samba-4-18-3/22719