Created attachment 15871 [details]
output of smbc debugging
The issue mentioned in my summary was already reported in KDE bugzilla
My client runs Arch Linux + samba and libwbclient 4.10.10 + KDE Plasma 5.18.3 desktop environment.
My server runs Windows 7 Professional.
I'm using a linux client to try access a share from a Windows server.
The client always asks for password to list and access the share despite it is passwordless.
Client lists the shares available when I enter fake "*" username and password
or another fake username and password. But I need to type username and password
that I use to start the user session of Window server when I want to open any
passwordless share from it.
You can read a detailed explanation and watch screen recordings showing the issue
in the following link
As we can read in the following link, KDE developer Harald Sitter thinks that something is wrong inside libsmbclient
I'm attaching the output of smbc debugging according to instructions
from the following link
FWIW, from the info in the kde report I would infer that currently the AutoAnonymousLogin probably attempts to login with an empty password which windows servers seem to take offense with (probably because of some default secpol in win7+).
An easy solution then would be to send a random password instead of no password in the AutoAnonymousLogin. For all I know that will break something else though.
sending a random password or no password looks like a very bad idea to me as this will increase the bad logon counter. I also suggest to remove the AutoAnonymousLogin if there is something like that. Something like that is asking for trouble in many environments. If the current user had a krb5 ticket, then this can be used to try authenticating the user. But don't try guest logons or random passwords. please.