THE FEDERAL POLYTECHNIC

BIDA, NIGER STATE

COMPUTER SCIENCE DEPARTMENT

ASSIGNMENT

ON:

DATA COMMUNICATION AND NETWORK

COURSE CODE: COM315

PREPARED BY:

GROUP 8

OLAREWAJU FRANCIS EMMANUEL

NWOSU VICTOR CHUKWUBUIKEM

ABUBAKAR ALIYU LIMAN

UZOMA VICTOR NNAEMEKA

ABUBAKAR ABDULRAHMAN

MUHAMMED ABUDULGAFAR OMEIZA

MUHAMMED ABDULKADIR ABDULSALAM

SULEIMAN USMAN SACHI

PETER JOHN AYEMOBA

DAVIES DANIE
SHEHU KABIRU

SUMBMITTED TO:

LECTURER: MR. OLAYEMI T.A

8.2 Explain the protocols and applications used in a small network.

A network protocol can be defined as a set of rules and standards that govern the communication and
data exchange between devices in a network or over the internet. Example: The Transmission Control
Protocol (TCP) is a network protocol that ensures reliable data transmission between devices by
breaking data into packets, numbering them, and reassembling them at the receiving end.

Network protocols can also refer to the specific methods and formats used for encoding, compressing,
or encrypting data during transmission to ensure secure and efficient communication. Example: The
Secure Sockets Layer (SSL) and its successor, Transport Layer Security (TLS), are network protocols that
provide secure communication between a client and a server, such as when accessing a website using
the "https" prefix.

In a broader context, network protocols can encompass the entire suite of protocols that work together
to enable various aspects of network functionality, such as addressing, routing, and error control.
Example: The Internet Protocol Suite (TCP/IP) is a collection of network protocols that govern how data
is transmitted, addressed, and routed across the internet. It includes protocols like TCP, IP, and Internet
Control Message Protocol (ICMP) for error reporting.

Network protocols support the applications services used by employees in a small network. For startup and small
business TCP and IP communication protocols are widely used easy to manage. For faster, more efficient file
transfer, your business may benefit from using FTP protocols instead of relying on HTTP alone. For security, HTTPS
is ubiquitous and reliable for data transfer over the network.

In a small network, several protocols and applications are used to ensure smooth communication and
functionality among devices. Here are some common ones and their explanations:

1. DHCP (Dynamic Host Configuration Protocol): DHCP is a protocol that automatically assigns IP
addresses to devices on a network. It simplifies the process of managing IP addresses and reduces the
need for manual configuration.

2. DNS (Domain Name System): DNS is a protocol that translates domain names (e.g.,
www.example.com) into IP addresses, which are required for devices to communicate on the internet. It
makes it easier for users to access websites and resources without having to remember their IP
addresses.
3. TCP/IP (Transmission Control Protocol/Internet Protocol): TCP/IP is a suite of protocols that govern
how data is transmitted between devices on a network or the internet. TCP ensures reliable data
transfer, while IP is responsible for addressing and routing data packets.

4. VLAN (Virtual Local Area Network): VLAN is a technology that allows devices on a network to be
grouped together and communicate as if they were connected to the same physical network segment.
This can be useful in small networks to separate traffic and improve performance.

5. SMB (Server Message Block): SMB is a network protocol used for sharing files, printers, and other
resources between devices on a network. It is commonly used in small networks to enable file sharing
and collaboration among users.

6. NTP (Network Time Protocol): NTP is a protocol that synchronizes the clocks of devices on a network
to maintain consistent and accurate time. This is important for various applications, such as logging
events or coordinating activities across multiple devices.

7. SNMP (Simple Network Management Protocol): SNMP is a protocol used for monitoring and
managing network devices, such as routers, switches, and servers. It allows network administrators to
collect performance data, troubleshoot issues, and configure devices remotely.

8. VPN (Virtual Private Network): A VPN is an application that creates a secure, encrypted connection
between devices on a network, even when they are connected to different networks or the internet. It is
often used in small networks to enable remote access to resources or to protect sensitive data during
transmission.

9. Firewall: A firewall is an application that monitors and controls incoming and outgoing network traffic
based on predefined security rules. It helps protect small networks from unauthorized access, malware,
and other security threats.
10. Antivirus Software: Antivirus software is an application that scans devices for known malware, such
as viruses, worms, and Trojans, and removes or quarantines them to protect the network from
infections.

These protocols and applications work together to ensure a small network operates efficiently, securely,
and reliably.
8.3. Explain how a small network severs as the basis of larger networks.

A small network is typically a localized collection of devices or nodes that are interconnected for the
purpose of communication and resource sharing. These networks usually serve a limited number of
users within a small geographical area, such as homes, small offices, or schools. Some examples of small
networks include: home network, school network etc

While A large network is a complex and extensive system that connects a significant number of devices
or nodes across a wide geographical area or multiple organizations. These networks often serve a
diverse group of users and require more advanced technologies, protocols, and management strategies
to ensure efficient communication and resource sharing. Some examples of large networks include:
enterprise network, cloud network, internet service provider (ISP) etc

A small network can serve as the basis for a larger network in several ways. Essentially, a small network
is a collection of interconnected devices or nodes, typically communicating and sharing resources within
a limited scope. When we talk about a larger network, we usually refer to a more extensive system that
connects a greater number of devices or nodes, often spanning across larger geographical areas or
organizations.

Here are some ways in which a small network can form the foundation for a larger network:

1. Scalability: A small network can be scaled up by adding more nodes, devices, or even other smaller
networks. The initial structure, protocols, and management principles used in the small network can be
applied and adapted to accommodate the growth.

2. Building Blocks: A small network can be considered as a building block for a larger network. The basic
concepts, such as connectivity, communication protocols, and network security, can be tested and
refined in a small network before being implemented in a larger scale.

3. Replication: A successful small network can serve as a model for creating similar networks. By
replicating the design, architecture, and management practices, it becomes easier to establish additional
networks with similar requirements and objectives.
4. Centralized Management: A small network can be managed centrally, and the same management
principles can be applied to larger networks. This centralized approach to managing networks can help
maintain consistency, security, and efficiency across the entire network infrastructure.

5. Standardization: A small network can help establish standards and best practices for larger networks.
By testing and implementing various technologies, protocols, and security measures in a small network,
organizations can determine the most effective and efficient solutions to adopt for their larger networks.

In summary, a small network can serve as the basis for a larger network by providing a foundation for
scalability, acting as building blocks, enabling replication, facilitating centralized management, and
promoting standardization. These aspects help ensure that the larger network is built upon proven and
reliable principles, allowing for efficient and effective communication and resource sharing across a
broader scope.
8.4 Explain common network troubleshooting methodologies.

Network troubleshooting is the process of identifying and resolving issues that affect the performance,
connectivity, or functionality of a network. There are several common methodologies and approaches to
network troubleshooting that help professionals diagnose and fix problems efficiently. Some of these
methodologies include:

1. The OSI Model: The Open Systems Interconnection (OSI) model is a widely-used framework for
understanding and troubleshooting network issues. It divides the network communication process
into seven layers, each representing a specific function or aspect of the communication. By working
through these layers systematically, technicians can identify and resolve issues at their source.

2. The Troubleshooting Steps: A systematic approach to troubleshooting involves following a series of

steps to isolate and resolve network issues. These steps often include:

a. Gather Information: Collect relevant information about the problem, such as when it occurs,
affected devices, and any error messages.

b. Reproduce the Issue: Attempt to recreate the problem to better understand its cause and identify
any patterns.

c. Isolate the Problem: Narrow down the possible causes by checking hardware, software, and network
configurations.

d. Test Theories: Develop hypotheses about potential causes and test them to determine which one is
most likely.

e. Implement Solutions: Once the root cause is identified, implement the appropriate fix or
workaround.

f. Verify and Document: Confirm that the issue has been resolved and document the process for future
reference.
3. The KISS Principle (Keep It Simple, Stupid): This approach emphasizes the importance of simplicity and
straightforwardness in troubleshooting. It suggests starting with the most basic and common
solutions before moving on to more complex ones. This method helps avoid unnecessary
complications and ensures that the most straightforward issues are addressed first.

4. The Divide-and-Conquer Method: This method involves breaking down the network into smaller
components and testing each one individually to identify the source of the problem. By dividing the
network into smaller sections, technicians can more easily pinpoint the issue and focus their
troubleshooting efforts on specific areas.

5. The Root Cause Analysis (RCA): RCA is a systematic approach to identifying the underlying cause of a
problem, rather than just addressing its symptoms. This methodology involves gathering data,
analyzing the information, and identifying the root cause, which can help prevent similar issues from
occurring in the future.

6. The ITIL Framework: The Information Technology Infrastructure Library (ITIL) is a set of best practices
for IT service management, including network troubleshooting. ITIL emphasizes the importance of
incident management, problem management, and continuous service improvement to ensure
efficient and effective resolution of network issues.

By utilizing these methodologies and maintaining a structured approach to troubleshooting, network

professionals can more effectively identify and resolve issues, ensuring optimal network performance
and connectivity.
8.5 list common connectivity problems associated as network devices.

1 Identify the affected area

2 Divide and conquer

3 Test the solution

4 Document the solution

The first step is to identify the problem by gathering information about what is not working. Users can be
interviewed, system logs can be reviewed, and network devices can be checked to help identify the issue

1 Identify the affected area: Once the problem is identified, the next step is to determine which area of the
network is affected. This could be a specific device, a particular subnet, or the entire network

2 Divide and conquer: Once the affected area is identified, the next step is to try to isolate the problem. This is
done by dividing the affected area into smaller sections and testing each section to determine where the issue is.

3 Test the solution: Once a solution is identified, it should be tested to ensure that it actually resolves the problem.
If the solution works, it can be implemented on a larger scale

4 Document the solution: Once the problem is resolved, it is important to document the solution so that it can be
referred to in the future if similar issues arise

These methodologies are not exhaustive but provide a starting point when dealing with network
troubleshooting. Depending on the specific issue, other methodologies or techniques may also be necessary to
resolve the problem.

1. Intermittent network problems

2. High bandwidth usage

3. High CPU usage

4. Physical connectivity issues.

5. Malfunctioning devices or equipment

6. D.N.S issues.

7. Interference in the wireless network.

8. Network congestion.

- what is the common problem or issue of computer network slow network speeds, wi-fi signals and damage are
just some of the most common network connection issues that IT department needs to troubleshoot.
Business is networks are complex, and many things can go wrong that disrupt network performance.

How to test network batency with ping and traceroute

Ping traceroute: - use the ping command with the –T Flag to perform a traceroute and identify the specific point
where latency is occurring. Type Ping –T < remote host IP address> in the command prompt or terminal. The
output will display the response time and the IP address of each router the ping passes through.

What is connectivity troubleshooting a network.

The term trouble shooting refer to the process of identifying problem with a network through a rigorous and
repeatable process and then solving these problems using testable methods.

Troubleshoot connectivity issues

Step1. Define the problem

2. Check physical connections

3. Restart devices.

4. Run network diagnostics

5. Check for software issues.

6. Monitor network traffic

7. Update firmware and software.