similar to: Possible Winbind Bug ?!?!

Hi there I hope that you understand by English. I'm a Rooky and don't know Samba very well. I installed the newest version 3.0.10 on my SuSE Linux 7.3 machine and it works very well. I make User- and Passwort-Requests with Samba (winbind) for the Squid-Proxy. Now always work's well but I get the following error message from log.winbind: [2005/01/24 11:05:52, 4]

hi list, i recently recognized, that winbind on my fileserver (needed for allocating SID->UIDs when setting ACL's from windows box) adds ldap attributes although the SID already exists !!??!?! example i have a user "install" # install, users, eva.mpg.de dn: uid=install,ou=users,dc=eva,dc=mpg,dc=de objectClass: posixAccount objectClass: person objectClass: sambaSamAccount cn:

hi list, i searched bugzilla but couldn't find an open/fixed bug for my problem: [system] - AMD Opteron 248, 8GB - SuSE 9.1 Prof. x86_64 - Samba v3.0.11-2.1 from ftp.samba.org (ftp://ftp.samba.org/pub/samba/Binary_Packages/SuSE/3.0/x86_64/9.1/) - netatalk v2.0.2 (self compiled) [situation] we're accessing our samba fileserver (files, directories, ... ) from different platforms

hi im using precompiled samba v. 3.0.4 packages from SuSE 9.1 DVDs all services (ldapsam, winbind, ... ) are compiled in user mapping on the PDC "SERVER" (SID-RID to UID) work fine the domain member server "FILESERV" gets the local accounts via nsswitch from the ldap backend of "SERVER" (tested with getent passwd) he also gets and checks the samba users and

hi, when i do nevanfs01:/ # nmblookup NEVAN#1B i get querying NEVAN on 192.168.255.255 192.168.41.3 NEVAN<1b> 192.168.41.3 NEVAN<1b> i just wonder, why there's two times the same entry? i also get error messages from nmbd like these, which i think are related to the problem i mentioned at first: 2004-07-21 13:34:21 nmbd[3150]: [2004/07/21 13:34:09, 0]

Samba version is 3.0.10 on Gentoo linux. I am trying to use idmap_rid backend in a Windows AD environment, the Linux PC acting only as a domain member. I am using idmap_rid because I need UID/GID predictability. I can log in to console correctly, and it shows the right user and the "Domain Users" as the group. When I use default winbind TDB, I can browse the home directory from an XP

hi i'm using samba 3.0.0 Beta 3 with LDAPv3 and --with-ldapsam users (unix+samba) are authenticated against ldap (nsswitch) since Beta3 we have to use winbindd, to map UID/GID correctly to RID v.v. IDMAP's are stored in LDAP (no .tdb-file) starting winbind give's me the following error ************ winbindd ************ #~ winbindd -FS -- snip -- winbindd version 3.0.0beta1

I'm using Samba 3.0.21b on SuSE 9.3 Pro (x86) with the binary RPMs from samba.org/suse.com (3.0.21b-1.1.2-SUSE-SL9.3) on a Domain Member Server in ADS mode with winbind against W2K3 SP1 AD servers and idmap uids/gids stored in a central OpenLDAP directory. Unfortunately, winbind gives me a hard time and reproducibly dies with a PANIC on a "wbinfo -g", although I think I've

With Samba on Debian Lenny joined to a Server 2003 Native domain that has two incoming non-transitive trusts (users in my domain can authenticate to the foreign domains, but their users cannot authenticate to us) winbind is taking a very long time to authenticate or list users the first time it is used after starting. Winbind blocks for four to five minutes, and anything that touches winbind will

Tried to upgrade our Samba 2.2.8a domain controller (Solaris 8) to Samba 3.0.2a. Compiled using gcc 3.3.2, linked to libiconv-1.8, popt-1.7 and cups-1.1.20. I shut down the Samba 2.2.8a. Removed everything in var/locks. Did a "make install" to install 3.0.2a, then restarted Samba. My smb.conf is basically the same as 2.2.8a with "domain admin group" removed. When I stared

Hi all, I have installed samba on aix. I am trying to integrate with the ADS using winbind. I am able to join domain and retrieve the users and groups from the ADS. I am not able to login to the server with ADS user id and password. The winbindd.log has the following error. Please let me know what is the solution for this. ?lib/charcnv.c:convert_string_allocate(567) +

Hello @ll, I'm having the following problem on a RHEL 3 Update 3, with the latest official release packages for RHEL 3. samba-common-3.0.9-1.3E.13.2 samba-3.0.9-1.3E.13.2 When changing the ip adress in /etc/krb5.conf to use the W2003 domain controller for kerberos authentication instead of the current W2000 it becomes impossible the login to this server using ssh. The command "$getent

Greetings, Here is what I have built samba on: Solaris 9 GCC 3.2.2 samba-3.0.20pre1 openldap-2.2.24 MIT Kerberos 1.4 Samba built with: ./configure --prefix=/opt/local/samba --with-automount --with-profile --with-acl-support --with-utmp --with-winbind --with-ads --with-ldap --with-krb5=/opt/local/kerberos5 --with-pam Within a minute of starting samba + winbind I get a core dump in the samba

dear list, in the output of pdbedit -L -v heupink I'm getting these errors: convert_string_allocate: Conversion error: Illegal multibyte sequence(???p? ????????) Any ideas where to look..? Are these serieus errors..? (it looks as if the errors occur BEFORE the actual ldap connection is opened, so I guess they're not ldap related...) My samba is 3.0.14a, and system is sles9 Below find

