https://bugs.kde.org/show_bug.cgi?id=445557
Tobias G. <tobi.goerg...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|UPSTREAM |---
Ever confirmed|0 |1
--- Comment #2 from Tobias G. <tobi.goerg...@gmail.com> ---
(In reply to Harald Sitter from comment #1)
> Sounds like https://bugzilla.samba.org/show_bug.cgi?id=14326
>
> I do rather feel like the problem is on the windows side though cause I also
> didn't manage to make it work from windows 10 to another windows 10
Yes and no.
As described in the linked bug report, smbclient asks me for a password, but
lets me access it nonetheless with anything entered as username and password.
KIO accepts until version 4.13 the windows PC name and anything as password,
with smbclient > 4.13 nothing works.
I can verify this since 4.15 was pre-installed on my machine and manually
compiled 4.13, which made it work.
It's also not an issue on Windows machines, they just don't ask me for a
password at all.
So yes, the bug applies here too, as it asks me for credentials, but it's not
the only bug here, as KIO doesn't seem to allow access to unprotected Windows
shares at all anymore.
The Windows machines have a specific setup, as a local account without user
password is in use instead of a Microsoft account, SMB1 is activated and
password-less shares are activated.
Accessing a Windows share with a Microsoft account and it's credentials works
fine.
Most of what I've written above is already stated in the linked bug report,
with another user having an issue with KIO and smbclient > 4.13, so it might be
worth a look.
--
You are receiving this mail because:
You are watching all bug changes.
