The Telnet Server allows remote access to a system through a TCP/IP network such as a LAN or the Internet. There are
a number of reasons for doing this: 

                                            remote problem anaysis and correction 
                                            remote access to private IP networks 
                                            running text mode OS/2 programs from non-OS/2 systems 

Use the following command to start the Telnet Server in OS/2: 

                                           start /f /c telnetd -u <password>

where "<password>" is a password which must be used to gain access to the system. 

Once the server is running, you can start up the TELNET or TELNETPM client on another system. This could be on
OS/2, UNIX, or any other operating system with the normal TCP/IP utilities. Enter the IP address of the system to be
accessed and the password and you will have access to the command line on the remote system. 

To see how this works, you can try it out on a single system. First, go to the OS/2 command line and make sure you
have a local loopback address defined: 

                                           ifconfig lo 127.0.0.0

(See TCP/IP interface configuration for more information on the ifconfg command.) 

Next, start the Telnet Server: 

                                           start /f /c telnetd -u secret

Finally, start the Telnet client, connecting to the local server. 

                                           start /f /c telnet 127.0.0.0

or: 

                                           start telnetpm 127.0.0.0

Enter the password "secret" to complete the connection and display the command line prompt. 

The connection between the Telnet client and the system to be accessed could be over the Internet, with each system
running on a dial-up connection to the Internet. In this case, if the IP address is dynamically assigned, you need to
know the address which has been assigned to the system running the Telnet Server. The address could be displayed
while starting the server using the following command: 

                                           start /f "Telnet Server" /c "netstat -a & telnetd -u secret"

If an icon was created for this command, it might be used to provide remote support to OS/2 users through the
Internet. The user would connect to the Internet and click on the icon to start the Telnet Server, then provide you with
the IP address displayed at the top of the server window. You could then connect to their system through the Internet
using the IP address provided. 

Once connected to the remote system, you can execute any text mode OS/2 program on that system. For example, the
text mode version of the Telnet client (TELNET, but not TELNETPM) could be executed. One reason for doing this
would be to remotely access systems on a private IP network, when the other systems do not have their own connection
to the Internet. One Telnet session would be running between your client system and the OS/2 system running the
Telnet Server, and another Telnet session would be running between the OS/2 system and the destination, but you
would be viewing the destination's screen on your client system. 

Note to Netware users: 

The Telnet Server in TCP/IP for OS/2 Warp Version 3 used "login.exe" to verify authorization to access the system. A
somewhat different "login.exe" file is also provided with the Netware Client (Requester) for OS/2. If the Netware
directory appears before the \tcpip\bin directory in the OS/2 PATH, then the Netware "login.exe" will be executed,
which results in logging into a Netware server and executing the associated "login.bat" file. While this might be useful
for providing remote access to Netware, if you are using it for remote access to the OS/2 system itself, you probably
don't want to see the system as is, rather than have the drive mappings changed when you login, so you probably want
to change the PATH to make sure the TCP/IP directory comes before the Netware directory.