Can no longer access NAS on clean install of 20.04

8,173

Solution 1

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.

Solution 2

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

Share:
8,173

Related videos on Youtube

George
Author by

George

Updated on September 18, 2022

Comments

  • George
    George almost 2 years

    I did a clean install of 20.04. In files I can see my NAS but can't access it as it does not give the password dialog box.

    There are other posts saying to modify the smb.conf file to make this work but I don't seem to have this file with a fresh install. Is there a way to fix this or is this version of Ubuntu basically useless to anyone with an older but perfectly functional NAS?

    • adasiko
      adasiko about 4 years
      What is SMB protocol version on NAS? With SMBv1 there are too many problems with Ubuntu 20.04. It’s deprecated protocol. samba.org/samba/history/samba-4.11.0.html
    • George
      George about 4 years
      The NAS is v1 and I know it is outdated and that there are security issues. That doesn't change the fact that you should have an option to access it. Even Windows gives you the option. I have no issue modifying the SMB.conf file like most posts about this are saying but with a clean install that file doesn't exist. Is there any other way of enabling v1?
    • ross minet
      ross minet about 4 years
      For me, it is now solved after today's (may 21) Ubuntu upgrade to 2:4.11.6+dfsg-0ubuntu1.2. With full samba installed and "client min protocol = NT1" add to smb.conf I can mount the NAS share and the objects (avi, jpg, etc.) are seen and treated properly as objects not as folders. I haven't tried with just samba-common installed.
    • Wellwisher1348
      Wellwisher1348 almost 4 years
      I found this article very helpful in resolving my issues with setting up SMB Server in Ubuntu 20.04 lts with a static IP, and mapping the shared drive in Windows 10 Enterprise: linuxconfig.org/… The main issues that resolved the connection were with turning on the MS Services that were inactive by default.
  • ross minet
    ross minet about 4 years
    Unfortunately, it does not work on Gnome 3.36 Ubuntu 20.30. You can mount and access the NAS share but every object (avi, jpg etc.) is seen as a folder!
  • guntbert
    guntbert about 4 years
    Please explain, what that add-apt... command does and why it helps.
  • ross minet
    ross minet about 4 years
    This comment refers to a discussion on a bug. If you add client min protocol = NT1 to smb.conf after a full samba install, you may access the NAS share but every objet is seen as a folder. So it's useless. In the discussion, someone is mentionning a PPA (a repository) solving the problem, for the sake of discussion. They say the solution is coming. Adding PPA's is not a great idea for security reasons. It's a widespread bug waiting for a solution.
  • ross minet
    ross minet about 4 years
    For many people with router from a ISP, this solution did not work until today's (may 21) Ubuntu upgrade to samba 2:4.11.6+dfsg-0ubuntu1.2. With the previous samba version all the objects (avi, jpg, etc.) in the NAS share were seen and treated as folders.