Use the local security settings to force NTLMv2

If the NTLM authentication setting on your Windows computer is not set to NTLMv2, your computer may repeatedly prompt you for your IU username and passphrase when you attempt to access your IU Exchange account via Outlook (or any other desktop email client).

Windows 8.x and later and Windows Server use NTLMv2 authentication by default, but in rare instances, this setting may become incorrect, even if the NTLM setting was previously correct.

You only need to use one of the following methods. Using the Local Security Policy console is easier, but not all versions of Windows include the secpol.msc application necessary to use this method. It is usually found on business-class versions of Windows (for example, Enterprise and Ultimate). The registry option will work on all versions of Windows.

Use the Local Security Policy console
To use the local security settings to force Windows to use NTLMv2:

Open the Local Security Policy console, using one of the following methods:
From the Control Panel: Navigate to the Control Panel. Double-click Administrative Tools, and then Local Security Policy.
Via search: Search for the secpol.msc application and launch it. To do so:
In Windows 10 or Windows Server 2016, use the search function from the Taskbar.
In Windows 8.x or Windows Server 2012, swipe down from the upper right corner, select Search, enter secpol.msc, and press Enter.
The Local Security Policy console will appear.

Find "Network Security: LAN Manager authentication level", which is located in Security Settings,
Local Policies, Security Options.
Set the LAN Manager authentication level to NTLMv2 response only/refuse LM and NTLM.

Also read : lan manager









Comments

Popular posts from this blog

How to Connect a TV to a LAN

Bridging Network importance in cyber operations

How to calculate Network transparency