Using samba-3.0.10-1.4E.2 as supplied by RedHat Enterprise 4. Using security=ADS mode, and using winbind and pam_winbind to authenticate. I was able to sucessfully join the domain, and can enumerate users and groups. Whenever I try to authenticate, it always fails with the status STATUS_BUFFER_OVERFLOW. -------------------pieces of Winbind Logs--------------- [2006/01/26 13:08:55, 5]

With samba 3.0.24 (Debian Etch packages) I joined a Windows 2003 ADS domain. Now wbinfo -u works fine, but wbinfo -g only says: Error looking up domain groups. smb.conf: [global] workgroup = wise realm = wise.vub.ac.be server string = %h server dns proxy = no password server = wisepc1 log file = /var/log/samba/log.%m log level = 10 max log size = 1000 syslog = 0

As of RC3 and RC4, I've noticed that winbindd's wb_getpwuid function is using the form <FQDN-domain><winbind-seperator><username>, and before, it was simply <NetBIOS-domain><winbind-seperator><username>. The net effect of what I'm seeing is that users which have a UNIX account locally on the samba box and also a domain account are being

Hi Anyone know my problems ? i don't have receive a answer or idea ;=< ================================================= I have upgraded from 3.0.14a to 3.0.20b and now when i put wbinfo -u or wbinfo -g i have a error message : [root@gw samba]# wbinfo -g Error looking up domain groups [root@gw samba]# wbinfo -u Error looking up domain users [root@gw samba]# and into the log.winbind:

I have a situation where I want to do some authentication via ntlm_auth on my DC. I've tested this on my test box (a domain member) and it works perfectly. On domain member - tor:~ # /usr/bin/ntlm_auth --username=adam --domain=BACKBONE --password=******** NT_STATUS_OK: Success (0x0) On domain controller - littleboy:~ # /usr/bin/ntlm_auth --username=adam --domain=BACKBONE

I have configured winbind on a Linux file server, connecting to a Samba PDC. When I run wbinfo -g, I can see the group "domain users". On the other hand, when I run getent group, I do not see this group. Apart from a few other groups, all groups are visibile in both wbinfo -g and getent group. When running for the first time wbinfo -u, getent passwd and wbinfo -g, I got the results