similar to: Windows client does not recognize password change...

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::

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

Hello Sorry to ask here, but all googeling doesn't helped. We have several samba domains (samba 3.5.6) with ldap backed and windows 7 clients, which worked fine so far. Know we begin to see that random machines begin to kick out of the domain with the error: _netr_ServerAuthenticate3: netlogon_creds_server_check failed. Rejecting auth request from client MBBUCHHALTUNG04 machine account

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 I just re-initiated by ldap sam database using smbldap-populate.pl, modified the Administrator account (uid/gid=0). I can join the domain from a Samba 2.2.7 linux machine, it creates the machine account etc... The problem happens with Windows 2000 SP2, It tells me wrong user/password. Here is the samba error : decode_pw_buffer: incorrect password length (-2118884061). Here is the full log :

Hi, I'm back on the list ;-) I seem to be having some trouble getting W2K machines to join the domain in 3.0.1rc2. I haven't looked at this in detail since 2.2.8a but it looks like the account gets created in LDAP and then it has trouble setting the password appropriately. I believe this is the relevant part of the log: api_rpcTNP: samr op 0x3a - api_rpcTNP: rpc command:

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]

I'm relatively new to samba I have been experimenting for a week or so, though I have setup several 2000/NT domains and have been using Linux for a couple of years. I'm using Red Hat 9, updated completely via apt. Samba 3.0.9 installed from apt and i am using the stock ldap server that installed with red hat as my back end. I followed the samba.idealx.org guide to get to where I am

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

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

Hello I have exactly the same trouble as described here: http://www.nabble.com/ldap-passwd-sync-on-3.0.25a-tf4261008.html on samba-3.0.25b-2.fc7. When i set "ldap passwd sync" to "only" and I change password on some ldap samba user, password in attribute userPassword is never changed by samba daemon (to update NT and LM password I use smbk5pwd overlay). If i set pwd sync to

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,

Hello list I have a problem that i am confronting for long time and i dont get a result. We use samba 3.0.24 (also tried other versions) with openldap and the smbldap-tools on Suse Linux SLES9. We use openldap for user authentikation for samba (objectClass: sambaSamAccount) and other application like email, apache, squid (objectClass: shadowAccount and objectClass: posixAccount). My scope

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 people: I have a Debian etch stable with the latests updates. When I try to join a computer to the domain I create the machine on the ldap and its created with the following atributes: dn:cn=test$,ou=Machines,dc=domain,dc=org objectClass: top objectClass: inetOrgPerson objectClass: posixAccount uidNumber: 3123 uid: test$ cn: test$ sn: test$ gidNumber: 604 homeDirectory: /dev/null loginShell:

Hi! Does this sound familiar, before I try to look deeper into it? [2005/02/13 20:10:16, 0] /usr/ports/net/samba/w-samba-3.0.11/samba-3.0.11/source/libsmb/smbencrypt.c:decode_pw_buffer(539) decode_pw_buffer: incorrect password length (1251354155).

Hi I have a PDC/BDC samba/ldap environment. PDC: samba 3.0.24 slapd 2.3.30 BDC: samba 3.2.5 slapd 2.4.11 Ldap replication is working fine, but I have noticed two issues 1- when a windows user change password on BDC, sambaPwdMustChange and sambaPwdCanChange is not synced on PDC (using ldap passwd sync = yes and unix password sync = no) 2- when using 'net sam set pwdmustchange' on

Has anyone got unix password sync for samba3.0.x running successfully on SLES8 server? Do I need the SLES service packs? Is there an interaction with PAM that I need to be aware of? I've compiled the full developer build of samba from 3.0.4-4 source. Compile was successful. I'm running tdbsam as password backend. I've troubleshooted quit a bit using google, docs, etc. as

I am trying to do a classicupgrade.  (This is not 1st try, I went through it once time already; then I deleted all data and trying it again, with questions now.) Command samba-tool domain classicupgrade --dbdir=/etc/samba.PDC/ --realm=ad.nemuh.cz --dns-backend=BIND9_DLZ /etc/samba.PDC/smb.PDC.conf Problem a) ... init_sam_from_ldap: Entry found for user: pc0027$ init_sam_from_ldap: Failed to

Hi Rowland, I tried that but didn't work. # AUTO-GENERATED FILE - DO NOT EDIT!! Use ldapmodify. # CRC32 9033b998 dn: olcDatabase={1}hdb objectClass: olcDatabaseConfig objectClass: olcHdbConfig olcDatabase: {1}hdb olcDbDirectory: /var/lib/ldap olcSuffix: dc=testdom olcAccess: {0}to attrs=sambaNTPassword,sambaPwdLastSet,sambaPwdMustChange by dn="cn=admin,dc=testdom" write by self