similar to: NTLMv2 passthrough auth fails on XP

I have upgraded to version 3.0.27a on ubuntu 7.10 server and now the getent command wont display the active directory users, but wbinfo will. It worked fine with 3.0.26a and I have not changed my configuration. I do however have this in my winbind log: [2007/12/04 13:39:01, 0] nsswitch/winbindd.c:request_len_recv(544) request_len_recv: Invalid request size received: 2084 (expected

I have two subnets in may LAN 192.168.0.0/24 and 192.168.1.0/24. Both subnets go out to the Internet through a Linux box acting as a gateway, so the gateway has one interface in each subnet (192.168.1.1 and 192.168.0.1). In both subnets I have Windows and Linux machines and I want to configure SMB networking using a workgroup (not a domain), so one workgroup for more than one subnet. I know that

My Question: ------------ Is it possible to get 2-way Interdomain Trust relationships working between a Samba domain and an NT4 SP6a domain, while restricting all password hashes to NTLMv2 only? Everything works except the inter-domain trust I'm able to get the NT4 domain to trust the Samba domain, but not the other way around. My System: ---------- I have a perfectly running Samba domain

I am running a Samba server version 3.0.23d on AIX and I am trying to figure out how to rotate the Samba logs daily. I know the logfile can be rotated based on size but how can I make it rotate daily without the size parameter? Any help would be greatly appreciated. Thanks, Maurice Forte

Can anyone suggest any apps/scripts for bulk generating passwords from real names (e.g. jsmith from John Smith) that would check for duplicated in an existing smbpasswd or passwd file and append a number to the username (e.g. jsmith1, jsmith2). Thanks Lee Baker MEng MIEE Music Technology Coordinator Email: <mailto:lbaker@mcauley.org.uk> lbaker@mcauley.org.uk

The subject says it all, I think. At home I have a PDC (Linux with Samba), and I have Win98 and Win 95(!) clients. And sometimes the domain name (workgroup name) is visble in the Network neigborhood, and sometimes it is not. I also got the impression that placing a link in the file NETHOOD makes a difference, but I am not sure yet. The PDC is visible, that is, it can be PINGed, I can connect

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

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

On Wed, Apr 19, 2017 at 11:03:34AM -0400, pisymbol . via samba wrote: > 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

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

Hi,d When trying ntlm auth = no on one of my samba servers it broke all my monitoring because smbclient failed to negotiate. After troubleshooting I found that it was not trying ntlmv2 as it should so I set client ntlmv2 auth = yes and then retried. It worked. However, other samba servers failed to connect (notably those using share level security) as it wanted lanman auth. So I set

Hello, everyone, I'm trying to mount a CIFS share served by Samba using mount.cifs with NTLMv2 authentication. According to 'man mount.cifs' the option "sec=ntlmv2" should be supported, but it keeps giving me "mount error(22): Invalid argument". The Samba server enforces the use of NTLMv2. When allowing for NTLMv1 on both sides everything works just fine. The

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.

Hello :-), I have some problem with the cifs client of linux. I can't mount a volume from a win7 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

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