I downloaded samba V2.2.1, compiled it and started it up. Looks fine,
except I can not
get a user authenticated to the QNX 6.1 password files. Anybody figured
out what is
needed in the smb.conf file to use the passwd/shadow files for samba
access or are you
using the smbpasswd to have seperate password files.
We’re running Samba 2.0.7, and have disabled encrypted passwords on the
Windows boxes using the XX_PlainPassword.reg files in the docs directory.
Marty Doane
“Rich Hemmenway” <rhemmenw@ocdus.jnj.com> wrote in message
news:3BAF7577.E5516815@ocdus.jnj.com…
I downloaded samba V2.2.1, compiled it and started it up. Looks fine,
except I can not
get a user authenticated to the QNX 6.1 password files. Anybody figured
out what is
needed in the smb.conf file to use the passwd/shadow files for samba
access or are you
using the smbpasswd to have seperate password files.
Rich Hemmenway <rhemmenw@ocdus.jnj.com> wrote:
I downloaded samba V2.2.1, compiled it and started it up. Looks fine,
except I can not
get a user authenticated to the QNX 6.1 password files. Anybody figured
out what is
needed in the smb.conf file to use the passwd/shadow files for samba
access or are you
using the smbpasswd to have seperate password files.
Maybe if you provide more context you’ll get more to-the-point tips. Does
SWAT authenticate properly? (You need to login to SWAT as “root”) If SWAT
works, you have an easy means of creating new user accounts.
BTW, there’s lots of documentation, including on how to setup
authentication properly. See your $srcdir/docs directory. (And if SWAT
works, you can also browse the online help.)
good luck,
rick
Rich Hemmenway a écrit :
I downloaded samba V2.2.1, compiled it and started it up. Looks fine,
except I can not
get a user authenticated to the QNX 6.1 password files. Anybody figured
out what is
needed in the smb.conf file to use the passwd/shadow files for samba
access or are you
using the smbpasswd to have seperate password files.
Look at the Marty Doane article but I’m no more so sure about that as I did
some tests previously with 2.0.7 without any certitude on how it’s managed.
I’m running now 2.2.1, I checked this morning on my NT4 SP5, I haven’t any
EnablePlainText in my registry. Encrypted password is set to No on Samba.
Security is on ‘SERVER’.
My qrtp server is declared on the same domain, I’m using the same
login/passwd on both NT and QRTP.
Everything works fine!
Take care that when you make changes on your smb.conf it may take several
minutes to affect smbd. For your tests, slay and restart smbd, you won’t
have any doubt.
I didn’t make lot of tests on 2.2.1 but I wonder if it look at smb.conf
periodically. Click on ‘Commit Changes’ in swat (Web administrator) doesn’t
change anything, smb.conf yes, but smbd doesn’t take care of it. it was ok
on 2.0.7.
I joined my smb.conf.
Regards,
Alain.
Thanks for all the suggestions.
It looks like my problem was that I don’t have access to a password server, so
I
had to configure with a /usr/local/samba/privage/smbpasswd file. The smbpasswd
program needed some fixes to work with Qnx 6.1.
What I was really trying to do is set it up like my old Qnx 4 samba server that
just used the Qnx 4 /etc/passwd file, to avoid the seperate passwords, but I
can’t
seem to find any way to do that. The changes I needed in my smb.conf file are:
lanman auth = Yes
encrypt passwords = Yes
thanks
rich
Alain Bonnefoy wrote:
Rich Hemmenway a écrit :
I downloaded samba V2.2.1, compiled it and started it up. Looks fine,
except I can not
get a user authenticated to the QNX 6.1 password files. Anybody figured
out what is
needed in the smb.conf file to use the passwd/shadow files for samba
access or are you
using the smbpasswd to have seperate password files.Look at the Marty Doane article but I’m no more so sure about that as I did
some tests previously with 2.0.7 without any certitude on how it’s managed.
I’m running now 2.2.1, I checked this morning on my NT4 SP5, I haven’t any
EnablePlainText in my registry. Encrypted password is set to No on Samba.
Security is on ‘SERVER’.
My qrtp server is declared on the same domain, I’m using the same
login/passwd on both NT and QRTP.
Everything works fine!Take care that when you make changes on your smb.conf it may take several
minutes to affect smbd. For your tests, slay and restart smbd, you won’t
have any doubt.I didn’t make lot of tests on 2.2.1 but I wonder if it look at smb.conf
periodically. Click on ‘Commit Changes’ in swat (Web administrator) doesn’t
change anything, smb.conf yes, but smbd doesn’t take care of it. it was ok
on 2.0.7.I joined my smb.conf.
Regards,
Alain.
Samba config file created using SWAT
from val_22055 (172.20.22.55)
Date: 2001/09/25 07:50:34
Global parameters
[global]
workgroup = SYSTEME
server string = QRTP Samba Server
security = SERVER
password server = serveur_systeme
log file = /var/log/samba/log.%m
max log size = 50
socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
dns proxy = No
lock dir = /var/lock/samba/[root]
comment = root directory
path = /
valid users = root a.bonnefoy gilles.coral
read only = No[homes]
comment = Home Directory
read only = No[printers]
comment = All Printers
path = /var/spool/samba
printable = Yes
browseable = No[downloads]
comment = QRTP downloads
path = /usr/local/downloads
read only = No
guest ok = Yes[usr_local]
comment = server’s usr/local directory
path = /usr/local
read only = No[projects]
comment = projects package repository
path = /usr/local/developpement/projects
admin users = a.bonnefoy
read only = No
Rich…
I have the same problem that you had. I wonder, does Samba works for
you now? If so, I wonder if you, at your convenience, could be more
specific with regard to the changes that you made between your original
post and now?
I appreciate it. Thanks…
Bests…
Miguel.
Rich Hemmenway wrote:
Thanks for all the suggestions.
It looks like my problem was that I don’t have access to a password server, so
I
had to configure with a /usr/local/samba/privage/smbpasswd file. The smbpasswd
program needed some fixes to work with Qnx 6.1.What I was really trying to do is set it up like my old Qnx 4 samba server that
just used the Qnx 4 /etc/passwd file, to avoid the seperate passwords, but I
can’t
seem to find any way to do that. The changes I needed in my smb.conf file are:lanman auth = Yes
encrypt passwords = Yesthanks
rich
Alain Bonnefoy wrote:
Rich Hemmenway a écrit :
I downloaded samba V2.2.1, compiled it and started it up. Looks fine,
except I can not
get a user authenticated to the QNX 6.1 password files. Anybody figured
out what is
needed in the smb.conf file to use the passwd/shadow files for samba
access or are you
using the smbpasswd to have seperate password files.Look at the Marty Doane article but I’m no more so sure about that as I did
some tests previously with 2.0.7 without any certitude on how it’s managed.
I’m running now 2.2.1, I checked this morning on my NT4 SP5, I haven’t any
EnablePlainText in my registry. Encrypted password is set to No on Samba.
Security is on ‘SERVER’.
My qrtp server is declared on the same domain, I’m using the same
login/passwd on both NT and QRTP.
Everything works fine!Take care that when you make changes on your smb.conf it may take several
minutes to affect smbd. For your tests, slay and restart smbd, you won’t
have any doubt.I didn’t make lot of tests on 2.2.1 but I wonder if it look at smb.conf
periodically. Click on ‘Commit Changes’ in swat (Web administrator) doesn’t
change anything, smb.conf yes, but smbd doesn’t take care of it. it was ok
on 2.0.7.I joined my smb.conf.
Regards,
Alain.
Samba config file created using SWAT
from val_22055 (172.20.22.55)
Date: 2001/09/25 07:50:34
Global parameters
[global]
workgroup = SYSTEME
server string = QRTP Samba Server
security = SERVER
password server = serveur_systeme
log file = /var/log/samba/log.%m
max log size = 50
socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
dns proxy = No
lock dir = /var/lock/samba/[root]
comment = root directory
path = /
valid users = root a.bonnefoy gilles.coral
read only = No[homes]
comment = Home Directory
read only = No[printers]
comment = All Printers
path = /var/spool/samba
printable = Yes
browseable = No[downloads]
comment = QRTP downloads
path = /usr/local/downloads
read only = No
guest ok = Yes[usr_local]
comment = server’s usr/local directory
path = /usr/local
read only = No[projects]
comment = projects package repository
path = /usr/local/developpement/projects
admin users = a.bonnefoy
read only = No
–
my opinions are mine, only mine, solely mine, and they are not related
in any possible way to the institution(s) in which I study and work.
Miguel Simon
Research Engineer
School of Aerospace and Mechanical Engineering
University of Oklahoma
http://www.amerobotics.ou.edu/
http://www.saic.com