Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No credits left to send SMB2_SESSION_SETUP #846

Open
Apisero-Connectors opened this issue Oct 15, 2024 · 5 comments
Open

No credits left to send SMB2_SESSION_SETUP #846

Apisero-Connectors opened this issue Oct 15, 2024 · 5 comments

Comments

@Apisero-Connectors
Copy link

Hi @hierynomus,

One of our client's are facing below error-
Error while establishing connection Not enough credits (0 available) to hand out 1 sequence numbers org.mule.runtime.api.connection.ConnectionException: Not enough credits (0 available) to hand out 1 sequence numbers at com.mulesoft.connectors.smb.internal.connection.SmbConnection.(http://SmbConnection.java:99)

Also they have already verified the Server OS is already configured for Min and Max SMB Client Credits.

Also there is no blocking of traffic from their end, they are allowing all connections.

could you please help with this issue.

@Apisero-Connectors
Copy link
Author

Hi @hierynomus , @pepijnve,

Can you please provide any information regarding this issue?

@hierynomus
Copy link
Owner

This happens if the server is not handing out enough credits. Which version of smbj and what server version?

@Apisero-Connectors
Copy link
Author

hi @hierynomus ,

We are using the SMBJ version 0.10.0 .

Let us know if any improvements have been made related to credits managements in the latest version release of the library.

@Apisero-Connectors
Copy link
Author

Apisero-Connectors commented Dec 19, 2024

hi @hierynomus /Team,

The Server version is Windows 2016.

The client has also reported ASYMMETRIC capability unsupported error while using the smbj library (via Mule SMB Connector) version 0.14.0 (Java version 17 and mule runtime version 4.6.0 ) , the same issue was never reported while using SMBJ library 0.10.0 (Java version 8 and mule runtime version 4.4.0).

Could you please confirm if SMBJ library used to support Asymmetric Capabilities in any version of the Library?

If not then what could be the possibility that this error is happening now with latest SMBJ library (0.14.0) and never occured in older version (0.10.0)?

PS - Please note that the SMB Share was always enabled to handle asymmetric capability for both the versions of SMBJ.

@Apisero-Connectors
Copy link
Author

hi @hierynomus,

Could you please help us out here?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants