Unable to share Public folder after upgrading to 22.04 Mate

Asked by apinunt

I believe in the past we had to install caja-share to enable sharing the Public folder, so we installed caja-share and samba, rebooted, and brought up home folder in caja, right clicked on Public, and clicked on Sharing Options. A Folder Sharing GUI opened and we enabled Share this folder, Share name Public, checked both allow others and Guest access, and then clicked on Create Share.
'net usershare' returned error 255 was the response we got, though I can now see the computer in Network on my other computer, but not the Public folder, just Print$.
What are we missing?

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu ubuntu-mate-welcome Edit question
Assignee:
No assignee Edit question
Solved by:
actionparsnip
Solved:
Last query:
Last reply:
Revision history for this message
actionparsnip (andrew-woodhead666) said :
#1

What OS are the clients going to be?

Revision history for this message
apinunt (apinunt) said :
#2

I'm not sure what you're asking, I said we upgraded to Ubuntu 22.04 Mate, and just sharing files between computers over the LAN connection. All our computers are running Ubuntu Mate, 2 now upgraded to Ubuntu 22.04 and all others still running Ubuntu 21.10 Mate until we can get 22.04 working.

Revision history for this message
actionparsnip (andrew-woodhead666) said :
#3

I'll rephrase. There are systems connecting to the share when you set this up. Are they using Windows or MacOS or are they Linux systems as well?

Revision history for this message
apinunt (apinunt) said :
#4

As I said, all our computers are running Ubuntu Mate Desktop 21.10, except 2 which we just upgraded to Ubuntu 22.04 Mate Desktop, and our sharing between them is done over our in house LAN which also provides us an Internet connection. All sharing is Intranet,

Revision history for this message
actionparsnip (andrew-woodhead666) said :
#5

Ahh I see. Then if you install openssh-server on the file server then you can mount sshfs easily. If you swap ssh keys then this will be passwordless.

Revision history for this message
apinunt (apinunt) said :
#6

I just installed "openssh-server" using the Software-boutiqueand I still get the same message when I right click on Public, click Sharing options, and Check Share this folder, folder name Public, and enable both others and guest access, and then click Create Share. 'net-usershare' returned error 255

Revision history for this message
actionparsnip (andrew-woodhead666) said :
#7

It's not done through sharing using openssh-server. The server side is now done.

You can run the below on the clients

sudo apt install sshfs

You can now mount sshfs using Nautilus on the client side.

Revision history for this message
apinunt (apinunt) said :
#8

I can see the other computer over the network, but I can't make the Public folder shared in it.
I just added sshfs, and tried to share Public, and still get the same error.

Revision history for this message
actionparsnip (andrew-woodhead666) said :
#9

You don't need to share public. The server side is done.

I'll give you the command to mount it if you like. What is the path to "public" on the server side?

Revision history for this message
apinunt (apinunt) said :
#10

And we;re running Ubuntu Mate Desktop version which uses Caja, not Nautilus.
I have not had any problem opening Public in the Ubuntu 21.10 computers from the 22.04 computers.
It's only trying to open Public in the 22.04 computer which I cannot make shared, and get an error each time I try, though I can see print$ over the network but not Public.

Revision history for this message
apinunt (apinunt) said :
#11

Public is the system created folder in my home folder.
We would like to be able to share as in the past, by using the menu, Places, Network, and selecting one of the computers connected to the Network we wish to send files to or retrieve files from.

Revision history for this message
actionparsnip (andrew-woodhead666) said :
#12

What is the name of your user?

Revision history for this message
apinunt (apinunt) said :
#13

If you're thinking the smb://computer.local/ ...
That only works if I omit Public, and it shows the computer with print$
If I add Public to the command, it returns an error, No such file or directory and does the same if I try to connect anonymously or login with a password.

Revision history for this message
Best actionparsnip (andrew-woodhead666) said :
#14

OK, I'll make up a username. Let's use "foo". This is the username on the server side.

Firstly, grab the remote certificate with:

foo@remoteserver

One you type "yes" you can log in then press CTRL + D to disconnect. You can map the remote "Public" folder, with:

mkdir $HOME/RemotePublic
sudo sshfs -o allow_other,default_permissions foo@remoteserver:/home/foo/Public $HOME/RemotePublic &

You will be asked for the password of "foo" on the file server side. Obviously, change "remoteserver" to your actual servername or even IP address. Change "foo" (both times) for the username on the remote file server that you login to Ubuntu with.

E.g. (For a user "pi" on "fileserver01")

mkdir $HOME/RemotePublic
sudo sshfs -o allow_other,default_permissions pi@fileserver01:/home/pi/Public $HOME/RemotePublic &

This will mount the folder securely and without Samba which you don't need. If you swap SSH keys then you won't be asked for passwords here

Revision history for this message
apinunt (apinunt) said :
#15

That's more a work around than a resolution to the issue.
In the meantime, I've been able to get bluetooth working both directions between al our computers, and can move files that way until we can resolve the issue sharing the Public folder.
But thanks for your help.

Revision history for this message
actionparsnip (andrew-woodhead666) said :
#16

You can use something better than Samba if both sides are not Windows

Revision history for this message
apinunt (apinunt) said :
#17

All our computers are running Ubuntu.
The issue is making Public shared without getting an error message,