upgraded to Ubuntu 20.04, unable to access older NAS and samba servers

Question

after upgrading to 20.04, I am now unable to access samba shes on older nas or older samba servers.

I have tried editing the smb.conf, and adding "client min protocol = CORE". This partly fixes the issue and authenticates and lets you view folder inside the share, but then all the files inside appear as folder. I am unable to copy the files out to access, and cannot open them in caja, which I think will be the same in Nautilus.

Other than that I am enjoying 20.04 :)

thanks in advance

Bigley

Solution

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!!!

Comments

[Nmath]

I think this is a bug: askubuntu.com/questions/1233727/…

[bigley Ling]

It is a very annoying bug, as there prob literally millions of Linux users that still need access to these older protocols. It is ok to disable on a default install, but there really needs to be options to re enable as necessarily, or warning dialogue when connecting to older protocols. The requirement to install a patch PPA to fix being able to access network shares is more of a downgrade than an upgrade

[bigley Ling]

yer guess so, assume once a fix comes out, all I do is remove the ppa to uninstall the patch? Will remember not to upgrade so fast next time. Just thought 20.04 being an lts version would be extra stable.

[bigley Ling]

Hi, thanks for the prompt reply. I would really prefer to use samba, as i attach my network drive inside the gui as needed as i connect to different networks, so putting permanent cifs links in fstab would not be feasible.

[bigley Ling]

I tried adding the fix PPA and it installed successfully, but the issue of objects or files still appears as folders. My distro is Ubuntu Mate. Lastly, this issue only happens to my older NAs, the newer one only needs the NT1 compatibility enabled. any help is greatly appreciated :)

[Morbius1]

Please see my edit above. I don't want to force you to do a cifs mount, but .... My edit is just a suggestion that makes it so it will mount only when you want it to mount.

[bigley Ling]

Ok managed to get your PPA fix working! (test on old Ubuntu samba share server)This PPA did not work launchpad.net/~panfaust/+archive/ubuntu/samba-bugfix, but this one did launchpad.net/~sergiodj/+archive/ubuntu/samba-bug1872476-v2 which was from the bugs.launchpad. Many thanks Morbius1, hope others can benefit from this soltuion too :)

[Morbius1]

Updated my answer to your PPA link. Thanks