
116
The
Network security: LAN Manager authentication level
security option setting determines which
challenge/response authentication protocol is used for network logons. This choice affects the level of
authentication protocol used by clients, the level of security negotiated, and the level of authentication
accepted by servers as follows. The following numbers in parentheses below are the actual settings
for the
LMCompatibilityLevel
registry value. This setting should be configured to the highest level that
the company network environment allows according to the following guidelines:
Network security: Minimum session security for NTLM SSP based (including secure RPC) clients
Member Server Default
Legacy Client
Enterprise Client
High Security Client
No minimum
No minimum
Enabled all settings
Enabled all settings
Important:
Administrators within multi-protocol heterogeneous environments may want to verify all
applications and protocol communications are working properly within their NAS box, and other
servers within the network, once this setting is set.
The
Network security: Minimum session security for NTLM SSP based (including secure RPC) clients
security option setting allows a client to require the negotiation of message confidentiality
(encryption), message signing, 128-bit encryption, or NTLM version 2 (NTLMv2) session security.
Configure this setting as high as possible while still allowing the applications on the network to
function fully to ensure that network traffic from NTLM SSP based servers is protected from man-in-the-
middle attacks and data exposure.
Network security: Minimum session security for NTLM SSP based (including secure RPC) servers
Member Server Default
Legacy Client
Enterprise Client
High Security Client
No minimum
No minimum
Enabled all settings
Enabled all settings
Important:
Administrators within multi-protocol heterogeneous environments may want to verify all
applications and protocol communications are working properly within their NAS box, and other
servers within the network, once this setting is set.
The
Network security: Minimum session security for NTLM SSP based (including secure RPC) servers
security option setting allows a server to require the negotiation of message confidentiality
(encryption), message integrity, 128-bit encryption, or NTLMv2 session security. Configure this setting
as high as possible while still allowing the applications on the network to function fully to ensure that
network traffic from NTLM SSP based clients is protected from man-in-the-middle attacks and data
exposure.
System objects: Require case insensitivity for non-Windows subsystems
Member Server Default
Legacy Client
Enterprise Client
High Security Client
Enabled Enabled Enabled Enabled
Important:
Administrators within multi-protocol heterogeneous environments, especially within Unix
and Linux, may want to set this setting to
Disabled
for the NAS and server systems.
The
System objects: Require case insensitivity for non-Windows subsystems
security option setting
determines whether case insensitivity is enforced for all subsystems. The Microsoft Win32® subsystem
is case insensitive. However, the kernel supports case sensitivity for other subsystems, such as the
Portable Operating System Interface for UNIX (POSIX). Since Windows is case insensitive (but the
POSIX subsystem will support case sensitivity), not enforcing this setting makes it possible for a user of
this subsystem to create a file with the same name as another file by using mixed case to label it.
Doing this may block another user accessing these files with normal Win32 tools, because only one
of the files will be available. To ensure consistency of file names, this setting is set to
Enabled
in the
three environments defined in this guide.