similar to: Forcing clients to use NTLMv2 in 3.6.12

Hello, i got some clients (WINDOWS7 and WINDOWS10) to connect to samba shares. OS is openSUSE 12.2; 13.1; 42.1 Samba-Version: 3.6.7; 4.1.22; 4.2.4 smb.conf is shown below. The samba setup is a workgroup setup, the W7-clients are set up to the workgroup 'workgroup'. No further changes are made to the W7-clients. samba setup: groupadd workgroup chgrp -R workgroup /srv/samba chmod -R 770

Only looking for file server solution. export LIBPATH=/opt/samba/lib /opt/samba/sbin/smbd ?D cat smb.conf [global] security = ads password server = * workgroup = ABC.NET username map = /etc/opt/samba/users.map encrypt passwords = yes client ntlmv2 auth = yes client lanman auth = no client plaintext auth = no lanman auth = no ntlm auth = no server signing = auto max protocol = SMB2 ;Enter

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

Here is the problem: I'm setting up a new squid proxy server with authentication via Samba and NTLM because the old one died suddenly. The new one is up and running and i have it working; mostly. The kicker is the 2 employees testing Vista (myself and my supervisor) could not authenticate against the server. I say could because through a variety of testing and some lucky reading I found the

updated smb.conf, still same error. details below. # cat /etc/samba/smb.conf [global] workgroup = NAMDEV realm = NAMDEV.NSROOTDEV.NET <http://namdev.nsrootdev.net/> client ldap sasl wrapping = seal ;username map = /etc/opt/samba/users.map encrypt passwords = yes client ntlmv2 auth = yes client lanman auth = no client plaintext auth = no lanman auth = no ntlm auth

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

> On 10/02/17 17:16, ToddAndMargo via samba wrote: >> Hi All, >> >> Server: >>    Fedora 26 >>    samba-4.6.8-0.fc26.x86_64 >> >> Workstations (5 of them): >>    XP Pro SP3 >> >> >> I set all five of my customer XP workstations to >> >> Send NTLMv2 response only\\refuse LM and NTLM >> >> and turned off

Hi, Sorry for my english. I configured Samba as DC and when I use win 10, everything is ok, but win xp dosn't attach disks. When I browse \\dc.gryko.org.local, xp can see disks, but dosn't attach them while logging in. Win 10 does. My smb.conf: # Global parameters [global] netbios name = SAMBA realm = GRYKO.ORG.LOCAL server services = s3fs, rpc, nbt, wrepl, ldap,

Is that with an active directory domain controller? On Apr 3, 2016 11:21 PM, "barış tombul" <bbtombul at gmail.com> wrote: > my conf win10 no problem: > client NTLMv2 auth = Yes > client lanman auth = No > server max protocol = SMB3_11 > server min protocol = LANMAN1 > client max protocol = SMB3_11 > client min protocol = CORE > >

Dear Samba Users, I set a samba share (4.8.1) on a linux (centos 7) as server member ; authentication is done against a AD win 2012 R2 server through winbind. I thought authentication was using kerberos, but I checked log and found : Auth: [SMB2,(null)] user [MYDOMAIN]\[mydomainuser] at [mar., 11 juin 2019 10:21:42.000927 -03] with [NTLMv2] status [NT_STATUS_OK] workstation [CANONDCE0BD]

I am encountering a problem after upgrading Samba 3.x to Samba 4.6.4 on AIX. When trying to update a file in Excel 2016 from Windows 10 clients, Excel gives an error trying to save the file with an Access Denied message. I first thought it was a locking option and tried many variations of those, but what I have found is that if the file's access mode is 700 (User:RWX, Group:none,

Hi all, I sometime have a strange behavior when using MS Office and saving files. First things first: - OS CentOS 6.7 x86_64 - SAMBA version 3.6.23, configured as member server (see [1] for full configuration) - inotifywait watching my shares to replicate them off-site - about 100 W7/W8 clients with MS Office 2010 Using inotifywait, I tracked how MS Office file save function works. Basically,

Hello :-), I have some problem with the cifs client of linux. I can't mount a volume from a Windows 7 machine with NTLMv2 authentication. e.g. # mount -t cifs //win7-box/C\$ mount-point --verbose -o sec=ntlmv2,credentials=smb-passwd mount error(22): Invalid argument Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) #dmesg | tail Status code returned 0xc000000d

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]

Hi all. Just looking for some guidance as to what works, and what doesn't. Recently I've noticed that no matter what I do, I can't seem to get NTLMv2 to negotiate using Windows Vista, Windows 7 or Mac OS X 10.6.x against Solaris 10 Samba 3.0.37. If I 'tune' the client OS that it only negotiates with NTLMv1, all is well. In my global block, on the Solaris Samba server, I

Am 2017-11-11 um 13:36 schrieb Rowland Penny: > As far as I am aware, 'net use' sends the password unencrypted, so if > someone is trying to 'sniff' the password, they will get it, but then > if the password is stored in the bat file unencrypted and anybody can > read the bat file, they wont need to 'sniff' the password. Yes, we know ;-) The thin client with

Hello, I am trying to figure out how the different values for "max protocol" and "min protocol" (as seen in the smb.conf man page under the "max protocol" section) correlate to the Microsoft jargon for the different logon protocols. Here is what I've determined. Could some please verify this for me? Samba Microsoft CORE

Hi All, Server: Fedora 26 samba-4.6.8-0.fc26.x86_64 Workstations (5 of them): XP Pro SP3 I set all five of my customer XP workstations to Send NTLMv2 response only\\refuse LM and NTLM and turned off (smb.conf) lanman auth = yes ntlm auth = yes And had to turn it right back on as the customer's Xerox Workcentre 3550 multifunction printer scanner requires it What are

I cannot connect as guest from Win10 to Samba anymore, since I removed "server max protocol = NT1" net use \\%IP%\testshare /user:"" "" /persistent:no System error 58 has occurred. The specified server cannot perform the requested operation. It works when I supply a userid and password. It works from Win7. It fails only in the combination Win10, SMB3,

Hi list. I've been running up against a bunch of ntlm v2 related issues recently with Windows 7 and Mac OS X 10.6 client systems attempting to connect to my Solaris 10 samba 3.0.37 server. As it turns out, Sun engineering suggest that because I use "security = SERVER" rather than "security = DOMAIN", ntlmv2 auth will never actually work, even if I have settings such as: