After setting up the Astroberry image over RPi 4, I was able to connect successfully to the web interface through astroberry.local. I can access the RPi also through the SSH without issue, and I can ping with no issues. Everything is working fine except when I try to access the Astroberry samba share from my win10 laptop.
I checked samba service and it is sunning. I checked its configuration and it was properly configured for sharing. When I try to access the shares in RPi from windows explorer using \\astroberry.local or \\<IP> i get "windows can't find \\astroberry.local or \\<ip>" respectively.
Any idea what could be going wrong?
Thank you
Mohamed
Warning: Spoiler!
astroberry@astroberry:~ $ testparm
rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384)
Load smb config files from /etc/samba/smb.conf
rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384)
Processing section "[homes]"
Processing section "[printers]"
Processing section "[print$]"
Processing section "[astroberry]"
Loaded services file OK.
Server role: ROLE_STANDALONE
Press enter to see a dump of your service definitions
# Global parameters
[global]
log file = /var/log/samba/log.%m
logging = file
map to guest = Bad User
max log size = 1000
obey pam restrictions = Yes
pam password change = Yes
panic action = /usr/share/samba/panic-action %d
passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* .
passwd program = /usr/bin/passwd %u
server role = standalone server
unix password sync = Yes
usershare allow guests = Yes
idmap config * : backend = tdb
[homes]
browseable = No
comment = Home Directories
create mask = 0700
directory mask = 0700
valid users = %S
[printers]
browseable = No
comment = All Printers
create mask = 0700
path = /var/spool/samba
printable = Yes
Your share is called astroberry so try \\astroberry.local\astroberry and see if you can connect to that. Otherwise, install the smbclient software on your astroberry and try
smbclient -L //astroberry.local
to see which shares are available. You may need to add parameters for the username and password (sorry, I am typing this from the top of my head and it has been years since I looked into samba).
Apart from that, you set browsable to No in the homes section and then try to add a share for the astroberry home dir. Perhaps they are in conflict? I'd suggest to take out the astroberry section and set browsable to yes in the homes section. I suppose that astroberry is the only (non-root) user so that should not be a safety issue.
Thank you for your response. I've been investigating this issue, and I believe it is a win10 issue and not setup on the Astroberry side. MS disabled many protocols including SAMBA by default. Although I was not successful using win10 to get to my files, as a workaround, I used FileZilla and logged in over SSH, and it worked.