I have just realized that when it fails it alway take 20 seconds.
That seems to match the default smbclient timeout:
-t|--timeout <timeout-seconds>
This allows the user to tune the default timeout used for each SMB request.
The default setting is 20 seconds. Increase it if requests to the server
sometimes time out. This can happen when SMB3 encryption is selected and
smbclient is overwhelming the server with requests.
Maybe the SAMBA server is sometimes overloaded?
Andrea
On Mon, Jul 31, 2023 at 7:31?AM Andrea Cucciarre <acucciarre at
cloudian.com>
wrote:
> Hello,
>
> I am running a Samba server release 4.13.17 as a DC member.
> On another system I periodically run the the command "smbclient -NL
> <samba server IP> -g" to monitor the status of the Samba server.
> Sometime (not always) the smbclient command hangs for few seconds and then
> fails returning the following error message:
>
> "smb2cli_req_compound_submit: Insufficient credits. 0 available, 1
needed
> session setup failed: NT_STATUS_INTERNAL_ERROR"
>
> Do you have any idea about what could be the cause of this odd error or
> any smbclient command options that could avoid it?
>
> Andrea
>
>
--
Andrea Cucciarre'
Global Technical Support Manager
Cloudian Inc.