Tripp Lite B070-016-19-IP Web Configuration Interface, In the Account Blocking section

2..Web Configuration Interface

2.In the Account Blocking section:

•In the Block after field, enter in the number of unsuccessful login attempts that will be allowed in a given time period. This time period is set in the attempts within (hr:min) field. Enter into this field the time in hours and minutes.

•In the Block account field, you can select the length of time that an account will be blocked for if it exceeds the number of unsuccessful login attempts.

•Check the for period (hr:min) checkbox to block the account for a specified period of time. This time period is set in the hours and minutes fields to the right of the for period (hr:min) checkbox.

•Check the forever checkbox to block the account indefinitely.

3.In the Password Policy section:

•Select the High security password policy checkbox to enable the high security password policy, or leave it unchecked to enable the standard security policy to apply. Both security policies prohibit the use of the username being included in the password, and have a maximum character limit of 10. The standard security policy requires only that the password contain at least six characters. The high security policy requires that the password contain at least eight characters, and that it contain one number, one upper-case letter, and one of the following special characters: !, @, #, $, %, ^, *, (), _, -, +, =, [], ’, :, ;, ?, /, or {}

•Check the Enable OSD password checkbox to require that a username and password be entered for local user access to the OSD. By default, a password is not required to access the KVM via the local console. Accounts created in the Web Configuration Interface are used for both local and remote access.

4.There is only one field in the Idle Timeout portion of the Security page: Disconnect after. In this field, select the amount of time that an account can be idle before it is automatically disconnected from the system. Select No Timeout to disable this feature.

5.The Serial Terminal Policy portion of the Security page allows you to enable access to the connected serial devices via your own SSH client (e.g. PuTTY, SecureCRT, etc.). By default, this is disabled, so that an account must open the Web Configuration Interface and double-click on the serial ports in the My Targets screen list to access them via the NetCommander IP’s internal SSH client. To enable direct SSH connection, check the Enable direct SSH connection checkbox and enter in the desired TCP port numbers for serial ports 1 and 2 (by default, these are set to 4001 and 4002). You can then access the connected serial devices using your own SSH client by providing 1) the IP address of the NetCommander IP, 2) the TCP port number for the desired serial device, and 3) your KVM username and password.

6.After changing any settings in the Security page, click the Save button at the top of the page to save your changes.

7.Upon clicking Save, you will be prompted to reboot the KVM to finish implementation of the new Security settings. Click Yes to proceed.

29