Hey @Bill that is great news. I’m glad we were able to get things working for you. please let me know if you need any additional help
For everyone else following this
We grabbed a copy of the HL15 image and could make an SMB share and connect. All we did was disable the SMB management on the ZFS tab and use our filesharing tab instead.
Disabled SELinux and installed samba started the service, and added it to the firewall
After that, I was able to connect to the SMB share using the HL15 image
Based on what you posted, you may have read-only access.
To help share detail on the Log Level (within Cockpit’s Samba web ui)
Log Level:
0 LOG_ERR
1 LOG_WARNING
2 LOG_NOTICE
3 LOG_INFO
4 LOG_DEBUG
When I was using level 4, I was able to see my user account authenticate and see any subsequent events that were causing me issues.
Did you also make sure that the permissions on the folder (I am assuming from the Linux OS side) have chmod 770 ( the owner of the file and the group can read, write and execute it.)
Within Cockpit’s web ui (the left side navigation panel)…
Click on FileSharing
Next to the 45Drives logo, Click Samba.
There will be a Global section, the 3 field is a dropdown (values 5 to 0). Pick 4 or 5.
Click out of the field, then click Apply (right side of the screen within that section).
The changes should be saved and Samba will restart.
To view the specific logs for Samba, you can do the following:
Left Navigation panel - click on Services
The window should update with Services having a blue underline. In the field “filter by name or description” type smb.
smb Samba SMB Daemon will appear. Click on smb.
the Samba SMB Daemon will be displayed. Within this updated window you will see the samba log under the label “Service Logs”
Then you can attempt to use the share from Windows.
if you are still having issues, there are some other things you can do to allow us to help you:
Within a terminal window you can type
testparm -s.
This command needs to be done as root. If you are the 45Drives users (that came with the prebuilt system), then you can use
sudo testparm -s
You should get a similar output to the following:
Load smb config files from /etc/samba/smb.conf
Loaded services file OK.
Weak crypto is allowed by GnuTLS (e.g. NTLM as a compatibility fallback)
Server role: ROLE_STANDALONE
Global parameters
[global]
printcap name = cups
registry shares = Yes
security = USER
server min protocol = SMB2
server string = some string
workgroup = sampleworkgorup
idmap config * : backend = tdb
cups options = raw
[SampleFolder
comment = Sample folder for this post on the forum
path = /somelocation/directoryname
read only = No
valid users = @sampleuser sampleuser
Your output will not be identical to mine.
I would check if you have a line similar to “valid users =”.
On this thread at this reply point #20, there is a suggestion to adjust the Cockpit ZFS Manager options to not manage the Samba shares. This was part of a similar issue I had where I could not successfully authenticate to get access to the shared folder.
I am assuming you are sharing content from the root folder /tank
The public folder and the media folder.
I am assuming this is the media folder was where you trying to initially connect.
As Samba does put other defaults within the configuration (and to inform you), you currently have the users home directory and printers (and print drivers) available. The directory would be shown as Home for those users that are configured on this server.
