[SOLVED] Cannot acces file structure with samba

[stevestar10]

Hey,

Samba worked just fine for me but after I did an apt-get update and upgrade it doesnt work anymore. My Pi is visible in networks on my macbook, it displays the home directory with HTPCguides folder and some log files. The shared folder that I set-up in the smb.conf file is listed on my mac, but it's empty..

This is the shared folder part in the smb.conf file:

Code:

[Raspberry Pi]
comment=Raspberry Pi System Access
path=/
browseable=Yes
writeable=Yes
only guest=no
create mask=0777
directory mask=0777
public=no
read only=no

I've got the workgroup set to WORKGROUP. And I used sudo smbpasswd -a pi (and for root) to set new passwords. I don't know whats causing this, maybe a permissions error of some kind?

[Mike]

Samba can be funky, try rebooting the Pi and the Mac.

[stevestar10]

I already did that a lot of times, its been going on for a few weeks now but I didnt have the chance to have a look at it. I saw by the way that there is a path in the config file to a folder that has to do with the profiles. But that folder doesnt exist on my pi.. I think it is /home/samba/something.... but the samba folder doesnt exist

[Mike]

With the path you have assigned it looks like you are trying to give samba access to the entire root file system! I have never tried this but it wouldn't surprise me if you weren't allowed to for security reasons.

You can try setting public to yes instead of no.

Samba is usually used for sharing a certain folder to easily copy files, if you need full file system access I'd recommend using sftp over ssh (this is enabled by default). I use Filezilla and put the Pi IP address in, user and password and use port 22 (SSH port) and copy things that way. For larger files where speed matters I use FTP (which is always faster than samba according to benchmarks) on Pi devices.

[stevestar10]

I changed the path to a sub folder and now it works :p
Thanks, Ill probably start using ftp when I run into errors next time

[Mike]

hehe, another problem solved @stevestar10

[jonesPhedra]

Double-check the rest of your smb.conf file to ensure mapquest that there are no typos or errors in the configuration that could be causing the problem.

[jonescelinaa]

Please double check the permissions of the shared folder in smb.conf, make sure the path is correct, and Mapquest Directions try restarting the Samba service.