| Unknown service |
This message will be written to $STDLIST for
JINETD.NET.SYS when a Telnet client is unable to find the
Telnet entry in the services file. Telnet client users may see a similar
message on their terminal, and call you, the system manager of the host,
to resolve the problem. Open the services file and make sure that the
line telnet 23/tcp exists. If necessary add the line and then
reconfigure the Internet daemon. For more information, read "Editing the
Services File" earlier in this chapter. |
| The Telnet client cannot run Telnet |
The Telnet client user may not have entered the correct program name at
the prompt, which is TELNET.ARPA.SYS. Or, there may be problems
with the network. |
| The Telnet client cannot connect to the host |
The Telnet client user can encounter this problem for one of several
reasons:
- The user entered the domain name, IP address, or NS node name
incorrectly.
- The system the client attempted to access does not support
Telnet.
- The network of the system the client attempted to access is not
working.
- The Internet daemon is not running on the system the client tried to
access.
|
| There is a host name lookup failure |
The Telnet user tried to log on when the network was not running. Or the
host system the client tried to access is not configured on the
network. |
| The Telnet client cannot logon to a host |
The Telnet client successfully established a connection to the host, but
could not logon. The user may call you, as host system manager, to
verify that the logon account and passwords are correct and to see if
the system limits are set such that new Telnet sessions are
prohibited. |
| The Telnet server cannot run an application |
The Telnet client successfully established a Telnet connection and logs
on to the host system. But, when the user runs the application, the
software behaves oddly or it produces error messages. If you receive a
call about this problem, you or the user can consult the
Asynchronous Serial
Communications Programmer's Reference Manual to see if the
application is attempting to use file system instrinsics that the Telnet
server doesn't support. Or have the user and his or her system manager
check the set and toggle values on their system to make sure they are
the values required by the application. |
| Invalid command |
The Telnet client user entered an invalid command at the Telnet prompt.
Type a question mark (?) to display a list of valid
commands. |
