similar to: Urgent Help :How set "NT password" for an for an user

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

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 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. We have a number of working ADS servers. One of out clients is not in the Kerberized domain so there users log in via NIS. Having looked at the options for enabling NIS authentication I have decided to use the smbpasswd. Now I can't get that to work. After using smbpasswd to create two users, one created locally, in the /etc/passwd, and one that exists already in NIS. Not only

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

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

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

Hi, I'm setting up a new sambserver, migrating from 2.2.8a with ldap backend to 3.0.x (3.0.2a and 3.0.3pre2 tested) with openldap 2.1.26 backend and using sambaSamAccount I'm experiencing the following problem: - Roaming profiles sometimes work, sometimes not (most of the time not) and show erratic behaviour like removing the local copy (without having the DeleteRoamingCache key in

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

Dear Help, I currently have a Samba PDC along with multiple BDCs using an eDirectory LDAP backend. While trying to figure out how to get the bad password account lockout feature to work, I managed to somehow mess up the samba PDC. If a user attempts to authenticate against the PDC with the correct password, all is well and works as usual. However, if I use an incorrect password, the Windows

I'm running Centos 4.3 and Samba 3.0.24. I have an OpenLDAP backend. I have successfully got a Windows Domain to work, Windows XP -> Samba -> OpenLDAP. I can add machines to the domain and I can login and change passwords. The trouble is that I'm using NTLM and have been told that I must upgrade to NTLMv2, but I'm having great difficulty doing so. I have existing NTLM users. I

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

There is something very strange going on with new users... i've created a new user using the smbldap-tools creation goes fine... smbldap-useradd -a -g labusers -G power_users -n -c 'test user' -m -P testuser I've set the password and i see this in my ldap dir: ldapsearch -x -D cn=ldapadmin,dc=bitc,dc=unh,dc=edu -W '(&(uid=testuser)(objectclass=SambaSamAccount))' #

I'm sorry for asking a question which has been asked so many times before, but I can't seem to find the answer... How do I get to access my home directory on a Linux server running Samba from a Windows XP client? I'm getting "NT MD4 password check failed" in the log file even though the Windows client is listed in hosts.equiv. More information below... I have a small home

Hello, i set up a squid proxy that should authenticate users against a samba PDC using winbind. It works fine as long i allow ntlmv1: on the PDC: ntlm auth = yes lanman auth = no client ntlmv2 auth = yes If i restrict the domains authentication method to ntlmv2 - that's what i want - with these settings: ntlm auth = no lanman auth = no client

Hi, - OpenSuse 42.2 - Samba Version 4.4.2-11.3.1-3752-SUSE-SLE_12-x86_64 I'm using samba for file sharing, where users have some control of the shares. This is a standalone server All works fine, the user was created and added on the samba host with smbpasswd -a <user> *The problem is*, when the samba password is changed using smbpasswd <user> , the Windows machines no

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

Hi all, In short, how do you force smbclient not to use Lanman passwords ? I specify these in my smb.conf lanman auth = no min protocol = NT1 Trying smbclient from the same host, root@localhost root]# smbclient //fileservertest/private -U somebody Password: Domain=[WORKGROUP] OS=[Unix] Server=[Samba 3.0.2a] tree connect failed: NT_STATUS_WRONG_PASSWORD Here are the logs, [2004/03/17

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"