1y ago

SMB Share - Help Before I Rip Out What's Left of My Hair :)? (Edit: Solved!)

         Fedora 39
     KDE DE
     Current Login: "User" with Password "1"

This allows me to connect to the share; however, it is "empty" on both the local and the remote machines.

I've followed at least 5-6 guides all w/ completely different instructions and would love somebody w/ experience on this to point to my fuck up and what I'm very clearly missing.

sudo nano /etc/samba/smb.conf

        [global]

    [share]

       path = /mnt/2666EE3966EE097F/
       writeable = yes
       browseable = yes
       public = yes
       create mask = 0777
       public = yes
       guest ok = yes

sudo nano /etc/fstab

        /dev/disk/by-uuid/D02A6F152A6EF7BC /mnt/D02A6F152A6EF7BC auto nosuid,nodev,nofail,x-gvfs-show 0 0
    //192.168.0.30/share /mnt/2666EE3966EE097F cifs username=user,password=1 0 0

Dolphin also has this tab below (local machine w/ the mounted drive), but any password input doesn't do anything (the explorer flashes w/ no info about what the "Set Password" button did)

11 comments

I don't fully understand this setup. Did I misunderstand something?
You have a Fedora PC with an NTFS partition mounted to /run/media/user/share. The Fedora computer shares a directory /mnt/2666EE3966EE097F over Samba.
Fedora and another computer connect to /mnt/2666EE3966EE097F/ over Samba, but they show no content.
Did you perhaps forget to remount your NTFS partition to /mnt/2666EE3966EE097F/? Otherwise I don't see a way to access the content with your current configuration.
- The configuration change in /etc/fstab is what stopped it being mounted correctly on boot. But is what was recommended for the SMB share.
  I'm not sure I understand why it changes from MNT to Media based on the GUI's changes to the drive. If I have it auto-mount, it adds a 2nd listing like this:
  
  //192.168.0.30/share /mnt/2666EE3966EE097F auto cifs username=user,password=1 0 0 /dev/disk/by-uuid/2666EE3966EE097F /mnt/2666EE3966EE097F auto nosuid,nodev,nofail,x-gvfs-show 0 0
  Do I combine them in some fashion lol?
  Did I misunderstand something?
  No, I'm stupid :'(
  
  You need to put the bommon line /dev/disk/by-uuid/2666EE3966EE097F /mnt/2666EE3966EE097F auto nosuid,nodev,nofail,x-gvfs-show 0 0 onto the computer with the NTFS partition.
  The top line //192.168.0.30/share /mnt/2666EE3966EE097F auto cifs username=user,password=1 0 0 is for mounting the Samba share on another device.
I was literally fighting with this these last 4 hours, and here's my conclusion:
What a goddamn mess Samba is. How in the world is it so hard to make this thing work?
I eventually realised that for my usecase minidlna would work, at least for a while, and it was amazing how simple it was.
This is all I can say about the subject. I am surprised there are no simple ways to setup Samba folders such as a GUI that asks you "what ya wanna share? Oh, okay, you want people to write things on it? Cool! It's working now. Don't forget to check these ports on your firewall, bye!"
- Everything has been immeasurably easier on Linux. But holy fuck the Windows' Right Click -> Share is eons better than this :(
Did you read the docs about SELinux? Maybe this will help you
Firewall and SELinux can mess up FTP and SMB
- So if I had to guess morethanevil, this is the line that ended up fixing it! Really appreciate it, because everything else seemed to fall into place after this:
  
  setsebool -P samba_export_all_ro=1 samba_export_all_rw=1
  I really appreciate all of your help Certainly_No_Brit! I had it set up in such a ridiculous way, but your assistance really helped me grasp why each guide was so wildly different (creation vs. adding a remote SMB on linux). After it worked, I could look up the network drive in Dolphin/Windows File Explorer in a very normal manner and can access all of the files :)!
  Maybe your issue was with your firewall or permission in some regard unknowing8343? I still really prefer Windows' method (gag), but this was certainly very doable w/ the SELinux tweaks in the link above.
  
  I had the same problem with Fedora, as I started to use it as my server OS for my homelab. SELinux can be tricky, expect the same if you ever run FTP. Webservers are different too. Bookmark the Fedora dics, they are very useful ☺️
  You can disable SELinux completly if you struggle too much. Firewalld is another part to learn, but you can switch easily to ufw if you want. Uninstall firewalld and install ufw

11 comments