Scribd
Upload
27 views4 pages

Overview of Application Layer Protocols

The document discusses several application layer protocols used in IP networks including Telnet, FTP, TFTP, NFS, SMTP, LPD, X Window, SNMP, and DNS. It provides details on what each protocol is used for and how it functions at a high level.

Uploaded by

hassan IQ
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
27 views4 pages

Overview of Application Layer Protocols

The document discusses several application layer protocols used in IP networks including Telnet, FTP, TFTP, NFS, SMTP, LPD, X Window, SNMP, and DNS. It provides details on what each protocol is used for and how it functions at a high level.

Uploaded by

hassan IQ
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd

Network Technology Fourth Year

Application Layer Protocols


There are different applications and services typically used in IP networks located
in application layer such as Telnet, FTP, TFTP, NFS, SMTP, LPD, X Window,
SNMP, DNS, and DHCP/BootP.

Telnet
Telnet is the chameleon of protocols—its specialty is terminal emulation. It allows
a user on a remote client machine, called the Telnet client, to access the resources
of another machine, the Telnet server. Telnet achieves this by pulling a fast one on
the Telnet server and making the client machine appears as though it were a
terminal directly attached to the local network. This projection is actually a
software image—a virtual terminal that can interact with the chosen remote host.
These emulated terminals are of the text-mode type and can execute refined
procedures like displaying menus that give users the opportunity to choose options
from them and access the applications on the duped server. Users begin a Telnet
session by running the Telnet client software and then logging into the Telnet
server.

File Transfer Protocol (FTP)


File Transfer Protocol (FTP) is the protocol that actually lets us transfer files, and
it can accomplish this between any two machines using it. But FTP isn’t just a
protocol; it’s also a program.
Operating as a protocol, FTP is used by applications. As a program, it’s employed
by users to perform file tasks by hand. FTP also allows for access to both
directories and files and can accomplish certain types of directory operations, such
as relocating into different ones. FTP teams up with Telnet to transparently log you
into the FTP server and then provides for the transfer of files.
Accessing a host through FTP is only the first step, though. Users must then be
subjected to an authentication login that’s probably secured with passwords and

73
Network Technology Fourth Year

usernames implemented by system administrators to restrict access. But you can get
around this somewhat by adopting the username “anonymous”—though what
you’ll gain access to will be limited.
Even when employed by users manually as a program, FTP’s functions are limited
to listing and manipulating directories, typing file contents, and copying files
between hosts. It can’t execute remote files as programs.

Trivial File Transfer Protocol (TFTP)


Trivial File Transfer Protocol (TFTP) is the stripped-down, stock version of FTP,
but it’s the protocol of choice if you know exactly what you want and where to find
it, plus it’s so easy to use and it’s fast too! It doesn’t give you the abundance of
functions that FTP does, though. TFTP has no directory-browsing abilities; it can
do nothing but send and receive files. This compact little protocol also skimps in
the data department, sending much smaller blocks of data than FTP, and there’s no
authentication as with FTP, so it’s insecure. Few sites support it because of the
inherent security risks.

Network File System (NFS)


Network File System (NFS) is a jewel of a protocol specializing in file sharing. It
allows two different types of file systems to interoperate. It works like this:
Suppose the NFS server software is running on an NT server, and the NFS client
software is running on a Unix host. NFS allows for a portion of the RAM on the
NT server to transparently store Unix files, which can, in turn, be used by Unix
users. Even though the NT file system and Unix file system are unlike they have
different case sensitivity, filename lengths, security, and so on both Unix users and
NT users can access that same file with their normal file systems, in their normal
way.

74
Network Technology Fourth Year

Simple Mail Transfer Protocol (SMTP)


Simple Mail Transfer Protocol (SMTP), answering our huge call to e-mail, uses a
spooled, or queued, method of mail delivery. Once a message has been sent to a
destination, the message is spooled to a device—usually a disk. The server software
at the destination posts a vigil, regularly checking this queue for messages. When it
detects them, it proceeds to deliver them to their destination. SMTP is used to send
mail; POP3 is used to receive mail.

Line Printer Daemon (LPD)


The Line Printer Daemon (LPD) protocol is designed for printer sharing. The LPD,
along with the LPR (Line Printer) program, allows print jobs to be spooled and sent
to the network’s printers using TCP/IP.

X Window
Designed for client-server operations, X Window defines a protocol for writing
client/server applications based on a graphical user interface (GUI). The idea is to
allow a program, called a client, to run on one computer and have it display things
through a window server on another computer.

Simple Network Management Protocol (SNMP)


Simple Network Management Protocol (SNMP) collects and manipulates the
valuable network information. It gathers data by polling the devices on the network
from a management station at fixed or random intervals, requiring them to disclose
certain information. When all is well, SNMP receives something called a
baseline—a report delimiting the operational traits of a healthy network. This
protocol can also stand as a watchdog over the network, quickly notifying
managers of any sudden turn of events. These network watchdogs are called agents,
and when aberrations occur, agents send an alert called a trap to the management
station.

