SAMBA logins and write not possible

Hello,

Thanks for reading.
My install: I installed OMV on top of Debian Jessie.
My main user account cannot login to SAMBA. (Oh, why are there two of the same users anyway)
Another user on the system can login to SAMBA but cannot write to shared folders on which I already gave that user write permissions.

I have followed the video posted by ryecoaaron (thanks) at but still no luck. I have rebooted the machine after making changes, no luck.

When I issue: service samba status
I get: samba service
Loaded: masked (/dev/null)
Active: inactive (dead)

I really don't know what else to do. I have turned the server off and then back on, no luck.
I have not made any fancy changes, aside enabling shares, etc. But as we can see the problems are well past that;
-why can't me, as admin, and main user, can't longin via samba
-why can't a user that can longin can't write

Thanks a lot in advance.

Zitat von caseyj

Its about the ownership right of the files not its access right... Try to look in "ACL"

As is widely advised here, I'm not using ACLs I'm using "Privileges."

Zitat von ryecoaaron

It must be a setting or permission.

What is the output of:

cat /etc/samba/smb.conf

#======================= Global Settings =======================
[global]
workgroup = WORKGROUP
server string = %h server
dns proxy = no
log level = 0
syslog = 0
log file = /var/log/samba/log.%m
max log size = 1000
syslog only = yes
panic action = /usr/share/samba/panic-action %d
encrypt passwords = truepass
db backend = tdbsam
obey pam restrictions = no
unix password sync = no
passwd program = /usr/bin/passwd %u
passwd chat = *Enter\snew\s*\s
password:* %n\n *Retype\snew\s*\s
password:* %n\n *password\supdated\ssuccessfully* .pam
password change = yes
socket options = TCP_NODELAY IPTOS_LOWDELAY
guest account = nobody
load printers = no
disable spoolss = yes
printing = bsd
printcap name = /dev/null
unix extensions = yes
wide links = no
create mask = 0777
directory mask = 0777
use sendfile = yes
aio read size = 16384
aio write size = 16384
null passwords = no
local master = yes
time server = no
wins support = no
#======================= Share Definitions =======================
[doc]
path = /media/03e660c6-9f2c-4c46-a34f-b70a7d0e5761/doc
guest ok = no
read only = no
browseable = yes
inherit acls = yes
inherit permissions = no
ea support = no
store dos attributes = no
vfs objects =
printable = no
create mask = 0664
force create mode = 0664
directory mask = 0775
force directory mode = 0775
hide special files = yes
follow symlinks = yes
hide dot files = yes
valid users = "auto","ring","sum","win",@"auto"
invalid users =
read list = "ring","sum"
write list = "aut0","win",@"auto"
[doc1]
path = /media/a05b0722-3488-498d-8986-1e851c696b3d/doc1
guest ok = no
read only = no
browseable = yes
inherit acls = yes
inherit permissions = no
ea support = no
store dos attributes = no
vfs objects =
printable = no
create mask = 0664
force create mode = 0664
directory mask = 0775
force directory mode = 0775
hide special files = yes
follow symlinks = yes
hide dot files = yes
valid users = "auto","ring","sum","win",@"auto"
invalid users =
read list = "ring","sum"
write list = "auto","win",@"auto"

Zitat von ryecoaaron

What are the usernames of your admin and main users?

admin user: "auto",

Other users: "ring","sum","win",

And I don't know why we have two "auto" accounts, the other shows up as (@"auto")

When I installed the system, I created auto during installation of Jessie

And then added a user with the same name, auto, when I created users on OMV.

Is that why we have two? Should there not be only one showing up. Two shows up everywhere, the privileges, etc.
Thanks a lot!

Zitat von ryecoaaron

This is a group. if you installed jessie, it creates a group with the same name as the user.
ring and sum are listed as read only users. You are still doing something wrong in the configuration.

Thanks. I want "ring" and "sum" to be read-only users.
But if you recall my original questions:
-why can't me, as admin, and main user, can't longin via samba
-why can't a user that can longin can't write
The configuration file that is there now is the same that I've posted here. So, I'm not doing anything else "wrong"
If there's another part of OMV configuration's that you'd like I look at, I'd be pleased.
Many thanks.

Zitat von ryecoaaron

Is there existing data on the drives?

yes