-
Notifications
You must be signed in to change notification settings - Fork 53
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
Notify failes without SMB v1 #56
Comments
if you put "client min protocol = SMB2" in smb.conf, you get the same result. |
If I put "client min protocol = SMB2" and "client min protocol = SMB3" under [global] in smb.conf I can connect and get no errors. But there is nothing being reported changed. With SMB1 on, it works fine. |
This is an upstream limitation of smbclient which only implements notify for smb1 With 2.0.3 you should at least get a relevant error message |
I can confirm this. With an smbclient 4.9.3 and smb2 the notify command works. But what is the first smbclient version which supports notify with smb2? You can test your version of smbclient with:
then type:
If your version supports notify with smb2 the output will be empty until a change event occur. |
Maybe I found the first working smbclient version. Can somebody confirm this with a smbclient 4.7.8? |
works for me with version 4.10.8 and even SMB3 as well. |
Edit: I am talking about the notify function here.
The text was updated successfully, but these errors were encountered: