Technical data

Managing TCP/IP Services

1.5 Auxiliary Server

When it receives a request, the auxiliary server dynamically creates a network

process, obtaining user account information from one or all of the following

sources:

• TCP/IP Services proxy account

• Services database

• Remote client

• Local OpenVMS user authorization ﬁle (UAF)

In addition, users requesting services at the client can include their user account

information as part of the command line.

Once a process is created, the auxiliary server starts the requested service. All

services except RLOGIN and TELNET must have access to their default device

and directories and to the command procedures within them.

1.5.1.1 Rejecting Client Requests

The auxiliary server rejects client requests for the following reasons:

• The maximum number of simultaneous processes for the requested service

has been reached.

• The request is from a host that is marked for rejection.

• There is a problem with the target account or directory.

1.5.1.2 Conﬁguring the Auxiliary Server

The postinstallation conﬁguration procedure, TCPIP$CONFIG, creates an entry

in the services database (TCPIP$SERVICE.DAT) for each service you conﬁgure.

If you need to modify your initial conﬁguration, run TCPIP$CONFIG or use the

SET SERVICE command.

The conﬁguration ﬁle TCPIP$SERVICE.DAT includes information about the

service name, the socket and protocol type associated with the service, the user

name under which the service should run, and any special options for the service

program.

Before you activate a service manually, conﬁgure the auxiliary server as follows:

1. Use the OpenVMS Authorize utility to create a restricted user account for the

process. Use the following qualiﬁers when creating the account:

• /NOINTERACTIVE

• /NOBATCH

• /NOREMOTE

• /FLAGS=(RESTRICTED,NODISUSER,NOCAPTIVE)

For more information about creating restricted accounts, see the OpenVMS

system security documentation.

2. Provide user account information that can be used when the network process

is created. Plan your requirements carefully before setting privileges, quotas,

and priorities to user accounts.

3. Provide the network process name.

1–8 Managing TCP/IP Services