The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This chapter describes how to configure Windows NT servers used in AAA and includes the following sections:
The ASA supports Microsoft Windows server operating systems that support NTLM Version 1, collectively referred to as NT servers.
Note Windows NT servers have a maximum length of 14 characters for user passwords. Longer passwords are truncated, which is a limitation of NTLM Version 1.
|
|
---|---|
This section includes the guidelines and limitations for this feature.
Supported in single and multiple context mode.
Supported in routed and transparent firewall mode.
This section includes the following topics:
Step 1 Add a AAA server group. See Configuring Windows NT Server Groups.
Step 2 For a server group, add a server to the group. See Adding a Windows NT Server to a Group.
If you want to use a Windows NT server for authentication, authorization, or accounting, you must first create at least one Windows NT server group and add one or more servers to each group. You identify Windows NT server groups by name.
To add a Windows NT server group, perform the following steps:
Step 1 Choose Configuration > Device Management > Users/AAA > AAA Server Groups.
Step 2 In the AAA Server Groups area, click Add.
The Add AAA Server Group dialog box appears.
Step 3 In the Server Group field, enter a name for the group.
Step 4 From the Protocol drop-down list, choose the NT Domain server type.
Note A warning message appears, indicating that support for NT Domain server authentication will be removed in an upcoming major release.
Step 5 In the Reactivation Mode field, click Depletion or Timed.
In Depletion mode, failed servers are reactivated only after all of the servers in the group are inactive.
In Timed mode, failed servers are reactivated after 30 seconds of down time.
Step 6 If you chose the Depletion reactivation mode, enter a time interval in the Dead Time field.
The Dead Time is the duration of time, in minutes, that elapses between the disabling of the last server in a group and the subsequent re-enabling of all servers.
Step 7 In the Max Failed Attempts field, add the number of failed attempts allowed.
This option sets the number of failed connection attempts allowed before declaring a nonresponsive server to be inactive.
The Add AAA Server Group dialog box closes, and the new server group is added to the AAA Server Groups table.
Step 9 In the AAA Server Groups dialog box, click Apply to save the changes to the running configuration.
To add a Windows NT server to a group, perform the following steps:
Step 1 Choose Configuration > Device Management > Users/AAA > AAA Server Groups, and in the AAA Server Groups area, click the server group to which you want to add a server.
The row is highlighted in the table.
Step 2 In the Servers in the Selected Group area (lower pane), click Add.
The Add AAA Server Group dialog box appears for the server group.
Step 3 From the Interface Name drop-down list, choose the interface name on which the authentication server resides.
Step 4 In the Server Name or IP Address field, add either a server name or IP address for the server that you are adding to the group.
Step 5 In the Timeout field, either add a timeout value or keep the default. The timeout is the duration of time, in seconds, that the ASA waits for a response from the primary server before sending the request to the backup server.
Step 6 Specify the server port. The server port is either port number 139, or the TCP port number used by the ASA to communicate with the Windows NT server.
Step 7 Specify the name of the domain controller. The domain controller is the hostname (no more than 15 characters) of the NT Primary Domain Controller for this server (for example, PDC01). You must enter a name, and it must be the correct hostname for the server whose IP address you added in the Authentication Server Address field. If the name is incorrect, authentication fails.
The Add AAA Server Group dialog box closes, and the AAA server is added to the AAA server group.
Step 9 In the AAA Server Groups pane, click Apply to save the changes to the running configuration.
To determine whether the ASA can contact a Windows NT server and authenticate or authorize a user, perform the following steps:
Step 1 Choose Configuration > Device Management > Users/AAA > AAA Server Groups, and in the AAA Server Groups area, click the server group in which the server resides.
The row is highlighted in the table.
Step 2 From the Servers in the Selected Group table, click the server that you want to test.
The row is highlighted in the table.
The Test AAA Server dialog box appears for the selected server.
Step 4 Click the type of test that you want to perform— Authentication or Authorization.
Step 5 In the Username field, enter a username.
Step 6 If you are testing authentication, in the Password field, enter the password for the username.
The ASA sends an authentication or authorization test message to the server. If the test fails, ASDM displays an error message.
To monitor Windows NT servers, see the following panes:
|
|
Table 38-1 lists each feature change and the platform release in which it was implemented. ASDM is backwards-compatible with multiple platform releases, so the specific ASDM release in which support was added is not listed.