mvTelnet Server Considerations

Take the following matters into consideration as you plan and configure one or more mvTelnet Servers.

Windows Considerations

If your network does not have a Domain Name System (DNS) you may need to add IP address entries in the HOSTS file. The HOSTS file is a name resolution file which matches the network name of computer systems to their IP addresses. For example, you may edit the HOSTS file in UNIX using the VI Editor. The entries in the HOSTS file should contain both the system name(s) and the IP address(es).
mvTelnet requires TCP/IP to be installed on client and Server systems.
Since mvTelnet is both port-definable and multiport capable, it can coexist with other Windows. Telnet servers by choosing different TCP ports for each.

Multiple mvTelnet Servers

When configuring multiple mvTelnet Servers, each of which uses a single dedicated line and TCP port, Rocket recommends using a consecutive sequence of lines and TCP ports. Available TCP ports are 23, and 1024-5000. To reduce the likelihood of encountering a previously consumed port when configuring the sequence of lines, Rocket recommends starting with port 2000. Line configuration should follow the recommendations made earlier.

mvTelnet Servers are configured with the Telnet Servers tab of the mvBase Workstation. Note, however, that this approach cannot guarantee resolved conflict with other line or TCP port consumption.

TCP Port and mvBase Line Consumption

In some circumstances, it may be advantageous to configure the mvTelnet Server to connect a TCP port to specific mvBase line(s) on the mvBase Server. This channels one or more Telnet clients with exact precision and these potential advantages:

Telnet clients connecting via terminal servers can each be restricted to a specific mvBase line.
There can be increased convenience for users of Telnet clients, who always know which TCP port to designate during connection with higher chances of availability of the desired line.
The administrator can avoid automatic consumption of the default TCP port 23.
An mvBase line can be administratively assigned to an exclusive Telnet client, helping ensure the identity of the connecting Telnet client and enhancing security. Note that the mvTelnet Server(s) must administer all TCP ports very tightly to ensure a high degree of security.
The quantity of connecting Telnet clients can be carefully controlled, also enhancing security.
There can be very specific allocation of interoperability functions to individual Telnet clients or groups of clients.

NOTE	When a TCP port is to be allocated to one or more specific mvBase lines, Rocket recommends following the guidelines in the section Coordinating Line Configuration for Multiple Client Types, contained in the mvBase Installation Guide.