KDE: connect to a NAS with samba

General system Newbie
1

Hy

New to Endeavour, I trying to connect my NAS using samba on Dolphin

After 3hours of trying, I’m losing hope

Here my smb.conf ( I need to create one because I don’t have one initially in the folder)

And i think something is wrong inside or not, don’t known

[global]
workgroup = WORKGROUP
security = user
map to guest = bad user
wins support = no
dns proxy = no

[public]
path = /home/sleepy
guest ok = yes
force user = nobody
browsable = yes
writable = yes

Here the config i took for someone

In the firewall, i see the ip adress for my nas and his protocol, so I set a exception for it

But still saying “ not connected”

And when I try this command smbclient -L hostname -U%

I have this error: tree connect failed: NT_STATUS_ACCESS_DENIED

I have started samba service and avahi service and set up a exception for samba in the firewall using a command

Noting I don’t have this file for avahi:

/etc/systemd/dnssd/smb.dnssd and even the folder dnssd

Samba is actually working and running because In dolphin → network → SMB files, I see my computer but not my NAS

Sorry is my way of writing is a mess, I trying to have the maximun of informations

Thanks for your help

2

Are you trying to share files FROM your NAS or FROM your EnOS computer? You don’t need to configure Samba on your client system unless you intend to share files/folders FROM that client to other clients.

You DO need to configure Samba on your NAS and set up share access permissions. If you don’t set up the SMB shares on your NAS, then nobody on the network will see them. On your NAS you can type this into the NAS terminal to see current status: samba status

I ran into a similar problem where my EnOS laptop could see the SMB shares on my unRAID server (NAS) but not write/modify them. Here’s how I fixed my permissions problem in Dolphin.

In fact, the ONLY way I’m able to achieve write access permissions in Dolphin, is to right-click in the left pane and select “add entry”, then hardcode the user/password into the path (super sketchy): smb://user:password@tower.local
(substiture ‘tower.local’ with your NAS static IP address if you don’t have LAN name resolution enabled.)

image
image613×402 23.9 KB

3

Thanks for you answer

From my NAS a Asustor NAS to be more precise.

SMB is already activate on NAS with “windows discovery"

You don’t need to configure Samba on your client system unless you intend to share files/folders FROM that client to other clients.

That news :slight_smile: why after hours of searching, nobody say this .

The think is the way my NAS is configure, I manage to connect to it with cachyOS KDE, after litteraly 7hours of work with just pure luck so I don’t known how. ( so why i don’t use cachyOS because the system hard crash and destroy itself for no reason :frowning: )

So my NAS is ready to share but EnOS or dolphin can’t or simply won’t see it

And every distro I try, dolphin always don’t want to see my NAS

I do the same as CachyOS add a exception on the firewall

I start avahi and Samba

Trying to connect like you do smb://user:password@tower.localeverytime I try, he refuse

4

Hey! Good to have you with us.

Question for you, - do you genuinely need SMB? Would NFS not be easier?

  1. Generate a user on your NAS with the same GID as your user on your Linux box.
  2. Set permissions for that user to read write.
  3. Apply the permissions to your NAS shares.
  4. Set your fstab to have the mount points defined.

Here’s an example line in /etc/fstab:
your NAS IP:/yourNASfolderpath /mnt/yourlocalmountfolder nfs defaults,x-systemd.automount,_netdev 0 0

That’s really it, - just make sure you sudo chown username:username /mnt/<folderpath on Linux box>

There are a handful of threads on the forum explaining deeper, - dig in, half the fun is learning there’s usually a better way :slight_smile: Enjoy the journey!

5

Instead of NFS, why not go with SSH?

Also, EndeavourOS has firewalld enabled by default.
To see if it is a firewall problem, enter

sudo systemctl stop firewalld

this will disable the firewall until the next reboot.
See if it works with the firewall out of the picture.

samba
samba1000×758 80.1 KB

samba and samba-client are not enabled by default (no check mark in the box).
If you are getting files from the NAS, samba-client (your EnOS is a client) should be enabled.

However, IMHO for security reasons, SSH and SSHFS would be a better choice. But it boils down to…your computer, your rules.

Pudge

6

I’ve been struggling with smb shares off and on for over a year. My final solution was to uninstall firewalld and install ufw. No problems since.

7

I had a problem accessing SMB shares in Dolphin (KDE) also. In the end I mapped the entry with user:password in the path which fixed it for me. Link to info: KDE: connect to a NAS with samba - #2 by MrSmartepants