FS#48987 - [smbclient] Unable to connect to a samba share with a file browser with 4.4.2-1
Attached to Project:
Arch Linux
Opened by hopimet (hopimet) - Sunday, 17 April 2016, 06:53 GMT
Last edited by Andreas Radke (AndyRTR) - Tuesday, 04 May 2021, 12:34 GMT
Opened by hopimet (hopimet) - Sunday, 17 April 2016, 06:53 GMT
Last edited by Andreas Radke (AndyRTR) - Tuesday, 04 May 2021, 12:34 GMT
|
Details
Description: After upgrade to smbclient 4.4.2-1 I am unable
to connect to a samba share with a file browser (I tried
thunar, dolphin or pcmanfm). The connection window asks for
a login and password user but does not connect and does not
return any error message. When I enter the login and
password it returns to the connection window and asks for a
password again and again...
It is important to note that I can mount this samba share in a terminal (mount -t cifs works fine). Downgrading to smbclient 4.4.0-1 and libwbclient 4.4.0-1 solved the problem Additional info: * package version(s) : smbclient and libwbclient 4.4.2-1 Steps to reproduce: Upgrade smbclient to version 4.4.2-1 and connect to a samba share via a file browser. |
This task depends upon
Closed by Andreas Radke (AndyRTR)
Tuesday, 04 May 2021, 12:34 GMT
Reason for closing: Fixed
Additional comments about closing: assuming this has been fixed for a long time...
Tuesday, 04 May 2021, 12:34 GMT
Reason for closing: Fixed
Additional comments about closing: assuming this has been fixed for a long time...
Also, with smbtree I get some random error:
mkdir failed on directory /var/cache/samba: Permission denied
If I create this directory, I get no error but still doesn't connect.
On doublecmd I get forced to use username.
Reverting to previous version solved the issue.
The Error Message in CUPS was: "Session setup failed: NT_STATUS_ACCESS_DENIED"
https://bugzilla.samba.org/show_bug.cgi?id=11834
Can someone verify if it is 'anonymous user' issue?
That work for me.
I find this in AskUbuntu http://askubuntu.com/questions/758860/samba-share-user-password-error-after-update
Good luck
If so, maybe the windows server is not updated and there is an incompatibility between smbclient and win server.
In my case, I try to connect to win xp computer. It is difficult to debug smbclient because it is at my work. If I find some time I'll try to debug it.
As proposed by Olivier Brunel, I'll wait the next update. I think the easier way to deal with this bug is to downgrade the client.
Before the release, I tried to compile the 4.4.3 version but I had the same problem. I thought that there might need some patch so I waited the official release.
I compiled the 4.4.0 with the security patch and again the same problem.
Did something changed at login users?
I don't know if it is client's or server's problem.
Is it because I try to connect to Win Xp which is unsupported OS?
Can someone verify if the latest package works?
@Alex,
I think the bug is related to the client, not to the server, because downgrading the client works, without changing the server configuration.
I'm also affected by this issue and cannot connect from my win7 machines on my server.
https://www.samba.org/samba/history/samba-4.4.2.html
Still asks for password when connecting to Windows network and shares.
At the history-log info they use technical meanings of what changed. (Which I cannot understand at all)
Is there something to write at the wiki for this? Maybe there is no more bug but we might have to configure the client to communicate right and secure.
A workaround is proposed here (I have not tried) but this is far to be ideal for security, unless your samba share is only accessed from your local network.
https://discussions.apple.com/thread/7534687?start=0&tstart=0
"I ended up using quite a simple work-around (obvious now with hindsight), which was just to create a dummy guest account (i.e. a named account called "guest") and send an email out to my users. Not ideal, but I didn't end up needing to add it explicitly to my existing shares because simply signing in with a valid user was enough to bypass the bug."
Edit - This works when connecting to password-less Windows network shares. Have not checked connections to Samba server.
Since the functionality has changed a bit I was confused as to how this works.
Now to login anonymously to a windows share all I had to do is - enter current USER password (instead of choosing "Connect anonymously" option).
Edit - actually it still works if one types anything in the place of the password... and the username can even be changed to anything... And it still works. By anything I mean literally anything - numbers, letters, symbols (I haven't tried emoticons :D).
Although it still poses problem, if for example the user doesn't know the password. But that is a different issue altogether.
I still can't login either anonymously or as an identified user (registered in the samba database). Could you give the samba version of your server, please?
As I previously posted I suspect a compatibility problem between the new version of the client when used to an old version of the server. If so, may be the configuration of the server would need to be changed.
I forgot to specify in the last comment that it works when connecting to password-less Windows network shares and not Samba server.
I edited the comment to include that.
Sorry I just realized that this bug was filed against Samba shares and not Windows shares. (facepalm)
Although it did affect both.
username: RANDOM
domain: RANDOM
password: RANDOM
where RANDOM is whatever word.
I think this might me a new bug for upstream...
Also, I don't have to use 'cifs' module (via modprobe) and no 'wins' at /etc/nsswitch.conf
Is this strange?
Check smbpasswd and pdbedit for your users and try to recreate them.
And using no password option with smbpasswd broke it too, I had to use simple empty password and hit return on creation.