Within the TCP/IP suite, which protocol provides remote terminal connection service (allowing users to log in to a remote host interactively)?

Difficulty: Easy

Correct Answer: TELNET

Explanation:


Introduction / Context:
Remote administration and interactive sessions predate SSH. In the classic TCP/IP suite, a standardized protocol enabled users to open a terminal session on a remote machine. Recognizing the purpose of each protocol avoids misconfiguration and helps in understanding historical tools and their modern replacements.


Given Data / Assumptions:

  • We are discussing legacy, clear-text protocols in the original TCP/IP stack.
  • Focus is on interactive remote terminal access.
  • Options include protocols with distinct functions unrelated to terminal login.


Concept / Approach:
TELNET (TCP port 23) provides an interactive, text-based remote terminal connection. It negotiates terminal options and transmits keystrokes and screen output. Although insecure by modern standards (no encryption), it is the classic answer for remote terminal service. In contrast, FTP handles file transfer, UDP is a transport layer protocol (not an application protocol), and RARP maps MAC addresses to IPs in early boot scenarios; none of these create an interactive login shell like TELNET does.


Step-by-Step Solution:

Identify the need: interactive, bidirectional terminal session.Map to protocol: TELNET fits this use case.Eliminate distractors: FTP (file transfer), UDP (transport), RARP (address resolution).Select TELNET as the correct protocol.


Verification / Alternative check:
Modern practice uses SSH (Secure Shell) as a secure replacement for TELNET. Running 'telnet host 23' (if available) demonstrates the unsecured login prompt, reinforcing TELNET's role while highlighting its security drawbacks.


Why Other Options Are Wrong:

  • FTP: Transfers files; does not provide terminal login.
  • UDP: A transport; not a remote terminal application protocol.
  • RARP: Used for address resolution during booting diskless systems; not interactive login.
  • None of the above: Incorrect because TELNET directly satisfies the requirement.


Common Pitfalls:
Equating TELNET with SSH in security properties (they are not equivalent) or believing FTP includes remote command execution by default—it does not provide an interactive shell.


Final Answer:
TELNET

Discussion & Comments

No comments yet. Be the first to comment!
Join Discussion