-
Notifications
You must be signed in to change notification settings - Fork 94
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
Don't connect to SMBv2 server #214
Comments
@joelfranco : can you adjust the port parameter in your connect() call to use 139? It seems that your smb server seems to respond on port 139. |
Hi @miketeo, I changed the port. Same issue:
And the wireshark capture:
Observe that smbclient works with 445 port. Thank you very much |
It will be good if the wireshark capture can provide more information on the server's response to the smbclient's Negotiate Protocol Request. That may reveal why the server is not responding to pysmb's connection request; the server could possibly be using a dialect that is not supported by pysmb. |
Hi Miketeo, in this print you can see the first packet after the TCP handshake and following it, just retransmissions. And this one is with the working smbclient: Observe that in this one, the protocol is described as "SMB2" by wireshark and the pysmb packet it calls just "SMB", and that packets are very different. Is it clearer now? Thank you. |
Your server seems to be supporting the new SMB2 variants and SMB3 protocols which is not supported by pysmb. |
Hi,
I can't connect to a (supposed) smb2 host. I have no control or detailed info about the server. I can't connect to it using smbclient:
smbclient //ip/share -U DOMAIN\\USER%PASS:
wireshark:
But with pysmb, the server host do not reply with any errors and the pysmb can not detect that it's talking to a smbv2 server to switch itself to smbv2:
wireshark:
What is wrong?
Thank you
The text was updated successfully, but these errors were encountered: