similar to: Just a simple smbpasswd authentication won't work

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,

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, Can anybody confirm the following problem: Sequence: bash-2.05# grep ankerpos /usr/samba.moonrock/private/smbpasswd ankerpos:921:XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX:XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX:[U ]:LCT-0 bash-2.05# /usr/samba.moonrock/bin/smbpasswd -c /usr/samba.moonrock/lib/smb.conf ankerpos New SMB password: Retype new SMB password: bash-2.05# grep ankerpos

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

Hi, I have a problem with Samba 3.0.4 and DOS 6.2.2. Our clientinstallation works with PXE. This setup connects the samba-server with a DOS 6.2.2 batch-script, which attempts to copy a text-file from the client to the installation-share. I have interrupted the script and attempted to do the copy manually. Error-message: File not found. "copy a:\hwinfo.txt w:\$BmNewPc.Dir\05100be5.chi"

Dear Help, Initially, I thought that I had solved this problem, but it turns out that I haven't. I currently have Samba set up as a PDC with an eDirectory/LDAP backend. There are also a few Samba BDCs in play as well. If a user enters the correct password, there are no issues and everything authenticates fine. If I turn off the PDC and force a user to authenticate against a BDC with the

Server role: ROLE_STANDALONE [global] workgroup = G8DOWNRANGE server string = G8DOWNRANGE1 passdb backend = tdbsam guest account = g8team log file = /var/log/samba/log.%m max log size = 50 preferred master = Yes domain master = Yes wins support = Yes hosts allow = 10.0.1., 127. [printers] comment = All Printers path = /var/spool/samba printable = Yes browseable = No [work-clear]

Hi everybody, I want to use my samba-shared Homedirectory from my Linux-Server on my Linux-workstation. I was using smbfs until now, but since i upgraded my hardware i'm not any more able to use smbfs, i get error-messages (timeouts) in the kernel logs and I/O-Errors on the console. Having this problems i read about cifs and that's much better, nicer, sexyer and faster than smbfs.

Hello everybody, I have to face a problem here with a samba share disconnecting after about 10 minutes. Situation: - debian woody, samba 3.0.14a - server configured as PDC - typically 100-150 smbd processes running everything runs smoothly but one client (W2K SP4) that obviously needs a quasi static connection to the PDC. The client runs a software that stores regularly data on a dedicated

This is a repost. Original sent last Friday afternoon received no response. Any ideas would be appreciated. Should I try Samba 4? =-=-=-=-= I have a server which will accept a file sharing connection from a FreeBSD workstation using smbclient, but not from a Vista workstation. The server also performs as a NAT gateway. Upstream network configuration is by DHCP (dhclient), the downstream side is

Sorry all, I think I attached the wrong files. Apologies for the noise. Correct files attached. again .. these are from the logfile on the server and were in the log file named 192.168.168.13.log 192.168.168.13 is the IP address of the test client orgonon that I have set up for this. I have cut two sections from the log and they start at the same point and seem to be the same until line 162;

A new Debian(unstable) machine with Samba 4.5.2 is trying to join an NT4-style Samba domain hosted on a Debian(wheezy) Server with 3.6.6 which can't be changed but has been working for some years now with a couple of windows clients. Joining the domain was quite easy (only surprise was "client ipc signing"), and "wbinfo -u" gives me a list with all domain users. BUT

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 list, After upgrade my FreeBSD samba server from 3.0.5 to 3.0.6, my cifs client on my linux box stop. My linux kernel is 2.6.8.1 and samba* rpms is 3.0.6. But when try access any file (cat grupos.conf) on mounted point (smbfs) on freebsd server (3.0.6), this connection freeze. If samba on freebsd is 3.0.5 work's normally. This 2 logs generated with log level = 4 ---log on freebsd with

We are using samba 3.4.8. We have some pc's using OS Windows XP Pro dan others Windows 7 Pro. All of them can join and logon domain to samba PDC + LDAP. FYI, the windows 7 clients are already hacked at registry settings: [HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LanManWorkstation\Parameters] "DNSNameResolutionRequired"=dword:00000000

Hi, The following ii ?samba ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?2:3.4.7~dfsg-1 SMB/CIFS file, print, and login server for Unix ii ?samba-common ? ? ? ? ? ? ? ? ? ? ? ? 2:3.4.7~dfsg-1 common files used by both the Samba server and client ii ?samba-common-bin ? ? ? ? ? ? ? ? ? ? 2:3.4.7~dfsg-1 common files used by both the Samba server and client are installed on a squeeze ( 2.6.32-3-686 #1 SMP Thu

Hello all, My Samba server has undergone a series of migration. And recently, I found that the newer accounts fails to login to older computers in the network. All PCs in my network runs Window XP. And I'm running Samba 3.4.7 here as PDC. When I login with a new account called "guest2", the computer says the password of my login is incorrect. What is my problem? What should I

Hello I'm having some strange problems with samba 3.0.23d (PDC) on my FC6 if i start samba, everything works fine, but after an hour orso(some times 2 hours if there is not mutch traffic) machines and user accounts start expiring. i don't know why, but it is ?! after i do a restart, samba comes up and works again. i checked the mysql server (coz' i use pdb-sql as backend) but the