similar to: Unable to locate SID, possible problem with Idmap?

I have a samba PDC with LDAP backend running on CentOs 4. Everything is working fine, but my log watch report showed two users with the same SID. I checked it out and it appears that ROOT and the samba machine ASTER$ both have the same SID. If I do a pdbedit -Lv I get this: --------------- Unix username: aster$ NT username: aster$ Account Flags: [W ] User SID:

I have a working Samba PDC, I can log in and out from a windows xp workstation. I recently upgraded to 3.0.25b-33 and now, when I add a new user, I get: The system cannot log you on due to the following error: A device attached to the system is not fuctioning Please try again or consult your system administrator I have network connectivity. I was able to join this machine to the

Hello ! I've the following problem on my samba+ldap installation : The samba server (version 3.0.28-1.el5_2.1) is running on a machine named luke. The ldap server runs on a machine named anakin. Both of them seems to be setup correctly, since I can log in on the samba domain, but when I try to get an entry from the ldap database using the pdbedit command on luke, I get the following :

Hi ! I'm running a samba domain controler under rhel 5. It's version 3.0.33-3.7.el5. I've also installed a ldap server to store users and groups and so on. When I try a pdbedit -v david, I get the following : Unix username: david NT username: david Account Flags: [U ] User SID: S-1-5-21-215069222-2822928016-2390355089-1016 Finding user

I am obviously confused about something, and feel like I am chasing ghosts. Any help or clarification would be appreciated. When a user logs in we get messages about corrupt recycle bins. Setting the logging to level 2 for that client, we have errors like: open_directory: unable to create user/Desktop. Error was NT_STATUS_OBJECT_NAME_COLLISION. OK, the folder already exists in the

Am 26.04.2018 um 20:07 schrieb Harry Jede via samba: > No, i have created 2 users with same sid. > > root at capella:~# pdbedit -Lv | grep "User SID" | sort|uniq -d > root at capella:~# > > root at capella:~# pdbedit -L|grep Failing > ldapsam_getsampwsid: More than one user with SID [S-1-5-21-3958726613-3318811842-4132420312-21010]. Failing. count=2 >

Hi, I am running a couple of Samba / LDAP servers. While they all do work fine, I get a message like this on all of them when I run pdbedit -L -v: Unix username: administrator NT username: administrator Account Flags: [UX ] User SID: S-1-5-21-XXXXXXXXXX-XXXXXXXXXX-XXXXXXXXXX-21000 init_group_from_ldap: Entry found for group: 512 lookup_global_sam_rid:

Hi, samba 3.14 with ldapsam, working fine. I tried this usrmngr.exe thingie because one of our admins is very gui-oriented, wanted to see if it worked fine. For most users, it is. I can change details, logon hours, groups, passwords. But for 3 of them I get this message: ldapsam_getsampwsid: More than one user with SID [S-1-5-21-3707708495-1570892323-1667890705-3076]. Failing. count=3 I check

I'm using samba-3.0.23d-19 on openSUSE 10.2 with an LDAP PDC arrangement I'm trying to sort out some problems with adding a trust relationship. Specifically, smbpasswd is failing when I try to create/modify the domain account. Further investigation shows that it is also failing to modify workstation accounts. However it is able to modify user accounts fine. The big difference here seems

Hi List samba 3.0.31-36 openldap2-2.3.43-1.1 log level = 3 I have a problem, in my domain user log i see this: <snip> 2008/11/19 08:06:04, 3, effective(0, 0), real(0, 0)] smbd/sec_ctx.c:set_sec_ctx(241) setting sec ctx (0, 0) - sec_ctx_stack_ndx = 3 [2008/11/19 08:06:04, 1, effective(0, 0), real(0, 0)] passdb/pdb_ldap.c:ldapsam_getsampwsid(1501) ldapsam_getsampwsid: More than one user

Hi list, The task is to move an old samba installation (ubuntu with samba 3.0 brachch) to a new debian installation with samba 3.3.9. Both setups work as pdcs and have an ldap backend which I try to move from one setup to the next. In this new setup I tried to ldapsam:editposix = yes. Therefore I also installed winbind. I moved the domain SID and the local SID to the new pdc and filled the ldap

Liutauras Adomaitis pisze: > On Wed, Aug 26, 2009 at 6:11 PM, Volker > Lendecke<Volker.Lendecke at sernet.de> wrote: >> On Wed, Aug 26, 2009 at 06:05:35PM +0300, Liutauras Adomaitis wrote: >>> now size is few times larger. Try it now >>> http://www.infosaitas.lt/logas.txt >> Normally a "Device is not functioning" (or so) means an >>

Hi all, I'm having a problem with an upgrade of Samba running on a Redhat4 Update 4 system. The default installation provides only 3.0.10 which doesn't include the privilege model or a number of fixes including some in 3.0.21a and 3.0.23 which it looks like we'll need. The system runs in PDC mode with user accounts in an ldap database. On a test system which I'm using to

I have had a samba PDC up and running for about a month now with no issues, this weekend I added a BDC and it seems that all my clients are now logging into the BDC automatically instead of the PDC. I had to mount the homes from the PDC to the BDC so that users can have access to their home directories and set the path to the profiles directory on the BDC to that of the PDC. I also had to

My root account keeps getting locked out automatically. I am running Samba 3.0.25b on a CentOS server, as PDC with LDAP backend. I have accounts set to lock after 8 un-successful login attempts. I zeroed out the bad password count, and then in less than a few seconds the account gets locked again and a /pdbedit -Lv -u root /yields the following: Unix username: root Logon time:

Hy Samba users, I've got a problem with an samba/ldap setup. As I set an ACL to a domain group in an windows client, a group mapping entry will be created in the Idmap ou at the ldap server. I discoverd the OpenLDAP logfiles. There, the server sends a search request for the domain group sid to the ldap backend will retreive an entry back: Jan 15 20:19:24 225 slapd[4518]: conn=190 op=24

I have Samba 3.0.24 running on CentOS 4 as a PDC with an LDAP backend. When I first set everything up, I could join workstations to the domain automatically with the Windows Network ID Wizard. Now when I try to join a workstation I get: Your computer could not be joined to the domain because the following error has occurred: The user name could not be found. If I add the computer

I've scoured the mailing list archives and the internet...has anyone actually figured out how to enforce strong passwords when using Samba and LDAP as a PDC? My users are allowed to change their Windows XP passwords, how do I enforce the use of strong passwords (either locally or globally)? -- *Jason Baker */IT Coordinator/ *Glastender Inc.* 5400 North Michigan Road Saginaw, Michigan

Hello group, I have 2 Samba PCDs w/ LDAP + winbind called FILESERVER and FUNDUS-SRV for the domains PROFICON and FUNDUS, respectively. In PROFICON I created a trust account for FUNDUS using net rpc trustdom add FUNDUS <passwd> -U proficon\\administrator which creates the LDAP entry: dn: uid=FUNDUS$,ou=Computers,dc=office,dc=proficon,dc=sk uid: FUNDUS$ sambaSID:

I'm not sure if this is the right place to post this, but here goes. I just put together a PDC using Samba. I have given users the ability to change their passwords (once every 7 days) if they wish. I used to keep a list of usernames and passwords in a spread-sheet, so I could keep track of the servers that I needed to update with the correct password if anything changed. That being said.