So I set up a share and set permissions to 777. Then I exported that share via samba and enabled guest access in the GUI. When I try to log into that share via Windows 7, it still asks me for a username/password and I have to use the user/pass combo I setup for the webui (not the one I setup for the os during install). Any ideas to eliminate the password altogether?
@storinator This seems like a client side issue. Iāve tested your steps with my Ubuntu 14.04 laptop and when I select guest access in samba export and mount the Share from my laptopās file browser, it does not prompt me for username/password. So, makes me think if this is a Windows 7 requirement.
Iāll leave you with the recommendation to do some online research. If you need to set custom parameters to the samba export you can do so in the custom configuration text area. Attached is the screenshot as an example.
Somehow Iām having the same issue. Do you have other shares with logons or is this the only SMB share? Iām wondering if my other shares are conflicting with it and will try to replicate on samba itself.
Did you try comparing using samba directly without rockstor?
If you edit the /etc/samba/smb.conf
and add this line between the two mentioned
security = user
map to guest = Bad User
passdb backend = tdbsam
Then restart samba systemctl restart smb
It will work. Just set guest and browseable options on the share setting. To write, youāll need to give nobody write access or just make it 777. I have 3 shares with no password and one (plex-data) with a password and it works well.
@suman - this may be a good default value, it basically says if there is no user assigned then donāt keep reprompting, check for guest and if ok, let them in. It is also one of the worst named options I have ever seen.
if I were adventurous enough Iād submit the code on github but it may be too much. On a side note, I am hoping to write a rockon for a DNS server that can host AD (Iāve done it manually on the Rockstor server).
Thank you! I can now confirm the suggested change does work.
After logging into the console and using nano to edit the file, it works like a charm. Tested with a Windows 10 x64 pro machine to verify the connectivity.
Ok, weāve taken a long time to fix this, but better late than never right? If you are on testing updates, please try out 3.8-14.04. We need to polish the UI side a bit more, so if you are on stable channel, please be patient for 3.8-15. Many thanks to @magicalyak for helping out on this one!
Iāll test this out this weekend if I get a chance. I think I pinpointed a problem of mine to a Realtek onboard NIC so I got an Intel to see if it helps.