similar to: Proposal to change security=share in Samba 4.0

The thing is, on the same machine, same net same moment, when I load the same folder from windows XP (through parallels) it takes like 10sec while samba 10min!!! MTU is 1500, set to match 100T devices like router and NAS on the LAN. Even on crossover cable it freaks out the same way. Btw my NAS is a Lacie Ethernet drive with linux based firmware and samba. Funny enough I load folders (ie

Vista32 3.0.25pre2 (I understand vista patches for "share level" are already in) security = share (with "valid users" on share definition) host msdfs = no user/pass in smbpasswd file. If I use "connect network drive..." method with "connect as another user", then it will always work. If I use start, search , \\server\share and then type user/pass in

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, We support an older version SMB1 server (propietary implementation) which does not support extended security . Mapping a share from that server, using smbclient, was working before applying badlock patches (to the smbclient) , with default settings in smb.conf. However, after applying badlock patches, smbclient fails to map with default settings. When I set the option : "client ntlmv2

I noticed when CentOS 6 came out that RHEL had moved to postfix vice sendmail as the default MTA. I had never heard the rationale given, it always sat on the back burner, but I was reminded of the question the other day when I was dealing with a related topic. I don't want to get into a pissing contest about how one MTA is obviously better than the other, nor why others think that I should

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

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

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,

On Thu, 21 Sep 2017 12:40:57 -0400 lingpanda101 via samba <samba at lists.samba.org> wrote: > > > I'm not understanding the change to 'ntlm auth' parameter. It's says > default is now ntlmv2-only as a value.  So this takes the place of > 'ntlm auth = no'(ie. ntlm auth = ntlmv2-only)? Using the value of > 'yes' is OK(ie. ntlm auth = yes)? 

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

Hi, all. I've got an old Telrad PBX with an Emagen(?) voicemail box. The VM box, itself, is beginning to show its age. Big-time. We're thinking it might be time to look for a replacement. I'd love to install Asterisk with an FXO card or something, but I don't think it supports whatever protocol legacy PBX's used to speak to VM systems. If someone can tell me I'm

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

Samba 3.6.5 client does not train down to plain NTLM if there is no "client ntlmv2 auth = no" statement in the smb.conf file. If the server is configured for just plain NTLM (not NTLMv2), the client will receive a login error, without the smb.conf statement. I know that smbclient 3.6.5 defaults to "client ntlmv2 auth = yes", but the lack of it should be able to login as just

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