similar to: Is NTLMv2 auth possible with security = SERVER ?

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

My AD server is Win2003. And my linux server is ubuntu. Samba version is 2:3.6.3-2ubuntu2.12 and 2:4.1.6+dfsg-1ubuntu2.14.04.7. They are join into the Win2003 AD as normal smb servers (not DC). After Win2003 DC autoupdate last week, I can't use smbclient access all samba server with NTLMv2: ~$ smbclient //172.16.3.13/share -U testuser Enter DOMAIN\testuser's password: session setup

​Hello, I compiled Samba 4.8.2 from the git repository to upgrade my existing samba install, however I'm not sure it has gone correctly and I am having a problem authorizing radius clients that previously succeeded using mschapv2 I set the option in smb.conf ntlm auth = mschapv2-and-ntlmv2-only but running testparm gives me an error set_variable_helper(mschapv2-and-ntlmv2-only): value is not

On 17/03/15 10:13, Sense Zeng wrote: > And use ntlm_auth fail too: > > ntlm_auth --username=testuser > password: > NT_STATUS_LOGON_FAILURE: Logon failure (0xc000006d) > > > 2015-03-17 7:30 GMT+00:00 Sense Zeng <opaperjam at gmail.com>: > >> My AD server is Win2003. And my linux server is ubuntu. Samba version is >> 2:3.6.3-2ubuntu2.12 and

I tested NTLMv2 again using the newly created Samba 3.0.2 (I didn't test 3.0.1). It still doesn't seem to work. Has anyone successfully made NTLMv2 work? If so, can I have a working sample of the smb.conf file? I have included below entries in my smb.conf (among other entries): security = server password server = NTDomainController client ntlmv2 auth = yes On both NTDomainController and

Hello, Has anyone successfully configured Samba 3.0 to authenticate using NTLMv2 only? I have below entry in smb.conf: password server = <domain controller> to use domain controller for user authentication and DC is configured with Level 5 - DC refuses LM and NTLM authentication (accepts only NTLMv2). So far I got: "System error 1326 has occurred. Logon failure: unknown user name or

Hello: As many of you already probably know, the neon library is the workhorse for davfs support. However, right now, the current version of libneon has very limited support for NTLM, particularly NTLMv2, both on the challenge/authentication side as well as handling NTLMv2 Session Security. There is a patch somewhere to add NTLMv2 authentication support natively but there is zero support for

Hi Thanks in advance. I know my question below is not really related with samba but I'm really confused, and you guys are expert on windows authentication, I really hope you have patience to read this and I'll appreciate any of your help. I learned a lot from this post http://lists.samba.org/archive/jcifs/2008-October/008227.html. I know that a "man in the middle" technique,

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

All, I need to force XP clients to use NTLMv2 when mapping to samba 3.6.12. My config is: ntlm auth = No client NTLMv2 auth = Yes client lanman auth = No client plaintext auth = No lanman auth = No XP systems can still map shares with the above config. If I add: max protocol = SMB2 min protocol = SMB2 W7 systems map shares, XP systems cannot map shares even if I change LAN Manager

Is there a way to make rpcclient support ntlmv2? When I configure my server to only accept ntlmv2 logins, my rpcclient stops working. I tried the approach needed to make TNG's rpcclient use ntlmv2 (a line like "client ntlmv2 = auto" in smb.conf), but it didn't work. Thanks, Dave __________________________________________________ Do You Yahoo!? Yahoo! - Official partner of 2002

Hi folks, I've been testing out Windows Vista Enterprise today. It defaults to only using NTLMV2 authentication. I'm testing with Samba 3.0.23d running on Sparc/Solaris 8. Samba is configured with security = domain The password server is a Windows Server 2003 domain controller. I've joined Samba to the domain. I simply can't get Vista to connect unless I change its security

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

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

Hello, I'm having some issues with getting NTLMv2 authentication working, and I thought you might be able to help. I've got a Windows XP Pro client machine trying to access shares on a domain member server running Samba. (Both the domain member server and the PDC are running Samba 3.0.4.) The XP machine is by default configured to use NTLMv2 for authentication, but that fails when

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

I have samba 3.0.14-5 installed (installed via Fedora Core 4's Yum) I have enabled "client NTLMv2 auth = yes" in smb.conf When I run "ntlm_auth --username=user --domain=MYDOM" it connects fine (change user and MYDOM to be my user and my domain) When I run "ntlm_auth --username=user --domain=MYDOM --diagnostics" it fails on all tests with "wrong password"

I have an interesting situation. I'm not sure if Samba doesn't support this, or if I have something setup wrong. All Linux/BSD machines: Samba 3.0.10 Windows XP cannot connect to a Samba Server when the Samba server is a member of a Samba Domain, and authentication is restricted to NTLMv2 _IF_ The Windows XP machine has the following Security Policy turned on: Network security:

I've seen various notes on this subject, but can't find a definitive answer. Does rpcclient support NTLMv2 authentication ? i.e if the AD server is setup to send NTLMv2 responses only (and reject LM and NTLM) can I still connect with rpcclient ? thanks for any info or pointers