Project Report

Design & Implementation of a Secure Multi-Service Enterprise Network for NovaTech Ltd.

1. Introduction

This project focuses on designing and implementing a small enterprise network for NovaTech
Ltd. using Cisco Packet Tracer. The organization operates across two buildings, each containing
multiple departments with different networking requirements. The goal of this project is to ensure
full connectivity, efficient IP address allocation, and the implementation of essential network services
such as DHCP, DNS, Email, and NAT.

The network was developed without using VLANs, meaning each department was logically
separated through subnetting and physical segmentation rather than virtual LAN technology. This
approach simplifies the design while still maintaining functional isolation between departments.

The project follows the given requirements such as RIP v2 routing, centralized DHCP services,
DNS resolution, and email communication across departments.

2. Objective of the Project

The primary objective of this project is to design a functional enterprise-level network that
supports multiple departments across two buildings while ensuring:

 Efficient IP address allocation using VLSM

 Inter-network communication using RIP v2

 Automatic IP assignment using DHCP

 Name resolution through DNS

 Internal communication via Email server

 Internet simulation using NAT

3. Network Scenario Overview

NovaTech Ltd. consists of two buildings:

Building A
  HR Department

 Finance Department

 IT Department

 Server Room (DHCP, DNS, Email)

Building B

 Development Department

 Quality Assurance (QA) Department

The topology shows that each department is connected through switches, and both buildings
are interconnected using routers. A centralized server is placed in Building A to manage network
services.

4. Network Topology Design

The network topology is designed using a hierarchical approach:

 Access Layer: PCs connected to switches (department-wise)

 Distribution Layer: Switches connected to routers

 Core Layer: Router-to-router communication between buildings

The topology clearly separates departments physically, ensuring easier management and
troubleshooting.

📌 [Insert Screenshot: Full Network Topology Here]

5. IP Addressing and Subnetting (VLSM)

The network uses the IP block [Link]/22 as specified in the assignment.

Using VLSM, subnets were allocated based on departmental size:

 HR → Medium subnet

 Finance → Medium subnet

 IT → Small subnet
  Development → Large subnet

 QA → Medium subnet

 Server → Small subnet

From the screenshots (Page 1–2), example configurations include:

 HR Gateway: [Link] /27

 Finance Gateway: [Link] /27

 IT Gateway: [Link] /28

 Server Network: [Link] /28

📌 [Insert Screenshot: Subnetting Table or IP Plan Here]

6. Router Configuration and Interconnection

Two routers are used:

 Router A (Building A)

 Router B (Building B)

Each router is configured with appropriate interfaces connected to departmental switches.

A serial connection is used between Router A and Router B, enabling inter-building

📌 [Insert Screenshot: Router Configuration Commands Here]

7. Routing Protocol (RIP v2)

RIP version 2 is used as the dynamic routing protocol. It allows routers to exchange routing
information automatically.

Configuration includes:

 Enabling RIP

 Specifying version 2
  Disabling auto-summary

 Advertising network [Link]

As shown in Page 3 of the screenshots, RIP ensures communication between Building A and
Building B networks.

📌 [Insert Screenshot: RIP Configuration Here]

8. DHCP Configuration

A centralized DHCP server is implemented in the server room of Building A.

Multiple DHCP pools are created for different departments:

 HR Pool

 Finance Pool

 IT Pool

 Development Pool

 QA Pool

Each pool includes:

 Default Gateway

 DNS Server

 Start IP Address

 Subnet Mask

Example from screenshots (Page 5–6):

 HR Pool uses gateway [Link]

 DNS server is [Link]

Routers are configured with ip helper-address to forward DHCP requests across networks.

📌 [Insert Screenshot: DHCP Configuration Here]

The DNS server is configured to resolve domain names within the network.

Configured records include:

 [Link] → [Link]

 [Link] → [Link]

This allows users to access services using domain names instead of IP addresses.

📌 [Insert Screenshot: DNS Configuration Here]

10. Email Server Configuration

An email server is configured to enable communication between departments.

Features:

 SMTP enabled (for sending emails)

 POP3 enabled (for receiving emails)

 Domain: [Link]

User accounts created include:

 hr1

 dev1

 qa1

From the screenshots (Page 9–12), email communication was successfully tested where:

 Email sent from HR PC

 Email received at Development PC

📌 [Insert Screenshot: Email Setup Here]

📌 [Insert Screenshot: Email Sending & Receiving Here]

Static NAT is configured on Router B to allow internal users to access external networks.

 Inside Local IP mapped to Public IP

 Public IP used: [Link] (as per requirement)

From Page 13, NAT configuration ensures external communication capability.

📌 [Insert Screenshot: NAT Configuration Here]

12. Network Testing and Verification

Several tests were conducted to ensure proper functionality:

1. Connectivity Test

Ping tests confirm that all devices can communicate across networks.

2. DNS Test

Domain names successfully resolve to IP addresses.

3. RIP Routing Test

Devices in Building A successfully communicate with Building B.

From screenshots (Page 14–16), ping results show:

 0% packet loss

 Successful inter-building communication

📌 [Insert Screenshot: Ping Test Results Here]

13. Observations

The network successfully meets all project requirements:

 All departments are connected without VLAN implementation

 DHCP simplifies IP management

 DNS improves usability

 Email service enables internal communication

 NAT allows external connectivity

The design is simple yet effective, suitable for small-to-medium enterprise environments.

14. Conclusion

This project demonstrates a complete enterprise network implementation using Cisco Packet
Tracer. The design ensures scalability, reliability, and efficient resource utilization. Even without
VLANs, the network performs effectively using subnetting and routing techniques.

The integration of multiple services such as DHCP, DNS, Email, and NAT reflects real-world
networking practices. This project enhances practical understanding of network design and
configuration, which is essential for both academic and professional purposes.

15. References

 Cisco Packet Tracer Documentation

 Course Materials

 Assignment Brief