similar to: NTLMv2 in Samba 3.0

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

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

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

Chaps, I'm trying to get a radius server to authenticate to AD via the samba ntlm_auth program. I've just built samba vsn 3.0.21c with the following config parameters ./configure --with-pam --enable-socket-wrapper --with-ldapsam --with-syslog --with-ldap --with-winbind My smb.conf has global] workgroup = ADIR security = domain password server = 150.237.54.198 realm =

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

Hello, Two questions for you this evening. How do you tell the difference between NTLMv1-style authentication and NTLMv2 style? The CIFS dialect NT LM 0.12 does both(?), so does not appear in the NegProtRequest message (nor in the flags, near as I could tell). Do you ascertain this by examining the SessionSetupAndX message? If so, what parts? Is it possible to have more than one CIFS

Is it possible to use NTLMv2 with MSCHAPv2 (using ntlm_auth and winbindd). What do I need to put in the smb.conf to make this work. Thanks a lot for any help. Thanks. Shirish. --------------------------------- Yahoo! Mail Use Photomail to share photos without annoying attachments.

On Fri, 2012-04-13 at 19:41 +0000, Chu, Ronald wrote: > hey all. we are running samba 3.5.4 on AIX but when client upgrade to > Win 7.. none of the client on window can see the share drive on AIX. > > the error said "window cannot access "servername" .. i know it is > group policy causing the problem and > > once i took out "computer configuration

I am running samba-2.0.7 on solaris 2.6 in domain mode Windows clients are 98/nt/w2k I was just wondering if 2.0.7 supports NTLMv2 I am asking this because lately some w2k clients are having issues with authentication... how do i check what if when client is requesting SMBnegprot to the server what NTLM version samba server is responding thanks Abdul Javid

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

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

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

Hi, We are having problems setting up a squid cache server to use NTLMv2 authentication to authenticate users against AD. We have narrowed the problems down to being a problem between samba and squid when using NTLMv2. It constantly moans about the password being wrong when using squid, but doing a direct samba auth works fine. We have (believedly) narrowed it down to this: the domain requires

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:

-----BEGIN PGP SIGNED MESSAGE----- Hash: RIPEMD160 What is the progress of NTLMv2 support in samba? I saw a question about this on the list earlier this month, and the answer of "We're working on it." I'm also wondering what still needs to be done? and What can I do to help? Robert Simmons Systems Administrator http://www.wlcg.com/ -----BEGIN PGP SIGNATURE----- Version:

Jeremy, Thanks for this feedback. I will include this info as soon as I get a moment. Good work. - John T. --- John H Terpstra Samba-Team email: jht@samba.org > -------- Original Message -------- > Subject: TOSHARG: Samba ADS domain membership notes > From: "Jeremy Naylor" <jnaylor@gmail.com> > Date: Wed, October 13, 2004 5:27 am > To: jht@samba.org > > Hi

Hello, context: Samba-3.0.2 on a i386 debian-sarge linux, 2.4 kernel. All the windows machine on our network switched today to NTLMv2, and mount.smbfs can't access anymore ressources which are available to smbclient. Exerpt from smb.conf: client NTLMv2 auth = Yes client lanman auth = No client plaintext auth = No The rest being default. Doing smbclient -L server

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