similar to: ldap passwd sync only

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

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

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]

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! 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 everybody I have configure a Samba PDC machine, using LDAP as password backend. The scripts smbldap-tools are used to create the accounts in the LDAP. I can add Windows XP machines to the domain without problems. But today, I tried to add a Windows NT Server SP6a machine to the domain, and there is the next error: smbldap_get_single_attribute: [sambaLogonHours] = [<does not

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:

On 24/03/15 17:32, Elias Pereira wrote: >> it has been sometime since I used an NT-4 style domain, but I seem to >> remember that you need to run the command as root and the user needs to >> exists as a Unix user. >> > You were right! Fixed! > > Continuing: > > But now when I try to join a window xp sp3 in the domain, it does the > following error: >

On 24/03/15 18:40, Elias Pereira wrote: > I had tried with the "root", but also gave error: *Could not find the > username.* > > The first time this happened I ran the following command: > > root at sol:~# smbpasswd -a root > smbldap_search_domain_info: Searching > for:[(&(objectClass=sambaDomain)(sambaDomainName=POA))] > smbldap_open_connection: connection

Hello, I have a working samba (2.0.7) server (Debian GNU/Linux 2.2) configured with security = user, but NOT domain. The clients are Windows 98. I whish windows users to be able to change their password without logging on the server (unix account on the server are disabled). I tried from the Password applet of the Control Panel, but I was able only to change the password stored on the Windows

Hello, i'm using Samba Version : 2:3.5.5~dfsg-1~bpo50+2 from backports Patch applied : http://support.microsoft.com/kb/2171571 Key modified : [HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LanManWorkstation\Parameters] "DNSNameResolutionRequired"=dword:00000000 "DomainCompatibilityMode"=dword:00000001

Hello, I have a centOS 5.5 box acting as as a PDC with samba 3.4.9 and openldap 2.4.22. Then I joined the domain with a centOS box (samba 3.4.17) which hosts the homes and profiles. I have no problem with XP clients. I can join a windows 7 client to my domain but it is unable to load the profile when logging in. See below a level 2 log.smdb from the file server when I log in with a domain

Hi We have a Samba server that authenticates with an openldap server. Or it used to. We had a power cut last week and after a bit of struggling everything came back, but not Samba. Previously our smb.conf file included the line passdb backend = ldapsam:ldap://server.domain.net/ With this line in place the connection to the LDAP server fails, and peoples shares drop off every few minutes. I

just small update: - idfix tool (Directory Synchronization Error Remediation Tool / https://github.com/microsoft/idfix) shows just small issues like empty/missing displayName attrib in some of objects which I have corrected and no more issues present at all. - no errors from AAD connect event viewer: final log message is "Scheduler::SchedulerThreadMain : Completed configured scheduler

Hello list, we have two samba servers on two localities with bigger distance between them. On both localities there are organizational staff working. And I am trying to configure homedirectories for all of staff in this way: - all users will have same beginning part of URL path where is their homedir located (i.e. \\files.example.com\loginname) for unification and central acces - but because

Hi Michal, Seems we are doing similar things at the moment: getting samba to work with azure AD. We also see the high CPU usage on the DC that the Azure AD Connect server connected to. Between 70 - 100 percent in our case. We are not seeing any replication issues after azure AD Connect, and I have a script that automatically checks replication every few minutes. I was the one reporting the

Hello, Recently our Samba server has started segment faulting. It happens occasionally, but is often enough to cause disruption. People notice thier network drives freeze, I am unsure of the cause of the segment fault, and have no experience debugging backtraces. Can anoyone lend a hand? We are running Samba as a primary domain controller with an Openldap backend on another server, both on