On 21/07/2019 10:36, Andy Burns wrote:
> Fokke Nauta wrote:
>
>> adding:
>>
>> lanman auth = no
>> ntlm auth = yes
>> client lanman auth = no
>>
>> to my share did not solve it. It's a very stubborn problem and it's
>> related to Windows 10 vsus Linux, I guess.
>
> Did you try the LmCompatibilityLevel registry setting on the client end?
>
>
>
<https://docs.microsoft.com/en-us/windows/security/threat-protection/security-p
olicy-settings/network-security-lan-manager-authentication-level>
>
Thanks,
OK, but:
It says: applies to Windows 10.
When I look at: Policy Location
Computer Configuration\Windows Settings\Security Settings\Local
Policies\Security Options
Sorry, I can't find it.
When I look at:Registry Location
HKLM\System\CurrentControlSet\Control\Lsa\LmCompatibilityLevel
It doesn't exist.
Do I need to create it, and with wat number: 0 to 5 ?
Holy Windows. It's done it again.
--- SoupGate-Win32 v1.05
* Origin: Agency HUB, Dunedin - New Zealand | FidoUsenet Gateway (3:770/3)
|