similar to: strange error: modify/delete: sambaPwdCanChange: no such value (Success)

AIX 5.2 OpenLDAP 2.2.15 Samba 3.0.7 (no winbindd) I've got a stupid problem with referrals that I can't seem to ferret out. Each Samba DC has a localhost-based LDAP replica for scalability (my idea anyway). So the only way they will talk to the Master is if there is need for an update. Ok. If I make the updatedn the same as the rootdn of the replica, it updates the local database;

Hello! SuSE Linux 10.0 Samba 3.0.20b OpenLDAP backend IDEALX scripts v0.9.2 Windows XP SP2 client Everything seems to be working except when changing your password from the Windows client (CTRL-ALT-DEL and "Change password"). When I try to change the password I get the following error message. "The User name or old password is incorrect. Letters in passwords must be typed

Hello all, I am trying to add W2K8 server to our domain "ns.local". This domain is working O.K. for all XP machines we have (~10), but when adding a W2K8 server, I get user/pass prompt and then after typing my* username and password I get: --------------------------- Computer Name/Domain Changes --------------------------- The following error occurred attempting to join the domain

Greetings, I am trying to join a EMC Celerra NS502 CIFS server to our Samba 3.0.21a domain controller. According to EMC, I was told that we need to manually create the machine account first. How is the best way to do this? We are using an openLDAP backend, using the idealx scripts. Joining a windows machine from the computer properties dialog of that machine works perfectly. Things I have

hi, i see the same error message with samba 3.0.14a and OpenLDAP 2.2.23 (Debian Packages) with Master/Slave setup. i did not set up a referral to the master, so why does samba get a referral when attempting to write to a slave? is this an in-build samba feature? do i have to enable referrals to get this to work properly? any advise is appreciated! thx! micha Zwonarz Ivo wrote: > We use

We use sambaPDC + LDAP On our BDC we have a replicated ldap slave. Everything seems to work fine. Hower, in the smbd log file we have the following messages (only on the BDC's) [2006/05/31 15:25:08, 1] passdb/pdb_ldap.c:ldapsam_modify_entry(1495) ldapsam_modify_entry: Failed to modify user dn= uid=pc01233$,ou=Machines,dc=brrc,dc=be with: Referral [2006/05/31 15:25:08, 0]

Hey list, Recently I've gotten my Samba PDC to successfully use an OpenLDAP backend, while using the smbk5pwd and ppolicy overlays for OpenLDAP. However, Samba appears to incorrectly handle responses from LDAP's ppolicy overlay, even though it very clearly receives them. If I enter in a password (be it through Ctrl+Alt+Delete or when a password expires and the user is prompted at logon)

Hi Daryl, > I recently migrated our samba PDC to an LDAP backend on a test machine. > Testing my account policies, I found out that the password lockout did not > work. bad password lockout works fine in Samba AD mode. Is there a technical reason for you to keep on using PDC NT4 mode? In AD mode, you'll also get a LDAP, and it will be much easier to setup and manage! By the way,

Howdy, I'm having one last problem with my Samba PDC with an ldap backend. When I add a machine to the domain I get the error, on my Win7 test client, that says: The following error occurred attempting to join the domain "office": A device attached to the system is not functioning. Here are some particulars: # smbd -V Version 3.5.6 (configured sernet repo to install latest

I found out the answer to why the bad password count was failing by following the stack trace If anyone has the same problem, this was caused by my access rights being too restrictive. source/passdb/Init_sam_from_ldap.c:1064 => There is a "goto fn_exit;" in case ldapsam_get_entry_timestamp() fails before the cache is read via login_cache_read. This function will fail if it cannot

Hi Denis, Thanks for your suggestion When I looked into Samba4 AD, I figured it would take too much effort to port our infrastructure to it, seemingly without benefits We already have a quite extensive network architecture with OpenLDAP acting as a LDAP server. Samba4 AD seems to require its own LDAP implementation (and some more quirks IIRC). There's also the additional DNS configuration

Hi everyone, I'm unable to make the account lockout to work properly. & this is driving me mad. I am running samba Version 3.0.23c-1.fc5 as a PDC with openldap 2.3.19 on a fc5 (all packages from yum). I was running a 3.0.21 with the same issue. I'm using as well the Idealx script to manage the LDAP. The fact: I have a very strange behavior. The domain policy have been setup with the

Hi All, I have a strange problem with passwords, stored in LDAP. When i try to logon as a user with the correct password, access is denied and the log says check_ntlm_password: Authentication for user [administrator] -> [administrator] FAILED with error NT_STATUS_NO_SUCH_USER When i try to logon a user with incorrect password, access is (of course) denied, but the log now says

I'm switching from OpenLDAP to the newly released Fedora Directory Server (formely known as the Netscape Directory Server) as a LDAP backend for my Samba domain. I'm now faced with a problem regarding how Fedora DS handles the userPassword field. Unlike OpenLDAP it encodes it in base64 so instead of reading userPassword: {SSHA}0lP+r3Z1NVan7Caf4CG9oSgnTbQRrv/p it reads: userPassword::

Hi, I have a strange problem with a Windows Server 2008 R2-System as a member of a samba domain (Samba-Version on PDC: 3.4.12). Join was successfully, but when I log on Windows I got an error "Unknown user name or bad password." (Event ID 4625). Here an abstract of logfile for Windows Server 2008 R2-System (log level 10). Maybe some of you has an idea:

Q#1. What SAMBA related object classes and attributes I must add to a POSIX user in LDAP (SunOne DS 5.2) before it can be used by SAMBA for authentication? Q#2. Why does the SAMBA log for the user show the error ?FAILED with error NT_STATUS_WRONG_PASSWORD? even before the user is prompted for username and password on the SAMBA client? Also in this log, I saw another error ?NT MD4 password

I recently migrated our samba PDC to an LDAP backend on a test machine. Testing my account policies, I found out that the password lockout did not work. When authentication fail, samba seems to call init_ldap_from_sam asking to update the bad password count. When I set the lockout threshold to 1, the account is locked after a failed attempt and the badPasswordCount attribute is updated correctly

Hi everybody, I'm an italian system administration (newbie about Samba). I have installed on Mandrake 9.1 the rpm samba3-*-3.0.2a downloaded from a Samba.org's mirror. I have configured a PDC based on ldapsam (OpenLDAP 2.1.29) that works fine, i use smbldap tools to manage sincronization account. Now the problem, when I try from my W2000 Workstation to change my domain password I reach

When I am setup external passwd change script (syncldap) for sync my smb pass and unix pass, and change smb password on my windows client client, him return error, but password change is successful! It's log from samba for my windows client machine: [2004/08/04 11:46:52, 3] smbd/chgpasswd.c:chat_with_program(424) chat_with_program: Dochild for user g-marchenko (uid=0,gid=0) (as_root =

Hi everybody, I'm an italian system administration (newbie about Samba). I have installed on Mandrake 9.1 the rpm samba3-*-3.0.2a downloaded from a Samba.org's mirror. I have configured a PDC based on ldapsam (OpenLDAP 2.1.29) that works fine, i use smbldap tools to manage sincronization account. Now the problem, when I try from my W2000 Workstation to change my domain password I reach