similar to: Vista, NTLMV2, security = domain

I'm working on trying to get Samba 3.0.23c to work with Vista and I've run into a snag. If a share is set up for security = share, and protected with a password, when I try to mount the share using Start->Run->\\server\share, the password is rejected by Samba for about the first 10 seconds, but after that, it lets me in. I've tried all the common suggestions such as changing

Sparc Solaris / UFS file system. I have some ACL's set up for a handful of users and its all worked flawlessly with every incarnation of Samba I've used over the past couple years, which would be most. Last Friday evening I upgraded from 3.0.11 to 3.0.13 and some of the users I have some ACL's set up for promptly found Monday that they couldn't save new Excel files, they'd be

More precisely what I've discovered is, at least in the cases of 2.2.8a and 3.0alpha22, when a 64-bit Samba is built with Sun's Forte compiler you'll end up with something incompatible with Mac OS 10.2.3. I always compile Samba myself with Sun's compiler to produce a 64-bit Samba. Well yesterday it came to my attention that Mac OS 10.2.x doesn't work with whats on my main

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

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

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, We have samba 3.0.23 installed. We are using free radius to take authentication requests from a nortel vpn server and using ntlm_auth trying to authenticate users against AD. This setup works fine when on the AD side ntlmv1 and ntlmv2 are enabled. (IE. Users can authenticate). However, when only ntlmv2 is enabled users are unable to authenticate. I have searched various places and while

Samba is a domain member server authenticating to a MS-Windows domain controller. With 3.0.7 and all previous version for the past few years I could map a Windows to Unix userid in the username map file like so.. fred = fredw His home directory was then accessible as \\servername\fredw so \\servername\%username% from a Windows NTx client. I make EXTENSIVE use of that functionality. I missed

Good morning, I have a working Offline Files setup w/Samba 3.0.24 (FreeBSD 6.2 host OS) and a Win XP SP2 client. Upon updating to Samba 3.0.25, the XP client's offline cache would show (as viewed via the Offline Files Folder) that synced files are write-only ('User W' in the Access column). When offline, theses files appeared to be available via Explorer and double clicking would

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

I'm having trouble with files being marked read-only in Windows because the Solaris file owner does not have write-permissions on the file; group-write is allowed: -r--rw---- 1 user group 32 Feb 13 14:19 testfile.txt I thought that setting "store dos attributes = yes" for this share would allow the "read only" setting to be stored in extended attributes, but it

We've recently migrated my entire University including faculty and staff from Novell to Samba. There's typically 700+ clients connected to the samba server at any given time and thus far there are about 400GB of client's files on the server. Basically every Microsoft Windows user generated file (Word, Excel, whatever) of the entire University gets stored on my Samba server. Obviously

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

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

I use a lot of "force user" and "force group" directives on various shares. With smbstatus of Samba 2 I could always verify with a glance what uid and gid a particular service is being accessed as, with Samba 3 you can't. I'd REALLY like to see that come back to smbstatus. Here's a real world example of my complaint... Samba 2 smbstatus output... Samba version

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