TCP/IP Configuration and Management Manual

Configuring the NonStop TCP/IP Subsystem
TCP/IP Configuration and Management Manual—427132-004
3-33
Configuring Subsystem Processes
FTP includes a standard set of commands and responses and, if applicable, reports
corresponding state changes.
For a detailed description of the FTP server and client commands, refer to the TCP/IP
Applications and Utilities User Guide For more detailed technical information on FTP,
refer to RFC 959 (DDN Protocol Handbook, Volume 2, DDN Network Information
Center, December, 1985, pp. 2-739 through 2-808). Also, refer to the book
Internetworking with TCP/IP (Douglas E. Comer, Prentice Hall, 1991).
FINGER Client/Server
The FINGER protocol provides a method for retrieving status information about one or
all of the users on a particular system. This protocol is used over a TCP connection.
The process that handles incoming requests from FINGER clients is LISTNER. A line
that has the proper information must be included in the PORTCONF configuration file
for the LISTNER process, as described in Configuration Files in the Guardian
Environment on page 3-34.
When the LISTNER process receives an incoming connection request for the FINGER
program, it starts up the FINGER server program. The FINGER server is a TCP
program that listens for connections on TCP port 79.
The FINGER server, once started, accepts the connection on a socket. It reads the
socket to obtain a user name, then sends information about the user (or about all
users, if no user name was specified).
For a detailed description of the operation of the FINGER server and client, refer to the
TCP/IP Applications and Utilities User Guide. For more detailed technical information
on FINGER, refer to RFC 742 (DDN Protocol Handbook, Volume 2, DDN Network
Information Center, December, 1985, pp. 2-1017 through 2-1024). Also, refer to the
book TCP/IP Illustrated by W. Richard Stevens, Prentice Hall, 1994.
ECHO Client/Server
The ECHO protocol provides a debugging tool for determining access to network
hosts. On the NonStop system, ECHO is used with TCP to allow an ECHO client to
send data to the ECHO server. If access to the host on which the server is running is
possible, the data will be returned to the requesting client. If the data is not returned to
the client, the named host is inaccessible or is not running the specified protocol.
The ECHO client can be run from any terminal connected to the NonStop server,
including a workstation emulating a 6530 or network virtual terminal. NonStop TCP/IP
ECHO does not service UDP ports.
For a detailed description of the ECHO server and client, refer to the TCP/IP
Applications and Utilities User Guide. For more detailed technical information on
ECHO, refer to RFC 862 (DDN Protocol Handbook, Volume 2, DDN Network
Information Center, December, 1985, pp. 2-1001 through 2-1002). Also, refer to the
book TCP/IP Illustrated by W. Richard Stevens, Prentice Hall, 1994.