similar to: ntlm

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

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 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: I have Samba 3.0.2a running on Fedora Core 1. This server is set to be Domain PDC and I am looking to have clients attach to it NTLMv2 only. After looking over the man page for smb.conf, I have set the two options that I thought would accomplish: [Global] lanman auth = no ntlm auth = no On the workstation side, I have set HKLM\SYSTEM\CurrentControlSet\Control\Lsa\lmcompatibilitylevel

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

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'

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]

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]

====================================================== "Nothing you wear is more important than your smile." Connie Stevens ====================================================== Release Announcements ===================== This is the first stable release of Samba 4.6. Please read the release notes carefully before upgrading. UPGRADING ========= ID Mapping ---------- We

====================================================== "Nothing you wear is more important than your smile." Connie Stevens ====================================================== Release Announcements ===================== This is the first stable release of Samba 4.6. Please read the release notes carefully before upgrading. UPGRADING ========= ID Mapping ---------- We

Release Announcements ===================== This is the third release candidate of Samba 4.6. This is *not* intended for production environments and is designed for testing purposes only. Please report any defects via the Samba bug reporting system at https://bugzilla.samba.org/. Samba 4.6 will be the next version of the Samba suite. UPGRADING ========= vfs_fruit option

Release Announcements ===================== This is the third release candidate of Samba 4.6. This is *not* intended for production environments and is designed for testing purposes only. Please report any defects via the Samba bug reporting system at https://bugzilla.samba.org/. Samba 4.6 will be the next version of the Samba suite. UPGRADING ========= vfs_fruit option

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

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

I?m not sure if this is related, but there was a regression a while back in handling resource forks in folder icons. It was supposed to be fixed in 4.10.13 but I don?t think it quite works yet and I haven?t had the time to test it further yet. -Perttu > On 30 May 2020, at 21.00, Martin Steiner / 3MF GmbH via samba <samba at lists.samba.org> wrote: > > I changed the configuration

Hi Rowland, Thank you for your feedback. I apologize for not including the global section in my previous message. Here it is: [global] ?? min protocol = SMB3 ?? workgroup = WORKGROUP As you can see, there isn?t much in the global section. To answer your question about the permissions on |/mnt/shared|, here are the settings: drwxrwxr-x 30 john_johnk sharedaccess 4096 Oct 15 23:42 shared

I worked with Netatalk for years and want to switch to Samba now. Currently i use Ubuntu 20.04. and Debian 9 before, i had no issues with netatalk at all. As soon as i try to add a color tag (e.g. yellow) with Mac OS 10.15.5, the tag appears shortly but hides one second later. The file system is ZFS with no special options configured. I tried the Ubuntu package but also the builds from source