[SOLVED]Samba shares accessible but not visible

MisterAnderson · 2013-05-01 09:12:38

Hey guys, I'm guessing the update to samba 4 has broken my samba partially, my samba shares seem to no longer be visible, but I can still access them. Probably an out of date config file, any chance of help with it?

These are super simple shares for my family home, no passwords, simple direct guest access. Windows computers are the main clients, other than my own linux ones. The workgroup name is correct (oh yeah, I'm that lazy).

[global]

   workgroup = WORKGROUP

   server string = Media Server

   security = share

   load printers = yes


   log file = /var/log/samba/%m.log

   max log size = 50


interfaces = 192.168.2.194/24


   dns proxy = no 


[printers]
   path = /var/spool/samba
   browseable = yes
   public = yes
   guest ok = yes
   writable = no
   printable = yes
   create mode = 0700
   write list = @adm root greg

[media]
   path = /shares
   public = yes
   only guest = yes
   writable = yes

[storage]
   path = /storage
   public = yes
   only guest = yes
   writable = yes

[story]
   path = /story
   public = yes
   only guest = yes
   writable = yes

[store]
   path = /store
   public = yes
   only guest = yes
   writable = yes

Last edited by MisterAnderson (2013-05-01 14:41:42)

MisterAnderson · 2013-05-01 14:24:55

Well, without replies I got bored, so I tried out getting SWAT working, and it says nmbd isn't running, so that's the problem. Telling it to start via SWAT works but I want it working off boot, so I'll look at that.

WonderWoofy · 2013-05-01 14:25:34

nmdb has a service file.

I commend your ability/drive to solve this on your own though. Good work!

Last edited by WonderWoofy (2013-05-01 14:26:20)

MisterAnderson · 2013-05-01 14:41:26

Got it. For some reason there was a /etc/systemd/system/nmdb.service file, which was very different from the one in /usr. I found it by running systemd-delta. After deleting that file, it now starts on boot correctly.

I also had to change "security = share" in the config file to:

security = user
map to guest = Bad User

All my problems are now cleared up. Maybe I'll try to work out why all help links in SWAT seem to 404. The only hint I've found is to install smb-doc from ubuntu wiki but we don't have it in the repositories or AUR. Oh well.

Last edited by MisterAnderson (2013-05-01 14:43:47)

WonderWoofy · 2013-05-01 14:50:34

I have never tried swat, nor do I feel as though it is entrely necessary. Editing a config file, and using either an example or a man page, doesn't seem all that scary to me. But then again, I am not frightened by breaking my computer either. But still, I fail to understand how the greater computer using public can be so afraid of editing a plain text config (especially one that is in ini format). I mean what really is the difference between a gui checkbox and "some-option = (0|1)"?

BTW, I thnk that 99% of the worlds workgroup names are WORKGROUP. You're just as lazy as the rest of us. I don't know if you just updated to samba 4 like today, but if you did, you may need to re-add all your users through pdbedit.

MisterAnderson · 2013-05-01 15:22:16

WonderWoofy wrote:

I have never tried swat, nor do I feel as though it is entrely necessary. Editing a config file, and using either an example or a man page, doesn't seem all that scary to me. But then again, I am not frightened by breaking my computer either. But still, I fail to understand how the greater computer using public can be so afraid of editing a plain text config (especially one that is in ini format). I mean what really is the difference between a gui checkbox and "some-option = (0|1)"?
BTW, I thnk that 99% of the worlds workgroup names are WORKGROUP. You're just as lazy as the rest of us. I don't know if you just updated to samba 4 like today, but if you did, you may need to re-add all your users through pdbedit.

I only tried it because I thought it might rewrite my config file and make it work, but since I discovered the problem myself I'm not too worried. Really, the problem with using samba for filesharing is that it can do so much more that the simplest implimentations (such as my passwordless shares) are hard to find sample configuration files for. I added my working config to the Samba Tips/Tricks wiki page for the sake of anyone who might want it (I left out some optimisations I'm trialling). Some people just don't want to deal with password protected shares.

Also, I've no clue what pdbedit is so I'm guessing I don't need it.

Last edited by MisterAnderson (2013-05-01 15:22:44)

Arch Linux

#1 2013-05-01 09:12:38

[SOLVED]Samba shares accessible but not visible

#2 2013-05-01 14:24:55

Re: [SOLVED]Samba shares accessible but not visible

#3 2013-05-01 14:25:34

Re: [SOLVED]Samba shares accessible but not visible

#4 2013-05-01 14:41:26

Re: [SOLVED]Samba shares accessible but not visible

#5 2013-05-01 14:50:34

Re: [SOLVED]Samba shares accessible but not visible

#6 2013-05-01 15:22:16

Re: [SOLVED]Samba shares accessible but not visible

Board footer