similar to: getent & winbindd on FreeBSD 5.4

Hello, During a re-start of Samba I got the following error: [2006/03/22 12:36:14, 0] passdb/pdb_tdb.c:tdbsam_tdbopen(196) Unable to open/create TDB passwd [2006/03/22 12:36:14, 0] passdb/pdb_tdb.c:tdbsam_getsampwrid(490) pdb_getsampwrid: Unable to open TDB rid database! The result is a new password file. The second problem is that after creation of the users and a new join of the

Hi everyone. I have a problem when using samba together with usrmgr. When adding a global group I get an error message. The group is still created. You can't see before you refresh but that's a minor detail. In the logfiles May 10 17:47:27 lanchester smbd[28424]: [2005/05/10 17:47:27, 0] passdb/pdb_tdb.c:tdbsam_tdbopen(195) May 10 17:47:27 lanchester smbd[28424]: Unable to

It's exactly the same. Except that I use tdbsam instead of ldap and the error message therefore also is different in the log file. But the example and result is the same. Do you have any idea of workaround or fix? Cheers, Joel -----Ursprungligt meddelande----- Fr?n: Doug Campbell [mailto:doug@bpta.net] Skickat: den 11 maj 2005 10:49 Till: Joel Larsson, PF, Posten; samba@lists.samba.org

Hello, For some time now have been trying to connect a Samba-3.0.14a-0.4 server running on SuSE Ent 9 linux server to our Exchange 2003 (running on Server 2003 Std w/ SP1) server which is also the AD server for our domain. I can connect to the shares using the AD as the authentication source, so the basic functionality is there but some command output does not show in the way i expect

Hello, i have migrate a Samba (3.0.20b-3.19-1616-SUSE) to debian 9 (4.5.16-Debian). On the old suse users are created with smbpasswd -an foo On Windows (10) users have a User account with also empthy passwords. No AD or NT4-Domain (round about 10 Users) Then I try to connect to the share smbclient -NL \\192.xxx.xxx.xxx work. Connect from Windows to share with no password dosed work. Set a

Hello world, I have a very strange update problem: this night I upgraded from 3.0.5 to 3.0.6 (debian unstable) and the system broke completely with very strange errors (I did not change anything to smb.conf) - win98 users can log in, copy and everything - xp users can log in, they see the shares but they cannot access the files (read error in xp). I have tested it with Xp-Prof SP1 und SP2

Using samba 3.5.12 on aix 6.1 when I set "server signing = mandatory" nothing can connect to my server. Included the smb.conf followed by errors showing up in the level 10 debug output. Thanks, >cat /usr/local/samba/lib/smb.conf [global] workgroup = somename netbios name = someserver server string = somename Samba Server %v security = user

Hi, i was the one who had problems with the start_tls function. I applied the patch yesterday. But now the compiling doesn't work anymore. This is what happens : --------snipp---------- [Lots of compiling output cut away] Linking bin/smbd passdb/pdb_ldap.o: In function `pdb_setsampwent': passdb/pdb_ldap.o(.text+0x1730): multiple definition of `pdb_setsampwent'

Hi, I have Samba 3.0.14a-3sarge4 package installed. It is actually working on other Debian machine with the same configuration, but in this machine, after starting samba I get: [2007/05/22 11:47:56, 0] passdb/pdb_tdb.c:tdbsam_tdbopen(208) TDBSAM version unknown: 3 [2007/05/22 11:47:56, 0] passdb/pdb_tdb.c:tdbsam_getsampwrid(488) pdb_getsampwrid: Unable to open TDB rid database! I

Hello all, This is my first time on the list. I just dl'ed thet latest samba, 2.0.6 and during my compile with linux 5.2 I get: smbd/files.o: in function `file_new`: smbd/files.o(.text+0xb8): undefined reference to `__bzero` .... Has anyone seen something like this before? any hints would be greatly appriciated. If I am on the wrong list please inform me where I can get the answeres to

This is more of a pam question then a samba question, but I thought I'd start here and see if I can get an answer. I've gotten pam_winbind.so working with gdm (on RHAT 8) using the following /etc/pam.d/gdm file. I've put + signs to show the lines I added I added to the stock RHAT 8 gdm pam def.: #%PAM-1.0 + auth sufficient /lib/security/pam_winbind.so + auth

Hi, We have a Windows 2000 domain controller using active directory. I would like to authenticate users against it, but it's not working. I've been trying for 2 weeks without much luck. Any (and I do mean ANY) help would be greatly appreciated. My linux box: Linux cptapp01 2.6.10-5-386 #1 Tue Apr 5 12:12:40 UTC 2005 i686 GNU/Linux (Ubuntu) My samba: Version 3.0.20 My smb.conf: [global]

I've installed SAMBA, Winbind etc and everything is working great for users to login with GDM using DOMAIN+username Although this is working, now I can no longer login as a generic Linux user (ex. root). The following is my GDM file from /etc/pam.d/gdm I wonder if someone might have a suggestion as to what it's missing to allow Linux users to login? #%PAM-1.0 auth required

Hi all, I have been trying to setup authentication of users on a Linux server against Windows server 2003 using winbind. I am at the point where an su - ADUSERNAME works, but sshing as that user still doesn't work. When I try to ssh as an AD user as follows: ssh -l "RILINUX+testuser" server.domain.com I get the following output in /var/log/messages: server pam_winbind[5906]:

Hi, I was using Samba 3.0.9 on Fedora Core 2 and decided to upgrade to 3.0.10. So I upgrade to Core 3 and installed Samba 3.0.10 and thought I could just copy my settings over to the new build and everything would run smoothly. I thought wrong. Everything seems fine until I enable Obey Pam Restrictions. If enabled I get a login error from XP stating: " Windows cannot locate your

Hi all, I was wondering if someone could lend a little assistance. I recently setup SAMBA/Winbind to allow users to login to a Redhat 8 box using their Windows NT Domain credentials. All is working well in that regard. The issue I am having is getting regular UNIX based users to be able to login. The following is my PAM configuration. For example, if I try to login as root, it does not work.

Hi, I'm preparing to do a migration, but I'm having some doubts. I installed 3.0.14a (from/for Suse) and I successfully joined the domain. When I did a "net rpc vampire -S ..." there were some things that worry me : ... Creating account: Administrator [2005/05/17 12:35:31, 0] passdb/pdb_tdb.c:tdbsam_tdbopen(195) Unable to open/create TDB passwd [2005/05/17 12:35:31, 0]

hi, my smb.conf looks like this: ... security = share update encrypted = yes encrypt passwords = no ... /etc/pam.d/samba: #%PAM-1.0 auth required pam_nologin.so auth required pam_stack.so service=system-auth account required pam_stack.so service=system-auth session required

Hello, I am have some interesting problems with the pam_winbind portion of samba 3.1. wbinfo -u and getent passwd works but when I login I get the following messages in /var/log/messages. Jan 5 11:09:36 hermes pam_winbind[9014]: write to socket failed! Jan 5 11:09:36 hermes pam_winbind[9014]: internal module error (retval = 3, user = `CSQ+shane' Jan 5 11:09:36 hermes PAM_pwdb[9014]: check

I'm about ready to smash my head through a wall...I could use a few answers. 1. When using security = ads, and completing net ads join, it was my understanding that samba authenticated username/pword against ads, and local posix accounts were nolonger needed, is this true? 2. If yes, I have not been able to get it to work. If I have a posix user account with the same name as one in