You can perform management tasks for workstation connections to the NetWare^® server from the Connections option in MONITOR's Available Options menu. Console commands that serve the same purpose are also listed for some tasks.

The tasks for which you can use MONITOR include

The following table contains tasks and procedures.

Table 3. Monitoring Server Connections

To	Do
View a list of active server connections Determine which users are logged in	1. Select Available Options > Connections. The list of Active Connections appears. 2. (Optional) Press F3 to re-sort the connection list. List items without an asterisk (*) represent logged-in users. List items with an asterisk (*) are unlicensed connections (this means they do not count against a server's total licenses). These connections are authenticated to NDS but are not logged in.
View information about a connection Connection number Connection name Elapsed connection time Network node address Read/write requests Authentication and license status Files in use Locks and semaphores in use Supervisor rights	1. Select Available Options > Connections to display the list of Active Connections. 2. Highlight a connection from the list. 3. Press Tab to activate the Connection Information screen in the upper window. 4. For an explanation of the information fields and statistics, press F1.
Configure a watchdog to monitor connections for activity	See Configuring Watchdog Packets and Enabling Console Message when Watchdog Logout Occurs.
View a list of files that the connection has open. Use this procedure when you want to determine whether a crashed workstation has open files remaining on the server.	1. Select Available Options > Connections. 2. Select the connection from the list. 3. After determining whether files are open on the server, press Esc to return to the Active Connections list.
Terminate one or more connections Use this procedure to clear the connection when a workstation has crashed and left open files on the server. Note: Transaction monitoring (TTS) provides automatic backout for database records or files stored on the server if a workstation has crashed and left those files open on the server. Also a file is protected if the Transaction (T) file attribute is set for it.	1. Select Available Options > Connections. 2. Highlight the connection (or for multiple connections, highlight each one and press F5 to mark it). 3. Press Delete. 4. At the Clear Connection? prompt, select Yes. Deleted connections are no longer listed. Press F6 to clear all unlicensed connections, indicated in the connection list by an asterisk (*). These connections are authenticated but are not logged in and therefore do not count against a server's total licenses. Note: If you know the connection number, you can also terminate a connection at the server console prompt with CLEAR STATION n. Use CLEAR STATION ALL to terminate all connections. See CLEAR STATION in Utilities Reference.
Send a message to one or more workstations Use this procedure when you need to warn users to log out before you down the server.	1. Select Available Options > Connections. 2. Highlight the connection (for multiple connections, highlight each connection and press F5 to mark it and then press F4 to confirm your selections). 3. In the text-entry box that appears, enter the message. 4. At the confirmation prompt, select Yes to send the message or select No to redisplay the text-entry window. Note: In the Active Connections list, items without an asterisk (*) represent logged-in users.

Sending Console Messages to Workstations

To send a message from the server console to all workstations or to a single user, access MONITOR.

Clearing a Workstation Connection

You can use either MONITOR or CLEAR STATION to clear a client connection when the workstation has crashed and left open files on the server.

NOTE:  If you clear the connection while the workstation is in the middle of a transaction or a file update, the files might be saved with incorrect data.

Using CLEAR STATION to Clear the Connection

Disabling and Enabling Logins

If you need to make repairs to the server, you can prevent users from logging in by entering the following at the server console prompt:

DISABLE LOGIN

This does not affect users who are already logged in to the network. However, a user who logs out cannot log in again until you execute ENABLE LOGIN.

To allow users to log in again, enter the following at the server console prompt:

ENABLE LOGIN

You can also use ENABLE LOGIN to enable a SUPERVISOR account when it has been locked by the intruder detection function.

Clearing a Connection that Uses Auto Reconnect

Client 32 has automatic reconnection capabilities that make possible a complete restoration of the user environment after a network failure. Because auto-reconnect is enabled by default, you need to prevent workstations from reconnecting while you are trying to perform some function on the server.

Client 32 also supports file caching on the client side, which allows files to be cached as they are read from the server and as they are written to the server. With the default settings for the Auto Reconnect Level and the File Cache Level parameters, Client 32 will restore all files to their actual state before the workstation connection was cleared (or the server went down). The workstation monitor displays a message:

Client32: Please wait while Application retries request to ServerName. To stop waiting, press Enter. NetWare will then return an error and try to reconnect in the background.

You can combine the use of console commands to prevent clients from reconnecting for long enough to complete your work on the server.

Controlling Resource Allocation with Locks

A lock prevents a file or record from being updated by more than one user at a time. By controlling the number of file and record locks available to a workstation or a server, you control access to files and records.

You can increase the number of locks if clients cannot open files. Or you can limit the number of locks to prevent overuse of file resources.

Preventing Workstations from Overusing File Resources

If you are running out of file resources, use MONITOR to limit the number of locks for the server and for each connection.

Before limiting file and record locks, make sure the workstations have an adequate number of locks to access the files and records they need. Limiting needed locks can cause applications to generate errors.

Increasing File Record Locks

Use MONITOR to provide more file record locks if applications fail either because clients cannot open enough files or because not enough record locks are available.

Configuring Watchdog Packets

The server sends watchdog packets to a workstation to determine if the workstation connection is still active. If there is no response from the workstation within a set amount of time, the server terminates the connection.

To provide an early warning that a connection has failed, set the values of the watchdog parameters so that the server sends twice the default number of packets in the shortest amount of time allowed.

Enabling Console Message when Watchdog Logout Occurs

If you enable an alert, a console message displays when the server terminates a connection.