similar to: rfc2307 - 3.0.24

If I run a normal ldapsearch it gives me the gidnumber and uidnumber attributes. It looks like the AD is set up properly. ---------- Forwarded message ---------- From: Urs Golla <urs.golla@gmail.com> Date: Oct 4, 2007 9:47 AM Subject: could not read attribute 'gidNumber' To: samba@lists.samba.org Hi I am using samba 3.0.23c on RHEL5 with security = ads. If I use "idmap

Hi, I'm using samba 3.0.23c, and having a bit of trouble getting it to play nice with my active directory. I'm using Windows Small Business Server 2003 with the SFU 3.5 NIS server/schema extensions installed. I have samba configured to use ad as the idmap backend, and sfu for nss info. When running getent passwd, only a few active directory users show up, and I get lots of errors

My long sojourn to get some configuration set up that will then allow me to set a uid of an ad user to whatever unix uid I want (nfs reasons), is still going. I set my backend to ad and added the winbind nss info = sfu. Nothing happened initially in the log.winbindd-idmap, but after lunch I saw some new things in there: 83390]: sid to uid S-1-5-21-54348060-1989963526-242692186-2762 [2006/08/25

I am encountering some error I am unfamiliar with in the log.winbind. Any help is appreciated. [2006/01/23 06:44:32, 1] nsswitch/winbindd_user.c:winbindd_getpwent(715) could not lookup domain user rjb15 [2006/01/23 06:44:32, 0] tdb/tdbutil.c:tdb_log(772) tdb(/var/lib/samba/winbindd_idmap.tdb): rec_read bad magic 0x42424242 at offset=20784688 [2006/01/23 06:44:32, 0]

I have upgraded one of my servers from a 3.0.22 implementation using the rfc2307 patch I supplied some months ago to the 3.0.23 release. I am now getting some unexplaned failures and would like some pointers as to where to start looking. I am getting the following logged in the samba logs when trying to start the servers. zebra.log: Sid S-1-5-32-544 -> BUILTIN\Administrators(4)

I have Samba 3.0.7 installed and running in security = ADS mode and I've built and installed the Idmap_ad backend according to the instructions. Group lookups seem to work fine, but getent passwd and id functions fail with the message - ad_idmap_get_id_from_sid: ads_pull_uint32 : could not read attribute 'gidNumber'. If I manually run an ldap query against Active Directory the

Hi all, after I searched the internet about a week now I can't find an answer to my problem: The company I work for is using a Windows 2003 Domain using the Windows Services for UNIX (SFU) and NIS. We are using two Domain Controllers that are hosting the ADS. Now I want to use Samba and NFS to implement a file server for our mixed client enviroment: There will be Linux, HP UNIX, Solaris,

I don't think that this is my problem. When I try 'getent passwd <user>' I get no output either. And we only store about 200 users. Is bug 3024 fixed in the newest version? I will try to apply the patch. J?rg -----Urspr?ngliche Nachricht----- Von: Gautier, B (Bob) [mailto:Bob.Gautier@rabobank.com] Gesendet: Freitag, 21. April 2006 12:54 An: Horchler, Joerg;

>It's probably worth noting that for users who are >adding idmap_ad over an existing winbind setup, the >old mapping has to be deleted as above. Thanks, I'll put this in the README for the next version. regards, -- Luke --

Samba from git (4-8-stable and 4-8-test) is failing to compile. I did not have these issues with the previous 4-7 branches. Basically this installation is just a simple file server, no domain, ad, print service, etc. necessary or even desired. My configure arguments: $ ./configure --without-winbind --disable-avahi --without-ads --without-ldap --without-pam --without-quotas --without-dnsupdate

Hi Guys, i have a problem getting id mapping to work as it should. My setup is as follows: Samba 3.0.22 on Debian Sarge 3.1 . I 've got SFU 3.5 installed on a W2K3 DC with SP1. I 'm using winbindd in "idmap proxy only" mode. Here 's my generic smb.conf: workgroup = METADS realm = META.XXX.XX "it 's not the real realm, of course !" security = ADS

I'm receiving the errors listed below. It also seems unable to map the root user uid 0 with this filter. That's not that big of a deal. Wbinfo -u and -g return output but getent passwd does not. This is Ubuntu 7 using debian packages. [2007/06/28 13:27:59, 5] lib/username.c:Get_Pwnam_alloc(131) Finding user DOMAIN\chapman [2007/06/28 13:27:59, 5]

As part of our deployment of FC updates we have upgraded our office server from 3.0.24-3 to 3.0.24.4. We got some strange results. Shares that have the same name as the users home directory and/or the same name as their users id became inaccessible. For example, my user id is kens, my home directory is in /home/kens and there was a share of it called kens. There is also a common share

I'm having a problem with BUILTIN accounts on a Samba 3.0.24 PDC with an LDAP backend on Ubuntu. I followed this guide for setting up the server: http://samba.org/samba/docs/man/Samba-Guide/happy.html ...and everything worked well until I migrated all the user, machine, and group accounts from the old domain and the PDC went into production this morning. Once the machine went live, I

Has anyone experienced any issues with Samba (3.0.24-r3), specifically with ADS domain joins, running on Hardened Gentoo 2007.0 (kernel 2.6.21 / AMD64)? I get "CLDAP Request Failed" error messages when attempting to do a net ads join, which has been successful with numerous other systems. This is familiar territory for us and a new issue never seen before. Thanks.

Coin, Quoting Quartexx <quartex73 at gmail.com>: > I'm experiencing your same issue. Have you found a fix for this? > Thanks in advance for your reply I downgraded to 3.2.5 to get a working version on the production server, and made a few more tests with 3.4.5. I discovered the ACL bug was linked to the full_audit vfs object, and deactivating it fixed the modification

I'm currently running samba 3.0.20a I can configure and make 3.0.20a with no problem I run the same configure command on the 3.0.24 source, configure works fine, but make returns the following. ( and just to test if a patch screwed me up I tested configuring and making the 3.0.20a version again, and it worked as it should ) Any bugs with 3.0.24??? Using FLAGS = -O -D_SAMBA_BUILD_

here's my krb5.conf:-----------------------------------------------[libdefaults] default_realm = HQ.COMPANY.COM [realms] HQ.COMPANY.COM = { kdc = 192.168.100.1 }[domain_realm] .hq.company.com = HQ.COMPANY.COM hq.company.com = HQ.COMPANY.COM----------------------------------------------- here's my

Hi all, is there a dead line for 3.0.24? Regards, LD

greetings list. am serving SMB using the samba-3.0.24 package on an openbsd 4.1-release machine and am seeing really low throughput from the server, even when both the server and client are on gigabit ethernet. the maximum throughput i've been able to attain is ~6 MBps, which is pretty slow, both on 100 Mbps and 1 Gbps segments. this top speed is identical on both 100 Mbps and 1 Gbps.