-
Notifications
You must be signed in to change notification settings - Fork 184
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
Comments
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. |
@TalAloni The problem is that the library does not properly handle smb v2 status_pending response. |
The server? The Client? please provide additional details and a WireShark capture demonstrating the problem. |
Sorry, the client.
I will try to make you a capture.
Basically I make a create request with smb 2 client, the windows server
answers with status_pending (I think it is caused by the fact that is a
large file), but the library does not handle it and return an error.
Regards
Le mer. 19 juin 2019 à 05:50, TalAloni <notifications@github.com> a écrit :
… The server? The Client? please provide additional details and a WireShark
capture demonstrating the problem.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#27?email_source=notifications&email_token=ABFEOQR7H23OIL3MAO74MY3P3GUIXA5CNFSM4HZCQIJKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYATGZA#issuecomment-503395172>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABFEOQRCZFVT2INVAYCUTZLP3GUIXANCNFSM4HZCQIJA>
.
|
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: |
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
The text was updated successfully, but these errors were encountered: