Tectia Server uses a distributed architecture where the master server process launches several servant processes that handle the actual client connections. The server's total number of connections is the number of connections multiplied by the number of processes.

Limiting the maximum number of connections is useful in systems where system overload may be caused by a high load in the server program when opening new connections.

Maximum number of connections defines the maximum number of client connections allowed per servant. The value range is 1-256. The default value is 256.

Total number of connections defines the maximum number of connections that a servant will handle before the server should start a new servant in its place. The value range is 1-4,000,000,000. If no value is given (default), the servant-lifetime functionality will be disabled and the servants are never retired. This corresponds to the servant-lifetime element in the server configuration file, see servant-lifetime.

Maximum number of processes defines the maximum number of servant processes the master server will launch. The value range is 1-40. The default is 40.

The GUI does not allow you to type in illegal values.

Tectia Server can be operated in FIPS mode, using a version of the cryptographic library that has been validated according to the Federal Information Processing Standard (FIPS) 140-2. In this mode, the cryptographic operations are performed according to the rules of the FIPS 140-2 standard. The OpenSSL cryptographic library is used in the FIPS mode.

Select the Operate in FIPS Mode check box to use the FIPS-certified version of the SSH cryptographic library. Clear the check box to use the standard (default) SSH cryptographic library.

	Note
	Tectia Server has to be restarted after changing the FIPS-mode setting. Extra checks are done when starting the Tectia Server and Connection Broker in the FIPS mode due to the OpenSSL FIPS crypto library health check. This will lead to a noticeable delay in the start of the process on slow machines.

To define a banner message file, click the Browse button on the right-hand side of the text field. The Select File dialog appears, allowing you to specify the desired file. You can also type the path and filename directly into the text field.

The message file is sent to the client before authentication. Note, however, that the client is not obliged to show this message.

Specify a time after which the server disconnects if the user has not successfully logged in. If the value is set to 0, there is no time limit. The default is 600 seconds.

Specify a path to a directory from where Tectia Server looks for user-specific authorized public keys, if they are not stored to the default location. With this setting the administrator can control options that are usually controlled by the user. If no setting is given, the default setting will be used.

The default setting is %D/.ssh2, which expands to %USERPROFILE%\.ssh2 (usually "C:\Documents and Settings\<username>\.ssh2").

Enter the path as a pattern string which will be expanded by Tectia Server. The following pattern strings can be used:

	Note
	The User configuration directory setting will be read only if the Authentication view does NOT have anything set in the following settings: Authorization file Authorized-keys directory OpenSSH authorized-keys file For reference, see Parameters

Specify what kind of user log-on methods for the local host are accepted by Tectia Server. The defined log-on type affects password authentication. Select a suitable value from the dropdown menu: batch, interactive, network, or network-cleartext. The default value is interactive. Note that this setting only affects password-based authentication methods.

For example, to enable accounts that do not have the access right to log on locally, select value network.

For information on the attribute values, refer to Microsoft documentation on Windows logon types.

Define whether Tectia Server should try to resolve the client host name from the client IP address during connection setup. By default, Yes is selected and DNS lookups are used to resolve the client host name at connection time.

If you select No, client host name resolution is not attempted, but the IP address is used as the returned client host name. This is useful when you know that the DNS cannot be reached, and the query would cause just additional delay in logging in.

	Note
	This attribute does not affect the resolution of TCP tunnel endpoints and Tectia Server will try to resolve the client host name when creating a TCP tunnel.

Define the mode of operation of a terminal session on the server side. This setting can have values Console and Stream.

If set to Console (default), the server reads the screen buffer in a loop and detects modifications based on current cursor location. If set to Stream, the server reads the stdout and stderr of cmd.exe as a stream of data, while providing basic facilities for command-line editing.

Define the address family Tectia Server will use for incoming connections.

If set to IPv4 (default), the server will accept only IPv4 incoming connections. If set to IPv6, the server will accept only IPv6 incoming connections. If set to both, the server will accept both IPv4 and IPv6 incoming connections, will resolve addresses of both families, and opens both IPv4 and IPv6 listeners for remote port forwarding.

Select the Terminate on session close check box to have all processes started by the user on the SSH terminal session terminated when the user logs off from the session. By default this is not enabled.