similar to: How to Disable LM Authentication on Windows NT

The issue of disconnected networkshares (shares offered on an NT server) has appeared on this mailinglist a few times. It is not a samba issue, but it seems many here might benefit from the information given below anyways, as I've never seen a solution to the problem come by. Problem: Whenever there has not been any activity (file/network IO) to or from a networkshare that is offered by an

On 25/06/2020 16:56, Greg Marshall via samba wrote: > Hello experts/users, > > We have a samba server in ubuntu 18.04 LTS with version. > > apt-cache policy samba > samba: > Installed: 2:4.7.6+dfsg~ubuntu-0ubuntu2.16 > Candidate: 2:4.7.6+dfsg~ubuntu-0ubuntu2.16 > > All is fine and great. Except one (internet disabled) windows 7 > professional PC (sorry we

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

On Tue Feb 17 11:14:15 GMT 2004, Andrew Bartlett wrote: >> Any suggestions for things to try (or even a guaranteed solution ;-) ) would >> be very much appreciated. >> server signing = no >Try this as yes. How did you get it work? I've tried the "server signing = yes or auto", but it didn't work. Could you kindly tell us how to set the XP to get it

Am 09.06.2017 um 19:55 schrieb Rowland Penny via samba: >> Can anybody please help me, even by simply giving me some hints to >> point me in the right direction to do a deeper investigation? >> >> Thank you very, very much in advance, >> best regards > > Try adding 'ntlm auth = yes' to smb.conf and restart Samba. > It was changed from 'yes'

Thanks Andrew for the answer. But even if I enable Windows XP to use NTLMv2 (using Regedit on (HKEY_LOCAL_MACHINE/SYSTEM/CURRENTCONTROLSET/CONTROL/LSA LMCOMPATIBILITYLEVEL to 5) and adding "ntlm auth = ntlmv1-permitted" to my smb.conf Still the same error. (No *more connections can* be *made* to this remote computer at this time) in versions higher than 4.10. Any ideas? Best Regards

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

when an nt 4.0 workstation or backup domain controller is joined to a domain, the trust account password is set to a well-known initial value. if you are concerned about internal network security, this is not really an acceptable risk: any captured network traffic can be decoded simply from knowing the name of the workstation, which is contained in the network traffic itself. the initial value

Hi all, I repost the message about the signatur because I've not had any response. This time I hopefuly to get some ideas. When we put the parameter "server signing = auto or Yes" in smb.conf, the Windows XP clients can no longer connect to the samba (3.0.2), the "net use \\server\ipc$ /u:user password" return error 64. If I disabled the "server signing" the

I've been having these really annoying issues ever since I started to configure SAMBA with Windows XP. As it seems the XP-machine detects the SAMBA-share on occasions, and even manages to connect to it; but only for a while. I have found no clue whatsoever why it connects only "sometimes". It seems that when the Windows XP machine is just booted, it normally gets access to the

Hello all, I guess that everyone knows the message "the trust relation between this workstation and the primary domain failed" when joining Win7 into samba domain. Unfortunately, the same problem appeared few hours/days after the machine was successfully joined in the domain(with reg keys from https://wiki.samba.org/index.php/Windows7) and user able to use it for awhile. Then at

Hi all, In my win2k ADS server(mixed mode), I have set the LAN Manager authentication level to Send NTLMv2 response only\refuse LM & NTLM. In the registry, i also set HKLM\System\CurrentControlSet\Control\Lsa|lmcompatibilitylevel --> level 5 (accepts only NTLMv2). Similarly, i also set HKLM\System\CurrentControlSet\Control\Lsa\MSV1_0\NtlmMinClientSec --> 0x00080000(NTLMv2 Session

On Mon, 31 Oct 2016 23:36:16 +0530 Pradeep Rawat <pradeeprawat85 at gmail.com> wrote: > Tried that, same error. > > Enter adminuser's password: > Failed to join domain: failed to lookup DC info for domain > 'MYDOMAIN.COM' over rpc:Logon failure > > On Mon, Oct 31, 2016 at 11:25 PM, Rowland Penny <rpenny at samba.org> > wrote: > > > On

Hi, I'm running Samba 3.5.6 with OpenLDAP 2.4.23 (from Debian Squeeze) as PDC. Everything is working fine (Joining Domains, Log on Users) but I'm not able to Log in as Domain Admin. If I try to, the message "Unable to log on ?The User Profile Service service failed the logon. User profile cannot be loaded." (in german: "Fehler bei der Anmeldung mit dem

Hi All, I am having an issue with Samba joining an active directory domain. When I run 'net ads join -S mydomaincontrollerFQDN -U adminuser command I get this error: Failed to join domain: failed to lookup DC info for domain 'MYDOMAIN.COM' over rpc: Logon failure The credentials we entered are for sure correct but if we see our domain controller it count it

Hy possible that it is a setting in the registry. See ftp://ftp.microsoft.com/bussys/winnt/winnt-docs/papers/ I'can't connect to the link (ftp is blockt at our site) but you houl'd see some information. if blockspace from your ehternetcard is less then 9.6 microseconds, you can run in problems. hope you'll find something cheers peter >>-----Urspr?ngliche Nachricht-----

> Date: Mon, 27 Apr 1998 18:00:15 +0100 > From: "Robert Koruna" <robert.koruna@tiwag.co.at> > To: samba@samba.anu.edu.au > Subject: DOS-Client using SAMBA-Server > Message-ID: <199804271600.SAA22065@mail.tiwag.co.at> > > Hello, > > I read some of your latest articles depending on DOS and Samba. > You always mentioned TCP/IP 32,

You could always run this as a service using Microsoft's tools from the NT 3.5 Resource Kit. The two tools you need are srvany.exe and instsrv.exe. I've used this many times on Win2k with no problems. You can download the resource kit from Microsoft here: ftp://ftp.microsoft.com/bussys/winnt/winnt-public/reskit/nt35/i386/i386.exe And there is an article about how to set it up here:

Hi Rowland, Thank you very much, you were spot on. I had changed the Windows 7 client to LM compatibility level, and now that I reverted it back to 5 (use NTLMv2) it works. It was this registry key that made it start working: [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa] "LmCompatibilityLevel"=dword:00000005 I was ignoring the old LM options and the "NTLMv1" in