75
Network Technology Fourth Year

Domain Name Service (DNS)


Domain Name Service (DNS) resolves hostnames—specifically, Internet names,
such as [Link] . You don’t have to use DNS; you can just type in the
IP address of any device you want to communicate with. An IP address identifies
hosts on a network and the Internet as well. However, DNS was designed to make
our lives easier. Think about this: What would happen if you wanted to move your
web page to a different service provider? The IP address would change and no one
would know what the new one was. DNS allows you to use a domain name to
specify an IP address. You can change the IP address as often as you want, and no
one will know the difference. DNS is used to resolve a fully qualified domain name
(FQDN) —for example, [Link] or [Link] . An FQDN is a
hierarchy that can logically locate a system based on its domain identifier.
If you want to resolve the name “todd,” you either must type in the FQDN of
[Link] or have a device such as a PC or router add the suffix for you.
For example, on a Cisco router, you can use the command ip domain-name
[Link] to append each request with the [Link] domain. If you don’t do
that, you’ll have to type in the FQDN to get DNS to resolve the name.

76

Common questions

Powered by AI

NFS facilitates file sharing across different file systems by allowing interoperability between systems such as NT and Unix. It enables a part of the NT server's RAM to store Unix files transparently, allowing Unix users to access them as if they were on a Unix system. This resolves challenges of differing case sensitivity, filename lengths, and security mechanisms between systems by allowing both Unix and NT users to access files with their respective file systems as normal. This interoperability is a key feature for environments using multiple operating systems .

TFTP is designed to be easy to use and fast by having no authentication process and sending smaller blocks of data compared to FTP. This prioritization results in simplicity and speed, making it suitable for simple file transfers when users know exactly what they need. However, the trade-off is significant security vulnerabilities because it doesn't authenticate users, leaving it susceptible to unauthorized file transfers and access. As a consequence, few sites support TFTP due to the inherent security risks .

DNS resolves the challenge of changing IP addresses by allowing the use of domain names instead of static IP addresses. Domain names can be mapped to different IP addresses without users knowing about the change, making transitions to different service providers seamless. Without DNS, each time an IP address changes, users would need to learn and use the new address, severely disrupting accessibility. DNS simplifies this process by managing the mapping across changes .

SMTP employs a spooled, or queued, delivery method to ensure messages are sent to their destinations. Once a message arrives at a server, it is spooled to a device like a disk until the destination's server software can process its delivery. The destination server regularly checks this queue and proceeds with delivery as soon as it detects new messages. This queued system ensures reliable transmission despite any temporary network issues .

FTP allows anonymous access where users can log in using the "anonymous" username; however, this access is typically limited to certain directories and resources to minimize security risks. Authenticated access, in contrast, requires a username and password set by system administrators, which grants access to a broader range of directories and functionalities on the FTP server. The use of anonymous access can pose security risks by potentially exposing sensitive data to unauthorized users, whereas authenticated access provides a layer of security through credential verification .

The Line Printer Daemon (LPD) protocol facilitates network printing by enabling multiple print jobs to be spooled and managed over a TCP/IP network. It operates in conjunction with the LPR (Line Printer) program to manage these print queues. The protocol allows print jobs from different clients to be sent to a centralized network printer, consolidating management of print resources and enhancing efficiency in networked environments .

DNS enhances user experience by allowing easier access to systems using memorable domain names rather than numerical IP addresses, which are harder for humans to remember. Through hierarchical domain identifiers such as Fully Qualified Domain Names (FQDN), DNS logically locates systems, enabling smoother internet navigation and flexibility. It is preferable to IP addresses because it abstracts this layer of complexity, helping users focus on recognizable names rather than numeric identifiers, thereby preventing user errors and improving accessibility .

Telnet's terminal emulation allows a user on a remote client machine to access the resources of another machine by making the client appear as a terminal directly attached to the local network. This is accomplished through a virtual terminal—a software image—that interacts with the remote host. Users are able to execute refined procedures like displaying menus for option selections and accessing applications on the server. This enhances interaction by providing a seamless interface that appears locally attached, simplifying remote operations .

SNMP agents act as network watchdogs by monitoring network devices and systems. They regularly report the status and performance metrics to a designated management station by polling the devices for specific information. When everything is operating normally, agents compile and report baseline data reflecting the traits of a healthy network. In the event of anomalies or failures, these agents send alerts or 'traps' to the management station, enabling quick responses to potential issues. This interaction allows managers to maintain oversight and control of network health efficiently .

X Window defines a protocol suited for client-server operations that employ a graphical user interface. Its primary purpose is to enable a program, called a client, to run on one machine while dynamically displaying graphic outputs through a server on a different machine. This functionality enables remote interaction with graphical applications, as it decouples the computing location from its visualization, thereby enhancing user flexibility and resource utilization .

You might also like