similar to: Samba 3 and NTLMv2 support

Hi folks, I have been asked to force NTLMv2 logins to avoid use of LM hashes. To meet the requirement I added some lines to the smb.conf in [Global] (we only have that section anyway - this is purely for domain authentication with an ldap backend): client lanman auth = no client NTLMv2 auth = yes lanman auth = no min protocol = LANMAN2 ntlm auth = no This seemed to work - users

Hi all, In my win2k ADS server(mixed mode), I have set the LAN Manager authentication level to Send NTLMv2 response only\refuse LM & NTLM. In the registry, i also set HKLM\System\CurrentControlSet\Control\Lsa|lmcompatibilitylevel --> level 5 (accepts only NTLMv2). Similarly, i also set HKLM\System\CurrentControlSet\Control\Lsa\MSV1_0\NtlmMinClientSec --> 0x00080000(NTLMv2 Session

Thanks Andrew for the answer. But even if I enable Windows XP to use NTLMv2 (using Regedit on (HKEY_LOCAL_MACHINE/SYSTEM/CURRENTCONTROLSET/CONTROL/LSA LMCOMPATIBILITYLEVEL to 5) and adding "ntlm auth = ntlmv1-permitted" to my smb.conf Still the same error. (No *more connections can* be *made* to this remote computer at this time) in versions higher than 4.10. Any ideas? Best Regards

On Tue, 16 Jun 2020, Rowland penny via samba wrote: > On 16/06/2020 12:41, Harald Hannelius via samba wrote: >> I have Samba AD-domain with two fileservers and two Samba DS-servers. Most >> people can authenticate OK, but one user always gets "wrong password". > What versions of Samba ? All servers are 4.9.5-Debian. >> Auth: [SMB2,(null)] user [SAD]\[username]

Hello experts/users, We have a samba server in ubuntu 18.04 LTS with version. apt-cache policy samba samba: Installed: 2:4.7.6+dfsg~ubuntu-0ubuntu2.16 Candidate: 2:4.7.6+dfsg~ubuntu-0ubuntu2.16 All is fine and great. Except one (internet disabled) windows 7 professional PC (sorry we still need to run it for a scientific tool) cannot connect unless I put "ntlm auth = yes" in

I discovered the situation. When attempting to logon from Windows 2008R2 to Samba4 is made we can see in Samba smbd log the following important for understanding the situation lines: [2017/11/20 13:25:52.040094, 2, pid=7100, effective(0, 0), real(0, 0)] ../libcli/auth/ntlm_check.c:430(ntlm_password_check) ntlm_password_check: NTLMv1 passwords NOT PERMITTED for user <username> [2017/11/20

Hi, I'm wondering if samba supports NTLMv2, particullary NTLMv2 session security. But I can't even get NTLM-only to work :(. I'm trying to increase lmcompatibilitylevel, but I can't connect to the samba server anymore when I set it to 2 or higher ("Send NTLM authenication only"). I'm using HEAD CVS of today, and my smb.conf looks like this: [global]

Am 09.06.2017 um 19:55 schrieb Rowland Penny via samba: >> Can anybody please help me, even by simply giving me some hints to >> point me in the right direction to do a deeper investigation? >> >> Thank you very, very much in advance, >> best regards > > Try adding 'ntlm auth = yes' to smb.conf and restart Samba. > It was changed from 'yes'

On 25/06/2020 16:56, Greg Marshall via samba wrote: > Hello experts/users, > > We have a samba server in ubuntu 18.04 LTS with version. > > apt-cache policy samba > samba: > Installed: 2:4.7.6+dfsg~ubuntu-0ubuntu2.16 > Candidate: 2:4.7.6+dfsg~ubuntu-0ubuntu2.16 > > All is fine and great. Except one (internet disabled) windows 7 > professional PC (sorry we

Are there multiple ways that Windows clients encrypt passwords? I'm seeing different behavior between two clients. On one, I can access a Samba share just fine. On the other, using the same username and password to access the same share, I get "incorrect password." Looking for the difference in Samba debug traces, I find it comes down to this: smb_password_ok: Checking SMB

Hi, I'm running Samba 3.5.6 with OpenLDAP 2.4.23 (from Debian Squeeze) as PDC. Everything is working fine (Joining Domains, Log on Users) but I'm not able to Log in as Domain Admin. If I try to, the message "Unable to log on ?The User Profile Service service failed the logon. User profile cannot be loaded." (in german: "Fehler bei der Anmeldung mit dem

HI to all! My Name is Juan Franco. I'm from Argentina, I work in a big gubernamental organization and we are migrating our deprecated (smb3 + Ldap + NT4) to Samba 4 AD DC: But I have some issues with newer versions. if I install a version newer to 4.9.x. Windows XP can't join the domain. The error message is ".. No *more connections can* be *made* to this remote computer at this

On Tue Feb 17 11:14:15 GMT 2004, Andrew Bartlett wrote: >> Any suggestions for things to try (or even a guaranteed solution ;-) ) would >> be very much appreciated. >> server signing = no >Try this as yes. How did you get it work? I've tried the "server signing = yes or auto", but it didn't work. Could you kindly tell us how to set the XP to get it

Hello all, I guess that everyone knows the message "the trust relation between this workstation and the primary domain failed" when joining Win7 into samba domain. Unfortunately, the same problem appeared few hours/days after the machine was successfully joined in the domain(with reg keys from https://wiki.samba.org/index.php/Windows7) and user able to use it for awhile. Then at

Hi all, I'm running Samba 4.1.6 with Ubuntu 14.04.1 LTS on a Power 8 box. Here is my smb.conf file: [global] client lanman auth = yes client ntlmv2 auth = no lanman auth = yes netbios name = myName map untrusted to domain = yes log level = 3 [myshare] path = /home/myuser/myshare available = yes valid users = myuser read only = no browseable = yes public = yes writable = yes When I try to

Hi Rowland, Thank you very much, you were spot on. I had changed the Windows 7 client to LM compatibility level, and now that I reverted it back to 5 (use NTLMv2) it works. It was this registry key that made it start working: [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa] "LmCompatibilityLevel"=dword:00000005 I was ignoring the old LM options and the "NTLMv1" in

Hello. I've just compiled Samba-3.0.0 on Tru-64 5.1b (AKA Digital Unix, AKA OSF) with base security (no shadow passwords) using the native compiler and GNU make. In smb.conf I'm forcing NTLMv2 only: security = user encrypt passwords = yes lanman auth = No ntlm auth = No client NTLMv2 auth = Yes client lanman auth = No

Probably this information affects Samba, ftp.microsoft.com/bussys/winnt/winnt-public/fixes/usa/NT40/hotfixes-postSP3/lm-fix DOCUMENT:Q147706 TITLE :How to Disable LM Authentication on Windows NT PRODUCT :Microsoft Windows NT, Windows 95, Windows for Workgroups 3.11 and LAN Manager 2.2c PROD/VER:2.2 3.11 4.0 95 OPER/SYS:WINDOWS KEYWORD :kberrmsg kbfile ntsecurity NTSrvWkst ntstop

On 08/20/2017 02:14 AM, ToddAndMargo via samba wrote: > On 08/20/2017 01:20 AM, Rowland Penny via samba wrote: >> On Sat, 19 Aug 2017 17:56:06 -0700 >> ToddAndMargo via samba <samba at lists.samba.org> wrote: >> >>> The cure was to add to smb.conf >>> >>> ; To operate with XP, add the following to the [global] section: >>> ; lanman

Can someone tell me what this means; [2004/03/30 12:09:56, 0] rpc_server/srv_pipe_hnd.c:process_request_pdu(605) process_request_pdu: failed to do schannel processing. Martin Stacey IT Support Manager Safcol Australia Pty Ltd