search for: msv1_0

...he request from user NT Authority/System comes 3 times and the user is locked. this is the first entry: user: NT AUTHORITY/SYSTEM Logon Failure: Reason: Unknown user name or bad password User Name: HOERIG Domain: LANGROUP Logon Type: 3 Logon Process: NTLanMan Authentication Package: msv1_0 Workstation Name: \\UTAH2 and this the second: user: hoerig Successful Logon: User Name: HOERIG Domain: LANGROUP Logon ID: 1020 Logon Type: 3 Logon Process: NTLanMan Authentication Package: msv1_0 Workstation Name: \\UTAH2 Has anybody an idea?? thanx Eckhard ----------------...

...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 security) HKLM\System\CurrentControlSet\Control\Lsa\MSV1_0\NtlmMinServerSec --> 0x00080000(NTLMv2 Session security) In my smb.conf, I added client NTLMv2 auth = yes lanman auth = no ntlm auth = no I have waited for about 5 minutes just to be sur...

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

...uot;The password is incorrect". The Win95 client authenicates against a 2000 server. The pertinent regisrty settings look like: [HKEY_LOCAL_MACHINE\System\CurrentControlSet\control\LSA] "LMCompatibility"=dword:00000003 [HKEY_LOCAL_MACHINE\System\CurrentControlSet\control\LSA\MSV1_0] "NtlmMinClientSec"=dword:00080000 I've verified the Secur32.dll on the Win95 is the 128-bit version, and that Winsock 2.0 update and DUN 1.3 are installed. If I use "security = domain" and use "password server = *" the users authenicate fine, but I'd rath...

...anManWorkstation\Parameters] "DNSNameResolutionRequired"=dword:00000000 "DomainCompatibilityMode"=dword:00000001 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa] "LmCompatibilityLevel"=dword:00000001 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\MSV1_0] "NtlmMinServerSec"=dword:00000000 "NtlmMinClientSec"=dword:00000000 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NTDS\Parameters] "LDAPServerIntegrity"=dword:00000001 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters] "RestrictN...

...algorithm) type against *AcceptedKeyTypes. bz#2746 * ssh(1): Request correct signature types from ssh-agent when certificate keys and RSA-SHA2 signatures are in use. Portability ----------- * sshd(8): On Cygwin, run as SYSTEM where possible, using S4U for token creation if it supports MsV1_0 S4U Logon. * sshd(8): On Cygwin, use custom user/group matching code that respects the OS' behaviour of case-insensitive matching. * sshd(8): Don't set $MAIL if UsePAM=yes as PAM typically specifies the user environment if it's enabled; bz#2937 * sshd(8) Cygwin: Change servi...

...algorithm) type against *AcceptedKeyTypes. bz#2746 * ssh(1): Request correct signature types from ssh-agent when certificate keys and RSA-SHA2 signatures are in use. Portability ----------- * sshd(8): On Cygwin, run as SYSTEM where possible, using S4U for token creation if it supports MsV1_0 S4U Logon. * sshd(8): On Cygwin, use custom user/group matching code that respects the OS' behaviour of case-insensitive matching. * sshd(8): Don't set $MAIL if UsePAM=yes as PAM typically specifies the user environment if it's enabled; bz#2937 * sshd(8) Cygwin: Change servi...