Results 1 to 10 of 11
I am having a problem with the users I create on Suse 10.0 not working on Samba. It is my understanding that simply creating users in the YaST2 control center ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
- 01-12-2006 #1Just Joined!
- Join Date
- Jan 2006
- Posts
- 13
Samba on SUSE 10.0
I am having a problem with the users I create on Suse 10.0 not working on Samba. It is my understanding that simply creating users in the YaST2 control center creates those users as samba users as well. So why don't any of the users I make work except for the root user? am I missing something? am I completely wrong about how this works?
- 01-12-2006 #2
did you create samba passwords for those users? i.e. smbpasswd -a user_name
Life is complex, it has a real part and an imaginary part.
- 01-13-2006 #3Just Joined!
- Join Date
- Jan 2006
- Posts
- 13
I ran that command successfully, then tried to login with no luck.
- 01-13-2006 #4
what does your /etc/samba/smb.conf file look like?
Life is complex, it has a real part and an imaginary part.
- 01-16-2006 #5Just Joined!
- Join Date
- Jan 2006
- Posts
- 13
This is my smb.conf file. My understanding is that in Suse 10.0 any local users that you create are supposed exist as samba uses also. If this is not so then I need to figure out a way to setup a user friendly administration interface of some kind. I can handle CLI administration, but my boss will not find it acceptable.
# Samba config file created using SWAT
# from 127.0.0.1 (127.0.0.1)
# Date: 2006/01/12 14:23:34
[global]
workgroup = SUSE-TEST
map to guest = Bad User
printcap name = cups
add machine script = /usr/sbin/useradd -c Machine -d /var/lib/nobody -s /bin/false %m$
logon path = \\%L\profiles\.msprofile
logon drive = P:
logon home = \\%L\%U\.9xprofile
domain logons = Yes
os level = 65
preferred master = Yes
domain master = Yes
cups options = raw
include = /etc/samba/dhcp.conf
[profiles]
comment = Network Profiles Service
path = %H
read only = No
create mask = 0600
directory mask = 0700
store dos attributes = Yes
[users]
comment = All users
path = /home
read only = No
inherit acls = Yes
veto files = /aquota.user/groups/shares/
[groups]
comment = All groups
path = /home/groups
read only = No
inherit acls = Yes
[printers]
comment = All Printers
path = /var/tmp
create mask = 0600
printable = Yes
browseable = No
[print$]
comment = Printer Drivers
path = /var/lib/samba/drivers
write list = @ntadmin, root
force group = ntadmin
create mask = 0664
directory mask = 0775
[netlogon]
comment = Network Logon Service
path = /var/lib/samba/netlogon
write list = root
[public]
comment = publich share
path = /samba shares/public/
read only = No
inherit acls = Yes
[accounting]
comment = accounting department folder
path = /samba shares/accounting/
read only = No
inherit acls = Yes
[communications]
comment = communications department share
path = /samba shares/communications/
read only = No
inherit acls = Yes
[operations]
comment = operations department share
path = /samba shares/operations/
read only = No
inherit acls = Yes
[tech]
comment = IT department share
path = /samba shares/tech/
read only = No
inherit acls = Yes
- 01-16-2006 #6Just Joined!
- Join Date
- Jan 2006
- Posts
- 13
I am wondering if perhaps what I need to do is add the following to my smb.conf file
# sync smb passwords woth linux passwords
passwd program = /usr/bin/passwd %u
passwd chat = *Enter\snew\sUNIX\spassword:* %n\n *Retype\snew\sUNIX\spassword:* %n\n .
passwd chat debug = yes
unix password sync = yes
I found this on a tutorial for setting up Ubuntu with Samba
- 01-16-2006 #7Linux Enthusiast
- Join Date
- Dec 2004
- Posts
- 637
What type of authentication are you using? The ideal case for your scenario is User authentication, instead of Share. Check your authentication scheme. This is what troubled me in the past.
- 01-16-2006 #8Just Joined!
- Join Date
- Jan 2006
- Posts
- 13
My security is set to "USER" I assume that this controls the authentication method, there is also the option of share, server, domain, and ADS. I understand share, I'm guessing that domain references a different server for authentication and that ADS refers to active directory services. As for "SERVER" I have no idea what that means, LDAP?
I am getting all of this information from SWAT by the way, perhaps there is something I can do from inside SWAT to reference my local users as valid samba users?
I am willing to change to any other free distro as well as try add-on tools. I am currently trying to get Idealx up and running.
- 01-16-2006 #9
try adding the following to the globals section of smb.conf:
make sure that the /var/lib/samba/private/smbpasswd file exists before setting this option.encrypt passwords = yes
smb passwd file = /var/lib/samba/private/smbpasswdLife is complex, it has a real part and an imaginary part.
- 01-17-2006 #10Just Joined!
- Join Date
- Jan 2006
- Posts
- 13
I have added the global variables that you suggested. What exactly should this for my problem?


Reply With Quote
