similar to: Samba 2 PDC upgrade to Samba 3 - group mapping problem

All, I've got a Samba 3 PDC serving numerous XP clients, and I'm getting an error I wouldn't have expected. When trying to rename an XP machine joined to the domain (via "netdom renamecomputer"), the command fails unless the specified domain user has UID 0. The command in question: netdom renamecomputer %COMPUTERNAME% /newname:%NEWNAME% /userD:DOMAIN\USER

Hi, I have troubles when trying to login to my SAMBA Domain, joinung the workstations to the domain was no problem, browsing shares is no problem, but no damain login. I'm running centos 4.3; rpm -qa |grep samba system-config-samba-1.2.21-1 samba-client-3.0.10-1.4E.9 samba-3.0.10-1.4E.9 samba-common-3.0.10-1.4E.9 rpm -qa |grep openldap openldap-clients-2.2.13-6.4E

I just got Samba + LDAP up and running as a PDC. If I list the users in the LDAP directory with pdbedit -L I see: root:0:test nobody:99:nobody aster$:1001:Computer toast$:1002:TOAST$ fordprefect:1003:Test Account Shouldn't there be an Administrator account and no root? I don't want my Linux root account even remotely confused or associated with a Samba/LDAP

freebsd 5.3, samba 3.10 I get this far with LDAP/Samba integrationg. Stuck on creating users/machines with smbpasswd -a (-m) username command. schema files weren't modified, everything else is pretty much at defaults. First the relevant config parts: passdb backend = ldapsam_compat:ldap://localhost/ ldap suffix = dc=company,dc=com ldap machine suffix = ou=Computers ldap user suffix =

What does the list think of setting "locking = no" on the netlogon share for a PDC? The man page for smb.conf says we should never need to set the parameter, but given that it's a read-only share for most users, I have a hard time discerning any downside to this. Thoughts? Ryan -------------- next part -------------- ------------------------------------------------- This email

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I have seen this problem posted several times and the common answer doesn't seem to be doing it for me. Here's the error: Trying to load: ldapsam_compat:ldap://127.0.0.1/ Attempting to register passdb backend ldapsam Successfully added passdb backend 'ldapsam' Attempting to register passdb backend ldapsam_compat Successfully added

Hello! I'm looking for a solution, how the data of a Samba server can be shared between 2 Samba Servers (2.x and 3.0) during migration process. The new environment will be done from scratch, new Hardware, etc. Old Samba server/environment: Samba 2.x Authentication via W2k Server (security = DOMAIN) Server has more than 100 netbios aliases No POSIX-ACL's Users and Groups are stored

Hello, I am trying to test out the new beta 3.0 version but I am running into an issue with GID/UID's in my OpenLDAP tree. I have compiled the beta with: --with-ldapsam --with-ads=no I do not run a PDC environment and do not plan to do so. The problem I see in the log is this error: sid_to_gid: SID S-1-5 bla bla -1002 is *NOT* a group (the user that I am trying to authenticate with has a

Hi there I am using Samba 3.0 release with the ldapsam_compat backend until we are ready to migrate to the new LDAP samba schema. Using the same "root" LDAP user (and smbldap-tools) that Samba 2.28 allowed me to add workstations to the domain successfully, I receive a new error - "No mapping between account names and security IDs was done". When I switch to the domain

Does anyone know if on Redhat AS 3, The Samba 3 Rpms have ldapsam_compat compiled in? I am trying to get it working and so far not having any luck. - Jamie

Hi. I am trying to get Samba 3.0.4, from tarball, working with Fedora Core 1. The problem is that I can't get LDAP authentication with either ssl or start_tls support. I tried compiling ldap on a plain install of fedora. I also tried compiling it after installing openssl-0.9.7d and openldap 2.2.11 clients and libraries from tarball. My ldap configuration of samba is as follows:

Dear All, When i configured samba to use openldap for passdb backend, no one could connect to it, (all workstation maked time out.) But, pdbedit -L works and prints all the users i've created.So, i think everything about my ldap is right. (I've used samba 2.x scheme on my openldap, so I used ldapsam_compat:ldap://localhost/ for passdb backend.) when i comment the LDAP lines of my smb.conf

Samba3.0rc4 When i type : smbpasswd -a ntadmin1 -D4 i have a output --------------------------------------- Netbios name list:- my_netbios_names[0]="ORLEAN" Trying to load: ldapsam:ldap://127.0.0.1 Attempting to register passdb backend ldapsam Successfully added passdb backend 'ldapsam' Attempting to register passdb backend ldapsam_compat Successfully added passdb backend

hi, we recently upgraded from samba 2.2.8a w/ldap to samba3 w/ldap and having troubles with domain group mappings. first symptom is that net groupmap list returns nothing. [root@lola root]# net groupmap list [root@lola root]# if we try to add a groupmapping, the command fails: net groupmap add sid=<sid-gid> ntgroup="Domain Admins" unixgroup=domadm type=domain --debuglevel=4

Hello, Help!! I'm struggling with ldapsam. I'm trying to configure Samba to use our LDAP directory (Sun's directory server) for the storage of Samba user accounts. It already stores our unix system accounts. I have successfully imported the schema file into our directory server and have compiled samba with the "--prefix=/opt/btifs/samba --with-ldapsam" options. I

I'm having some issues with samba 3 and my ldap passwords. First I'll tell you what I'm working with. Ldap server is RH 7.3 and openldap 2.0.25 DBM Samba 3.0.2a-1 using ldapsam_compat (Compiled from RPM source by me ) on RHEL 3 Samba 2.2.8-1.ldap on RH9 -------------- The Samba 2 works great. Auth against ldap no problem, has been for over a year. The Samba 3 does not work.. Well

Hi! I am seeing other users with the same problem as I have. My samba also fails to add machine accounts. It seems to me if it didn't even try. If I use some other script (pdbedit, smbldap-tools) than smbpasswd it manages to add the account but still fails to authenticate within the same session. If I try again the machine account exists and authentication goes ok. server:~# smbpasswd -a -m

Sorry to repost this question.. But I am at my wits end.. The server has been off line for 2 weeks. So I will have to downgrade to samba 2.X by the end of the day unless a miracle happens ;) I'm having some issues with samba 3 and my ldap passwords. First I'll tell you what I'm working with. Ldap server is RH 7.3 and openldap 2.0.25 DBM Samba 3.0.2a-1 using ldapsam_compat (Compiled

Hi everybody, i'm having serious problems with the configuration of samba 3.0.10. First my setup : samba-3.0.10 built from source openldap-2.2.20 built from source OS : Suse Linux 7.1 (but updated -> Kernel 2.4.27) My problem : ------------ I'm trying to use smbpasswd like the following : ---snipp--- [PTS2] 486dx66:/usr/local/samba3 # bin/smbpasswd -D 10 tina Netbios name list:-

I can't really guess the point of your intelligent answer from this. If I have to assume you're surprised, I guess I am too. The cn exists in ldap, with all the attributes that I imported from other databases, the message given by smbpasswd suggests that it either tried to create an entry or update it with sambaaccount attributes ( which it didn't ), neither of which are the expected