ITM 301 – Business Data Communication
Multi-Router Enterprise Network Simulation Project
Student Name: Bassem Hoteit
Student ID: 202307313
Student Name Karim Akkewe
student id
Instructor: Ayman Khalil
1. Project Overview
This project consists of designing, configuring, and testing a multi-router enterprise network in
Cisco Packet Tracer.
The network simulates a small organization composed of several LANs, two servers, and
multiple interconnected routers running RIP version 2.
The goals of the project were to:
•
Build a functioning network with 5 routers, 2 switches, 6 PCs, and 2 servers.
•
Implement static IP addressing on all devices.
•
Configure RIP v2 routing across all routers.
•
Ensure full connectivity between all end devices across all subnets.
•
Configure a DNS server and provide a working URL (www. i t m301. c om).
•
Implement Static NAT on Router 2 to allow internal LAN access to the web server.
•
Demonstrate and verify successful connectivity using ping and nslookup.
This project demonstrates practical skills in routing, subnetting, NAT, server configuration, and
network troubleshooting.
2. Tools and Technologies
The project uses the following technologies:
Tool / Feature
Purpose
Cisco Packet Tracer
8.x
Network simulation environment
RIP Version 2
Dynamic routing between routers
Static NAT
Mapping internal web server to a public IP
DNS Server
Domain name resolution for the internal website
HTTP Server
Hosting the ITM301 webpage
PC Command Prompt Connectivity testing: pi ng, ns l ook up
This setup mimics real-world enterprise networks where routing, NAT, and DNS must work
together to ensure reliable communication.
3. Network Topology
The network is composed of:
•
Router0 (Left LAN gateway)
•
Router5 (Core router, links all routers)
•
Router2 (Right LAN gateway, NAT router)
•
Router3 (Server network gateway)
•
RouterX (Additional router depending on your layout)
Two main LANs exist:
Left LAN
Contains three PCs (PC0, PC1, PC2) connected through Switch0.
Gateway: 71.71.1.2
Right LAN
Contains PCs (PC3, PC4, PC5) and Server1 through Switch1.
Gateway: 192.168.2.1
Server Network
Server0 hosts the web page and DNS.
Gateway: 91.91.1.1
All routers connect using serial/copper links with appropriate interfaces enabled.
4. Addressing Scheme
Router LAN Interfaces
Router Interface IP Address
Purpose
Router0 Fa0/0
71.71.1.2
Left LAN gateway
Router5 Gi0/0
61.61.1.1
Core router link
Router2 Gi0/0
192.168.2.1 Right LAN gateway
Router3 Gi0/1
91.91.1.1
Server network gateway
Servers
Server
IP
Server0 (DNS + Web) 91.91.1.2
Subnet Gateway
/24
Server1 (Internal Web) 192.168.2.201 /24
91.91.1.1
DNS
91.91.1.2
192.168.2.1 91.91.1.2
PCs
PCs in each LAN received correct IP → Gateway → DNS according to their network.
5. Routing Configuration (RIP v2)
Each router was configured with:
r out er r i p
v er s i on 2
no aut o- s ummar y
net wor k <eac h c onnec t ed net wor k >
Example from Router5:
r out er r i p
v er s i on 2
no aut o- s ummar y
net wor k 71. 71. 1. 0
net wor k 81. 81. 1. 0
net wor k 61. 61. 1. 0
After configuration, the command:
s how i p r out e
confirmed that all routers successfully learned all remote networks.
6. NAT Configuration (Router2)
Static NAT was required so LAN users could reach the Web Server.
Example NAT rule:
i p nat i ns i de s our c e s t at i c 192. 168. 2. 201 91. 91. 1. 2
Interfaces were configured:
i nt
i p
i nt
i p
g0/ 0
nat i ns i de
g0/ 1
nat out s i de
This correctly mapped the internal server 192.168.2.201 → public-facing IP 91.91.1.2.
7. DNS Configuration
On Server0 → Services → DNS, the following entry was added:
Name
www.itm301.com
Type
Address
A Record 192.168.2.201
DNS Service was turned ON.
8. Connectivity Testing
8.1 Ping Tests
All devices successfully reached:
•
Their own gateway
•
Remote LANs
•
DNS server
•
Web server
Example:
C: \ > pi ng 91. 91. 1. 1
Repl y f r om 91. 91. 1. 1:
by t es =32 t i me<1ms TTL=254
8.2 Website Access
Opening the browser on PC3:
ht t p: / / www. i t m301. c om
successfully displayed the hosted webpage on Server1.
8.3 DNS Resolution
C: \ > ns l ook up www. i t m301. c om
Ser v er : 192. 168. 2. 201
Addr es s : 192. 168. 2. 201
Name: www. i t m301. c om
Addr es s : 192. 168. 2. 201
DNS timeout issue was fixed by correctly setting DNS server and ensuring routing was complete.
9. Challenges and Troubleshooting
Several issues occurred during the project:
Interface Down Issues
•
GigabitEthernet links not coming up
•
Incorrect cable types (fixed using copper cross-over or straight-through)
RIP Not Advertising Networks
•
Missing network statements
•
Incorrect subnet masks
DNS Timeout
•
DNS server IP mismatch
•
NAT misconfiguration causing unreachable DNS
NAT Failure
•
Inside/outside interfaces reversed
•
Incorrect static NAT syntax
All problems were resolved through systematic troubleshooting using:
•
s how i p i nt er f ac e br i ef
•
s how i p r out e
•
s how r unni ng- c onf i g
•
Packet Tracer simulations
10. Advantages and Learning Outcomes
This project strengthened understanding of:
•
Multi-router topologies
•
Dynamic routing with RIP v2
•
NAT and public/private addressing
•
DNS operation
•
Proper server configuration
•
Enterprise troubleshooting workflow
It also built strong hands-on skills in designing and deploying real networks.
11. Conclusion
This network simulation demonstrates a complete small-scale enterprise network containing
routing, NAT, DNS, and server communication. The final network provides:
•
Full end-to-end connectivity
•
Successful domain name resolution
•
Working website access via NAT
•
Verified routing between all routers
The project shows readiness for larger-scale networking designs and provides a strong
foundation for advanced concepts such as OSPF, DHCP, VLANs, ACLs, and network security.