[Solved] Publishing shares to other computers in the local network

[Member dirkd]

I tested my smb.conf configuration from an mx-19 computer with Thunar on the same network.

With Antix17, when browsing the network, I saw my Antix host, with 5 network shares. Some of them are shared publicly, others ask for password before making the connection. Everything works as expected, and as specified in smb.conf

My new Antix21 installation has exactly the same configuration: same shares, same access rights, same smb.conf. Browsing the network from MX shows my Antix21 host (twice even), but clicking it leads to the error message “Failed to retrieve share list from server: connection timed out”.
[note: two slight exceptions: the network interface in Antix17 is named wlan1, in Antix21 wlan0, this is reflected in smb.conf. Also I might have given .home as domain name for Antix21 and .local for Antix17. Not sure about that anymore]

My TV-set also has networking capabilities. It finds the Antix21 host and even shows the shares. The public ones can be accessed (not so on the MX computer), but the ones that demand a password are shown as empty, even when connecting as root.

What has changed? I noticed the samba version has a slightly increased version number. Should I risk downgrading? And what are the chances this solves the problem?

• This topic was modified 1 year, 5 months ago by dirkd.

[Member dirkd]

Helpful

Up

1

::

I perused half the internet before I came across something that works. First, in Thunar, you have to use fully-qualified-device-names, e.g. ‘dokux.local’ in stead of just plain ‘dokux’. Then you can see the list of all samba shares on the server.

Then, to make contact with a password-protected share, you have to add a seperate samba password on the server, like this
sudo smbpasswd -a <username>
Then, after enteriing your sudo password, you get to enter the samba password twice. The <username> should be an existing user on the server, because he needs the right permissions on the server to access the shared resource.

Then, from another computer, when asked for a password to access a samba share on that server, you can enter the <username> and the samba password in case it’s different from your normal user password.

Which leaves me with one big question. Why was all that unneeded in Antix17?

[Member dirkd]

Helpful

Up

0

::

Seems it was necessary in Antix17 after all. Making a new user in Antix17, assign him a samba share, and trying to access that share from another computer with his login password only didn’t work. I must have added my existing users as samba users, using the same passwords for both roles, and forget about it altogether.

Who was it again that once said ‘Set it and forget it’ was the ideal in system management?

I feel a little embarassed, but hey, it was more then 4 years ago…

[Author]

Posts