Overview

Introduction

The Understand TCP/IP Services Part 3 module provides you with the instruction and computer hardware to develop your hands on skills in the defined topics. This module includes the following exercises:

  • Administering Kali Linux Using VNC and SSH
  • Verifying Port 80 for HTTP
  • Verifying HTTPS Port 443
  • Verifying Port 139 for NetBIOS
  • Contrast TCP and UDP Protocols

Exam Objectives

The following exam objectives are covered in this lab:

  • 220-901: 3.4 Explain common TCP and UDP ports, protocols and their purpose (80 HTTP, 443 HTTPS, 137-139 - Netbios/NetBT, TCP vs. UDP, 22 SSH)
  • 220-901: 1.6 Given a scenario, install and configure Windows networking on a client/desktop (Remote Desktop Connection
  • 220-902: 2.1 Identify common features and functionality of the Mac OS and Linux operating systems (Shell/Terminal, Basic Linux commands)

Lab time: It will take approximately 1 hour to complete this lab.

Exercise 1 - Administering Kali Linux Using VNC and SSH

Virtual Network Computer or VNC is a graphical desktop sharing program that allows you to remotely control another computer. This tool transmits the keyboard and mouse movements on your computer to a remote system, and responds with graphical screen updates. All this communication takes place over a network. 5900 is the default port number for VNC.

Many VNC variants are available for free public download. You can explore these to select the one most suited to your requirement(s).

Similarly, Secure Shell or SSH is an encrypted network protocol for initiating text-based shell sessions on remote systems. SSH allows a user to run commands on a machine’s terminal window without being physically present at the machine. SSH is similar to telnet. The difference being that SSH provides a secure channel over an insecure network.

In this exercise, you will use TigerVNC (a VNC app) and Putty (an SSH app) to remotely administer PLABKSRV01 - a Kali Linux device.

Exercise 2 - Exercise 2 - Verifying Port 80 for HTTP

Hypertext Transfer Protocol (HTTP) is an application level protocol that is used for transmitting web pages that contain a huge variety of data formats - from text, data, graphics and different multi-media content over the Internet. HTTP servers typically listen on TCP port 80 for any session requests from HTTP clients using popular web browsers such as Microsoft Internet Explorer (Edge), Mozilla Firefox, Google Chrome, Opera and Safari.

To get a better understanding of this technology, please refer to your course material or use your preferred search engine to research this topic in more detail.

You will use a new set of devices to meet the requirements of this lab exercise.

You will be working on the following equipment to carry out the steps defined in each exercise.

  • PLABDC01 (Windows Server 2008 - Domain Controller)
  • PLABGW01 (Windows Server 2008 - Server)
  • PLABWIN701 (Windows 7 - Workstation)

Exercise 3 - Verifying HTTPS Port 443

HTTPS, short for Hypertext Transfer Protocol Secure, is essentially HTTP with Secure Sockets Layer/Transport Layer Security (SSL/TLS) added for security. A computer certificate issued by a certification authority is bound to the web site with SSL/TLS enabled. The security feature helps prevent unauthorized access of information as data is encrypted when transmitted over a network. This is especially relevant to networks accessed over WANs, such as Internet. TCP reserves port #443 for the HTTPS protocol.

Exercise 4 - Verifying Port 139 for NetBIOS

Network Basic Input/Output System (NetBIOS) is service that supports communication among applications on different computers over Local Area Network. NetBIOS does not support communication on WANs. Software vendors like Microsoft use NetBIOS to run with TCP/IP (NetBT) where a computer is given a computer name and a numeric Internet Protocol (IP) address. NetBIOS is not a networking protocol as it relies on protocols like TCP/IP to make connectivity possible among network devices. Port #139 is reserved for NetBIOS protocol.

Exercise 5 - Contrast TCP and UDP Protocols

Transmission Control Protocol (TCP) is a session level protocol that prepares the connection between two networked devices. TCP uses well-known (fixed) port numbers to identify a service where clients can connect to. TCP is a connection-oriented protocol which guarantees delivery of data from source to destination.

User Datagram Protocol (UDP) is another session level protocol that functions like its counterpart - TCP. UDP however is a connectionless oriented protocol that sends data in small increments and does not guarantee its delivery from source to destination.

Comprehensive Learning

See the full benefits of our immersive learning experience with interactive courses and guided career paths.

Courses