Bob Fillmore
2001-Apr-29 22:03 UTC
2.2.0 bug? "unable to open smb password database" with security=domain
Hi, This is probably not a serious bug, but is probably affecting Samba performance. We are using Samba 2.2.0 on Solaris 2.6 with security=domain, and debug level=1. When I view the security properties of a file from an NT workstation, I see messages in the Samba logs like this: [2001/04/29 15:44:04, 0] passdb/smbpass.c:startsmbfilepwent_internal(87) startsmbfilepwent_internal: unable to open file /usr/local/samba/private/smbpa sswd. Error was No such file or directory [2001/04/29 15:44:04, 0] passdb/smbpass.c:iterate_getsmbpwuid(1243) unable to open smb password database. Why is Samba trying to access the smbpasswd file if security=domain? Thanks, Bob Fillmore
Bas
2001-Apr-30 08:12 UTC
2.2.0 bug? "unable to open smb password database" with security=domain
Hi Bob, Just a few lines coming from man smb.conf .... SECURITY = DOMAIN This mode will only work correctly if smbpasswd(8)has been used to add this machine into a Windows NT Domain. It expects the encrypted passwords parameter to be set to true. In this mode Samba will try to validate the user? name/password by passing it to a Windows NT Primary or Backup Domain Controller, in exactly the same way that a Windows NT Server would do. Note that a valid UNIX user must still exist as well as the account on the Domain Controller to allow Samba to have a valid UNIX account to map file access to. Note that from the clients point of view security = domain is the same as security = user . It only affects how the server deals with the authentication, it does not in any way affect what the client sees. Note that the name of the resource being requested is not sent to the server until after the server has successfully authenticated the client. This is why guest shares don't The rest is of this man page is installed on your system. Good Luck, Bas. ----- Original Message ----- From: Bob Fillmore <fillmore@home.com> To: <samba@samba.org> Sent: Sunday, April 29, 2001 3:03 PM Subject: 2.2.0 bug? "unable to open smb password database" with security=domain> Hi, > > This is probably not a serious bug, but is probably affecting Samba > performance. > We are using Samba 2.2.0 on Solaris 2.6 with security=domain, and debug > level=1. > When I view the security properties of a file from an NT workstation, I > see messages > in the Samba logs like this: > > [2001/04/29 15:44:04, 0] passdb/smbpass.c:startsmbfilepwent_internal(87) > > startsmbfilepwent_internal: unable to open file > /usr/local/samba/private/smbpa > sswd. Error was No such file or directory > [2001/04/29 15:44:04, 0] passdb/smbpass.c:iterate_getsmbpwuid(1243) > unable to open smb password database. > > Why is Samba trying to access the smbpasswd file if security=domain? > > Thanks, > > Bob Fillmore > > > > -- > To unsubscribe from this list go to the following URL and read the > instructions: http://lists.samba.org/mailman/listinfo/samba