Open pbuchholz123 opened 1 week ago
Are you by chance using Kerberos auth in your test environment? Have you set any credentials with the ClientConfig()
. It sounds like the session is missing for this particular server and user and so it's trying to create a new one. SMB authentication by default tries to use Kerberos if available with a fallback to NTLM. In this case there is no username/password specified so if Kerberos fails then the NTLM fallback fails with that particular error.
Hello,
no, i don´t use Kerberos. I am not using the ClientConfig() object, i use it directly like this:
import smbclient
[...]
smbclient.register_session(server, username=username, password=password)
I will try giving ntlm as the auth_protocol in the register_session method, maybe it will help. Unfortunately i will have to wait a week to give some feedback :/
Cheers
Hello,
firstly, great lib. But we kinda face a problem we can't identify... So let me give u some context.
We have a python script running inside a docker container observing a local directory inside that container. If something goes in that directory, the script does different things. That script observes that directory 24/7 and one
action
is to copy the content of that local directory to an SMB share (Win 2k16 File Server). That whole process works like charm for exactly 7 days. After 7 days, we receive the following error/s in our logs...Extracted traceback
The script continues running but throws that error over and over again. I have to restart the container, and it works again for the next 7 days...
Script runs with python version 3.12, smbprotocol version is 1.13.0
Now the weird part.. We have another python script running inside a container doing literally the same thing as described above. Copying a local file to a SMB share. But this script runs with python version 3.10 and smbprotocol 1.9.0. But here we don't have this problem.
Anyone else having this problem?