error when connecting to smb server

Bug #1855758 reported by Mika
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
samba (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Befor a while when I connect to smb server (nas) permanently appears

"Error while getting peer-to-peer dbus connection: Operation was cancelled"

Nevertheless, it has connected.

Well, last weekend any samba packages were updated, now the connection fails.

I think, it is related to this bug:

https://bugs.launchpad.net/bugs/1849859, but I do open here a new report, maybe its better so.

There is now need of authentification on this nas, the bug has existed since these updates.

Revision history for this message
Mika (70mike) wrote :
Revision history for this message
Mika (70mike) wrote :

And this:

Revision history for this message
Andreas Hasenack (ahasenack) wrote :

Samba 4.11.x disabled SMB1 by default both for the client and the server (https://www.samba.org/samba/history/samba-4.11.0.html):

SMB1 is disabled by default
---------------------------

The defaults of 'client min protocol' and 'server min protocol'
have been changed to SMB2_02.

This means clients without support for SMB2 or SMB3 are no longer
able to connect to smbd (by default).

It also means client tools like smbclient and other,
as well as applications making use of libsmbclient are no longer
able to connect to servers without SMB2 or SMB3 support (by default).
"""

If your NAS Server only supports SMB1, then this could be the problem.

Can you try setting this in the [global] section of /etc/samba/smb.conf in your ubuntu machine and try again please:

client min protocol = NT1

You might need to logout/login again.

Revision history for this message
Mika (70mike) wrote :

This worked for me, many thanks.

(Ich hoffe, nach dem nächsten Update wird dieser workaround nicht auch weggepatcht.)

But the problem with the error ( see attachment) stays on, I can click it away, but I don't know, where it comes from.

Revision history for this message
Andreas Hasenack (ahasenack) wrote :

I'm not sure we can add that to the package. There is a world-wide effort to get rid of the SMB1 protocol. Even modern windows machines have it disabled by default I think.

You are probably better off in changing the configuration of your NAS to support more modern protocols. Have you inspected that configuration? It could be something simple to change.

Revision history for this message
Andreas Hasenack (ahasenack) wrote :

Regarding the dbus error, I have never seen that before. I'll try to get a 20.04 desktop running.

Revision history for this message
Sebastien Bacher (seb128) wrote :

How do you connect to the server? What desktop environment are you using?
Could you add a 'journalctl -b 0' log from a session when you triggering the issue?

Revision history for this message
Mika (70mike) wrote :

Hallo Andreas, the configuration of the NAS does not allow for anything in this aspect.
(look at the attachment).

The dbus error I have never seen that in a older Ubuntu too. Its a normal NAS connecting to it via smb.
In the journalctl -b 0 there is no entry.

(Ich habe es paar mal versucht, zum Zeitpunkt der Verbindung und Fehlermeldung ist kein Ereignis zu sehen.
Übrigens manchmal kommt auch keine Fehlermeldung in der gesamten Sitzung, aber wenn sie kommt, dann erscheint sie nach jedem Klick auf dem NAS und muss permanent weggeklickt werden.)

Revision history for this message
Mika (70mike) wrote :

I have installed a minimal server Ubuntu 20.04 mit LXQT as desktop environment.

If you test it yourself, here are my installation command:

sudo apt-get install lxqt-core kde-window-manager intel-microcode sddm plasma-nm qterminal

Revision history for this message
Andreas Hasenack (ahasenack) wrote :

That NAS seems pretty old, you might have to live with the configuration change to downgrade the protocol to SMB1. Maybe you can ssh into it and find out what samba version it's running, and tweak its config manually. I find it weird that samba, even from 2011, would reject SMB2 connections, or not work with them. Have you also looked for firmware upgrades?

About the dbus error, lxqt is in the universe repository and thus not strictly supported. If you could reproduce the error with a normal ubuntu desktop, that would be better. I tried a 20.04 desktop the other day, standard ubuntu-desktop, and could connect to my NAS just fine (a synology Ds216), but it doesn't show up in the "windows network" tab, just under "other locations".

Revision history for this message
Mika (70mike) wrote :

Vielen Dank dir erstmal, wenn ich mal wieder Zeit übrig habe, kann ich ja mal auf einen anderen Desktop umstellen.

Revision history for this message
anthony olszynski (aktony) wrote :

Ok sorry but the massages from this board are landing in my spam folder that i have see the answers and question today.

The problem was that i have a wrong setting.
the error was that I had set in the pat.d common session and all other files that manage the login the following.

session optional pam_krb5.so minimum_uid=1000

It must by the same id what i have set in my smb.conf
The range from my idmap that was 3000000-4000000.

Also i have set my pam properties to

session optional pam_krb5.so minimum_uid=300000-4000000.
And i can use passwd to change my localun unix aeé

session optional pam_krb5.so minimum_uid=3000000-400000

And this in all files.

Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

So it turned out to be a configuration issue.
Thanks Anthony for coming back and sharing that info.

Marking the bug as invalid, and even if no fix was needed that into might help others affected by the same.

Changed in samba (Ubuntu):
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.