Please Whitelist This Site?

I know everyone hates ads. But please understand that I am providing premium content for free that takes hundreds of hours of time to research and write. I don't want to go to a pay-only model like some sites, but when more and more people block ads, I end up working for free. And I have a family to support, just like you. :)

If you like The TCP/IP Guide, please consider the download version. It's priced very economically and you can read all of it in a convenient format without ads.

If you want to use this site for free, I'd be grateful if you could add the site to the whitelist for Adblock. To do so, just open the Adblock menu and select "Disable on tcpipguide.com". Or go to the Tools menu and select "Adblock Plus Preferences...". Then click "Add Filter..." at the bottom, and add this string: "@@||tcpipguide.com^$document". Then just click OK.

Thanks for your understanding!

Sincerely, Charles Kozierok
Author and Publisher, The TCP/IP Guide


NOTE: Using software to mass-download the site degrades the server and is prohibited.
If you want to read The TCP/IP Guide offline, please consider licensing it. Thank you.

The Book is Here... and Now On Sale!

Searchable, convenient, complete TCP/IP information.
The TCP/IP Guide

Custom Search







Table Of Contents  The TCP/IP Guide
 9  TCP/IP Application Layer Protocols, Services and Applications (OSI Layers 5, 6 and 7)
      9  TCP/IP Key Applications and Application Protocols
           9  TCP/IP Interactive and Remote Application Protocols
                9  Telnet Protocol

Previous Topic/Section
Telnet Protocol
Previous Page
Pages in Current Topic/Section
12
3
Next Page
Telnet Connections and Client/Server Operation
Next Topic/Section

Telnet Overview, History and Standards
(Page 3 of 3)

Telnet Applications

Telnet is most often associated with remote login, which is its most common traditional use. A user typically uses a Telnet client program to open a Telnet connection to a remote server, which then treats the Telnet client like a local terminal, allowing the user to log in and access the server’s resources as if he or she were using a directly-attached terminal. Telnet is still used this way quite extensively by UNIX users, who often need to log in to remote hosts from their local machines; I myself use Telnet in this manner every day to access a machine hundreds of miles away. However, this use of Telnet is not nearly as common amongst the majority of Internet users who work on Windows or Apple computers where network resources are accessed not through direct login but by other means.

However, while remote login is a big part of what Telnet is about, it’s important to note that the protocol was not inherently designed for that specific function. When Telnet is used to access a remote device, the protocol itself is only used to set up the connection between the client and server machines, encode data to be transmitted according to the rules of the Telnet NVT, and facilitate the negotiation and use of options. It is the client and server devices themselves that decide whether Telnet is used for remote access or for some other purpose.

Telnet's Legacy

Telnet’s flexibility, combined with its age in the TCP/IP suite, has led to Telnet being adopted for a variety of other protocols. Since Telnet doesn’t make assumptions about what a client is and what a server is, any program or application can use it. Many of the file and message transfer applications, including FTP, SMTP, NNTP and HTTP, communicate through the sending of text commands and messages, and use the Telnet’s NVT specification to ensure the compatibility of communication between devices. They don’t actually establish Telnet sessions or use features like option negotiation, they just send data in a manner consistent with how Telnet works.

Thus, even though modern Internet users may never intentionally invoke Telnet specifically, they use it indirectly every time they send or receive e-mail or browse the Web. Administrators can even use Telnet client software to access devices such as FTP and HTTP servers and send them commands manually.

Key Concept: Telnet is one of the oldest protocols in the TCP/IP suite, first developed in the 1960s to allow a user on one computer system to directly access and use another. It is most often used for remote login, with Telnet client software on a user’s machine establishing a session with a Telnet server on a remote host to let the user work with the host as if connected directly. To ensure compatibility between terminals and hosts that use different hardware and software, communication between Telnet client and server software is based on a simplified, fictional data representation that can be enhanced through the negotiation of options.



Previous Topic/Section
Telnet Protocol
Previous Page
Pages in Current Topic/Section
12
3
Next Page
Telnet Connections and Client/Server Operation
Next Topic/Section

If you find The TCP/IP Guide useful, please consider making a small Paypal donation to help the site, using one of the buttons below. You can also donate a custom amount using the far right button (not less than $1 please, or PayPal gets most/all of your money!) In lieu of a larger donation, you may wish to consider purchasing a download license of The TCP/IP Guide. Thanks for your support!
Donate $2
Donate $5
Donate $10
Donate $20
Donate $30
Donate: $



Home - Table Of Contents - Contact Us

The TCP/IP Guide (http://www.TCPIPGuide.com)
Version 3.0 - Version Date: September 20, 2005

© Copyright 2001-2005 Charles M. Kozierok. All Rights Reserved.
Not responsible for any loss resulting from the use of this site.