Acopia Networks 810-0044-00 Manual de instalación descargar pdf (Pagina 146)

100

101

Configuring a Namespace

Configuring Windows Authentication (CIFS)

7-18 CLI Storage-Management Guide

Removing an NTLM-Authentication Server

From gbl-ns mode, use no ntlm-auth-server to remove a server from the namespace:

no ntlm-auth-server name

where name identifies the NTLM authentication server to remove from the

namespace.

For example, this command set removes the “asa-test” authentication server from the

“medarcv” namespace:

bstnA6k(gbl)# namespace medarcv

bstnA6k(gbl-ns[medarcv])# no ntlm-auth-server asa-test

bstnA6k(gbl-ns[medarcv])# ...

Opening Windows-Management Access (optional, MMC)

You can configure a group of Windows clients to have management authorization in

this namespace, typically through the Microsoft Management Console (MMC). These

clients can use MMC to make CIFS shares, open files, and/or any open CIFS-client

sessions. You configure this group of clients and their permissions ahead of time, as

described in “Authorizing Windows-Management (MMC) Access” on page 3-28.

Each namespace can allow multiple management-authorization groups. From gbl-ns

mode, use the

windows-mgmt-auth command to apply one such group to the

namespace:

windows-mgmt-auth name

where name (1-64 characters) identifies one management-authorization group

for this namespace. Use the

show windows-mgmt-auth command for a list of all

configured management-authorization groups.

If you remove an NTLM-authentication server from the namespace, the server’s clients

will no longer be able to authenticate through NTLM. This may even pose a problem for

Kerberos clients who occasionally fall back to NTLM authentication.

While the namespace is enabled, you cannot remove the final NTLM-authentication

server.

1 2 ... 141 142 143 144 145 146 147 148 149 150 151 ... 491 492

Comentarios a estos manuales

Sin comentarios

Acopia Networks 810-0044-00 Manual de instalación Pagina 146

Comentarios a estos manuales