> Try setting the PYSMBC_DEBUG environment variable to "1"
> before running your test program. What output do you get?
Sorry I wasn't able to deliver this by now..
I just tried setting that variable, and calling:
PYSMBC_DEBUG=1 python test.py 2>&1 | tee logout_pysmbc_04-oct-2011.txt
... and the logout_pysmbc_04-oct-2011.txt is attached.
I tried to again obfuscate / search/replace all direct mentions of the work server addresses, and convert them to strings like in the original post example - except, for better accuracy, now it shows 'my.workdomain.com' for the domain I'm member of, printserver is thus 'printserver.workdomain.com' - and so the "master" site is "workdomain.com".
Note, I remember I did something at a certain point to increase log verbosity, but I can't really remember what - so this log may actually generate a bit more data than what PYSMBC_DEBUG=1 would cause..
Anyways, let me know if I can assist further with this.
Hi @till-kamppeter, @twaugh,
Many thanks for the responses!
> Try setting the PYSMBC_DEBUG environment variable to "1"
> before running your test program. What output do you get?
Sorry I wasn't able to deliver this by now..
I just tried setting that variable, and calling:
PYSMBC_DEBUG=1 python test.py 2>&1 | tee logout_ pysmbc_ 04-oct- 2011.txt
... and the logout_ pysmbc_ 04-oct- 2011.txt is attached.
I tried to again obfuscate / search/replace all direct mentions of the work server addresses, and convert them to strings like in the original post example - except, for better accuracy, now it shows 'my.workdomain.com' for the domain I'm member of, printserver is thus 'printserver. workdomain. com' - and so the "master" site is "workdomain.com".
Note, I remember I did something at a certain point to increase log verbosity, but I can't really remember what - so this log may actually generate a bit more data than what PYSMBC_DEBUG=1 would cause..
Anyways, let me know if I can assist further with this.
Thanks again - Cheers!