Content area
Full Text
Operating System: Microsoft Windows NT 4.0
Remote access is a bone of contention in almost every enterprise network today. Companies experience much internal strife over what type of remote access methods should be implemented. If you need a straightforward and easy remote access connection to a server, you can always use the Windows NT Telnet service.
Tuning in Telnet
This article will discuss setting up a Telnet server on Windows NT 4.0. First, we'll examine the Telnet protocol and its operation. Next, we'll discuss the problems and advantages to using Telnet to connect remotely to other servers. Last, we'll explore how to set up the NT Telnet service on a Windows NT server.
What is this Tel-net thing?
It's no secret today. Almost every administrator or engineer has, at one point or another, come across a Telnet utility. If not, odds are that you've at least heard of Telnet. Telnet is nothing more than a cross platform, remote access protocol for use on TCP/IP based networks for remote administration of hosts.
One of the oldest and most reliable utilities available inside the TCP/IP suite of protocols, Telnet was standardized around the time of the mid-'70s. Telnet is short for Telecommunications Network and, at its most basic level, provides a remote terminal emulation layer to incoming clients to use as the access method for a host when local or physical access isn't feasible.
Telnet came about because the IT departments of old became tired of not being able to connect to many different types of systems without jumping through hoops. Back then, each vendor made its mainframe in its own proprietary way, which precluded the concept of interoperability. As a result, engineers began work on a protocol that would provide platform-independent terminal emulation. Thus, if a client needed to contact a remote system, he or she could do so through the Telnet protocol. The idea...