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

STATUS_PENDING not taken in account #27

Closed
gldfdp opened this issue Jun 18, 2019 · 5 comments
Closed

STATUS_PENDING not taken in account #27

gldfdp opened this issue Jun 18, 2019 · 5 comments

Comments

@gldfdp
Copy link

gldfdp commented Jun 18, 2019

Hello,

it seems that the library does not take in account CreateMessage with Response status STATUS_PENDING. It should be wait for the next answer with same PID. I have this status for large file requests.

From https://wiki.wireshark.org/SMB2

If a SMB2 command can not be completed immediately the server will respond immediately with STATUS_PENDING and specify a value for the PID that the client can use later to Cancel the request. This STATUS_PENDING reply has the P bit set to 1 to indicate that the PID is valid. Once the command completes later the server will send a second reply to the command, this time still keeping the P bit set to 1 and repeating the same PID as in the initial STATUS_PENDING reply.

@TalAloni
Copy link
Owner

it's not clear from your text what your issue is and which component of the library is not behaving as expected. moreover, you quote from a document that is not the official MS-SMB2 specifications.

@gldfdp
Copy link
Author

gldfdp commented Jun 18, 2019

@TalAloni The problem is that the library does not properly handle smb v2 status_pending response.

@TalAloni
Copy link
Owner

The server? The Client? please provide additional details and a WireShark capture demonstrating the problem.

@gldfdp
Copy link
Author

gldfdp commented Jun 19, 2019 via email

@TalAloni
Copy link
Owner

If you're getting STATUS_PENDING when sending a Create request it usually means one of your Create parameters is incorrect. I suggest you examine the parameters sent by Windows in order to figure out how to correctly create a file, there are also examples here:
#9

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