samba - Jan 2023 - Slow login after samba upgrade

Apologies if I annoyed you, in business it is common practice to reply to
everyone in the thread.
Here are the files.

https://drive.google.com/drive/folders/1GIE0npEovJhuMKGdRFY14u3nJ_TszFOO?usp=share_link


On Mon, Jan 2, 2023 at 11:48 AM Rowland Penny via samba <
samba at lists.samba.org> wrote:
>
>
> On 02/01/2023 10:26, Max Serafini wrote:
> > Got the message about the size.  Here they are again, split...
> >
>
> Please stop trying to send attachments to this list, this list strips
> attachments. Post them somewhere and provide a link.
>
> Also, can you please stop 'CC'ing me, just reply to the list,
'CC'ing me
> breaks my mailbox.
>
> Rowland
>
>
>
> --
> To unsubscribe from this list go to the following URL and read the
> instructions:  https://lists.samba.org/mailman/options/samba
>

On 02/01/2023 11:02, Max Serafini via samba wrote:
> Apologies if I annoyed you, in business it is common practice to reply to
> everyone in the thread.
No, it didn't annoy me, it just breaks the thread, instead of appearing 
in my 'samba mailing list' folder, your replies end up in my inbox and I
have to manually move them to the samba mailing list folder. It is 
further compounded by having to enter the mailing list address when I 
reply to list.
> Here are the files.
> 
>
https://drive.google.com/drive/folders/1GIE0npEovJhuMKGdRFY14u3nJ_TszFOO?usp=share_link
> 
> 
You appear to be losing two minutes, as shown in log.smbd:

[2023/01/02 04:49:23.236086,  5] 
../../source3/rpc_server/srv_pipe_hnd.c:138(np_write_send) 
np_write_send: len: 2170
[2023/01/02 04:49:23.658523,  0] 
../../source3/smbd/smb2_server.c:671(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/01/02 04:50:25.348121,  0] 
../../source3/smbd/smb2_server.c:671(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/01/02 04:51:27.624487,  5] 
../../source3/rpc_server/srv_pipe_hnd.c:138(np_write_send) 
np_write_send: len: 2170

The time starts at 04:49:23 and ends at 04:51:27
Tracing this back in code, appears to point to protocol negotiation, 
though I could be wrong.

Why this is happening, wiser heads than myself will have to comment.

Rowland