Add "client min protocol = NT1" to /etc/samba/smb.conf in [global] section
It is required to access NAS which only support SMB v1 with the new Samba v4.11.6 included in Ubuntu 20.04. Samba 4.11.x disables by default SMB v1.
You will probably need the fix for this bug to be published in main Ubuntu repository, as pointed by Opifex.
Answer from Bruno on askubuntu.comsoftware installation - Cannot install Samba client on Ubuntu 20.04 - Unix & Linux Stack Exchange
samba - Windows share smb connection hangs on Ubuntu 20.04 - Stack Overflow
Windows 10 unable to connect to Ubuntu 20.04.3 Samba Server (0x80004005 Unspecified Error) - Stack Overflow
fresh install of Ubuntu 20.04.5 installed samba mac seeing network, but not seeing any folders
Videos
Just so I understand the question: You are trying to access Ubuntu Server 20.04 from another Linux client? If that is so it won't work by default.
You have three choices:
[1] Enable SMB1 on the server:
Edit /etc/samba/smb.conf and under the workgroup = WORKGROUP line add this one - NT1 is samba speak for SMB1:
server min protocol = NT1
Then restart smbd:
sudo service smbd restart
[2] Keep smb.conf as it is but have the client ask for the server and share explicitly either through Connect to Server or in the Location bar as
smb://server-name.local/share-name
The .local part requires you add the avahi-daemon package to your server. You can try it without the .local and just use the host name but that can be problematic. Or you can use the server's IP address.
[3] Use a CIFS mount from the client. For example:
sudo mount -t cifs //server-name.local/share-name /mountpoint -o guest,uid=1000
After some syntax changes you can set this up as a systemd automount in fstab so the user doesn't have to use the terminal.
Exactly as Morbius1 said. Add either (or both) lines to your smb.conf:
client min protocol = NT1
server min protocol = NT1
Same issue here.
Since version 4, both Samba Server & Samba Clients do not allow an older level of protocols negotiation.
You have to enable them in smb.conf file
Edit /etc/samba/smb.conf file (need root permissions)
in the [global] section, add the following line
client min protocol = NT1
Save the file and exit the editor.
You must restart the Samba Service for this change to take effect. In a terminal, enter this command:
sudo service smbd restart
You should be able to access your samba shares successfully. If you cannot connect to your samba share, you can lower even more the protocol security in smb.conf (not recommended), by using:
client min protocol = CORE
Cheers!
Same issue here. It worked out of the box in 18 and 19 without any further step. It's easy to check with a 18,19 live dvd. In a february discussion, they wondered if this out of the box feature should be scraped in 20.04.
Samba.libs and samba.common are installed by default in 18,19, 20.04 but it does not work in the latter Simply installing the full Samba package, which installs /etc/samba/smb.conf. and adding under [GLOBAL] client min protocol = NT1 or CORE does not work. You can access the NAS folder but every object text, jpg etc. is treated as a folder.
There is a bug report relating to NAS and samba. https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1872476 If you install full samba add NT1 to smb.conf (installed by full samba), you can access the NAS share but all objects in the share (avi, jp, txt, etc.) are seen as folders.
So, i've found out that apparently when you have ubuntu 20.04 you can't just set up samba and ssh and just connect to your samba shares, but you need to implement a single line of code which is:
just below the workgroup = WORKGROUP tag, you have to write the code, server min protocol = NT1
after that, you have to restart the service with: sudo service smbd restart
Now i can access the folder, but i have yet to see my folders, but that is next step.
Good luck everyone
The same happened to me, had 2 computers with Ubuntu 22.04, one can see the list of shares from my samba server, the other doesn't.
The samba server has both lines configured:
workgroup = WORKGROUP
server min protocol = NT1
The difference is that one machine is a fresh install of Ubuntu 22.04, the other machine has been updated from 18.04, and for some reason to have nautilus also needs to install gvfs*
I found my issue was the samba client (as I don't have samba server running at all anywhere in my setup).
The desktop client (MATE Caja file manager) would see the NAS server with the wrong name. It would see the NAS box name (mynas) rather than the configured SMB server name (homebackup).
When I used :
$ smbclient //homebackup/mybackup
I was able to connect and browse and copy files via smbclient.
So I went into Caja and manually typed :
smb://homebackup/mybackup
And wala the share appeared.
So for me the only problem is browsing the network and not attaching to shares.
Even after manually connecting in this way the Caja browser still shows mynas instead of homebackup under networks!!!
Just for completeness...as I could not read the exact instructions from the posts. If you have a NAS (e.g. FritzBox) that uses SMB1 you can make nautilus/gio downgrade the smb connection with the following commands, if you don't already have a .smb/smb.conf file (like me):
mkdir ~/.smb
echo "[global]" > ~/.smb/smb.conf
echo "client min protocol = CORE" >> ~/.smb/smb.conf
As an alternative for FritzBox users you could possibly upgrade your FritzBox to SMB2/SMB3 using the experimental Fritz!Lab OS. See https://en.avm.de/service/fritzbox/fritzbox-7490/knowledge-base/publication/show/3327_SMB-versions-supported-by-the-FRITZ-Box/
Then you possibly don't need this workaround, but I didn't test that yet.
The bug with the files showing as folders is fixed now in Ubuntu 20.04 (focal) with smblibs package version 4.11.6+dfsg-0ubuntu1.2
One way to resolve this issue in Samba:
Edit /etc/samba/smb.conf
That file will be added when you install either the samba package or the smbclient package. If you don't want to install samba install smbclient:
sudo apt install smbclient
Then edit /etc/samba/smb.conf and right under the workgroup = WORKGROUP line add this one:
client min protocol = NT1
Another way - and one I prefer myself - is a cifs mount.
I added these two lines to smb.conf in the [global] section and that fixed it for me on Xubuntu 20.04.
client min protocol = NT1
server min protocol = NT1
More details are given here: Broken samba shares
There are two issues here - really three - that have combined to cause the issue you reported.
One is a bug in gvfs ( gvfsd-smb-browse ) that is hard-wired to use SMB1 ( NT1 ) to get a list of the servers and their shares when you browse for them in your file manager.
The second one is Sambas decision to disable ( but not remove ) SMB1 on both the client and server side.
Your samba server can run between SMB2.02 to SMB3. The bug in gvfs causes the samba client to try to access that server using SMB1 which the server cannot understand so it throws an error:
Failed to retrieve share list from server: Invalid argument
There are three ways to get around this issue:
[1] Bypass gvfsd-smb-browse by asking for the server and its share in Connect to Server: smb://server-host-name.local/share-name
Samba client and server will connect using SMB3.
[2] OR do what you just did and set the min server and client to SMB1 ( NT1 ). IT will also connect using SMB3 because the server and client negotiate with one another to determine the best dialect to use after the initial SMB1 connection.
[3] OR use a mount.cifs mount which will also connect using SMB3. This has to be set up in fstab to happen automatically.
If it makes you feel any better a newly installed Win10 machine will not be able to "discover" your samba server at all because it too disabled SMB1. The solution there is the same as for your Linux system: Connect with a \\server-host-name.local OR enable SMB1 on the client side of Win10 which Microsoft really doesn't want anyone to do.
Same problem here. My windows machine were working fine with my local Samba server but my Ubuntu 20.04.4 machine could not. Usually in my Ubuntu file browser I would acces the server with :
smb://server-host-name.local/share-name
but it would not work.
The solution that works for me is replacing the server name by the IP adress of the server. Example:
smb://14.15.16.17/share-name
Like headline says. My mac is seeing the network and I can open it, but i am not seeing any of my folders. see images below. any ideas on how to fix this?
https://imgur.com/PY87AWh
https://imgur.com/vvi5UHi