Below is a simple network architecture and step-by-step connection guide for the configuration
you provided.
1. Recommended Network Architecture
Use this basic small-office network design:
Internet / ISP
|
ISP Gateway Router
[Link]
|
g0/1 - Outside
Cisco Router R1
g0/0 - Inside
[Link]/24
|
Switch SW1
--------------------------------
| | |
PC1 PC2 Server
DHCP Client DHCP Client Static/DHCP
2. IP Address Plan
Device Interface IP Address Purpose
R1 Router G0/0 [Link]/24 LAN gateway
R1 Router G0/1 [Link]/24 WAN/ISP side
ISP Gateway LAN side [Link]/24 Default route next-hop
PC1 NIC DHCP LAN client
PC2 NIC DHCP LAN client
Server NIC [Link]/24 or DHCP Internal server
3. Physical Connection Steps
Step 1: Connect router to switch
Connect:
Router R1 G0/0 ---> Switch SW1 Fa0/1 or G0/1
Use a straight-through Ethernet cable.
Step 2: Connect PCs to switch
Connect:
PC1 FastEthernet0 ---> Switch Fa0/2
PC2 FastEthernet0 ---> Switch Fa0/3
Server NIC ---> Switch Fa0/4
Step 3: Connect router to ISP gateway
Connect:
Router R1 G0/1 ---> ISP Gateway / Internet Router
Use a straight-through Ethernet cable.
4. Router Configuration Step by Step
Step 1: Enter privileged and configuration mode
Router> enable
Router# configure terminal
Step 2: Configure LAN interface G0/0
This interface connects to the switch and acts as the default gateway for LAN devices.
Router(config)# interface gigabitEthernet 0/0
Router(config-if)# ip address [Link] [Link]
Router(config-if)# no shutdown
Router(config-if)# exit
Step 3: Configure WAN interface G0/1
This interface connects to the ISP gateway.
Router(config)# interface gigabitEthernet 0/1
Router(config-if)# ip address [Link] [Link]
Router(config-if)# no shutdown
Router(config-if)# exit
Step 4: Configure default route
This tells the router to send unknown traffic to the ISP gateway.
Router(config)# ip route [Link] [Link] [Link]
5. Configure DHCP Server on Router
The router will automatically give IP addresses to PCs.
Router(config)# ip dhcp excluded-address [Link] [Link]
Router(config)# ip dhcp pool LAN
Router(dhcp-config)# network [Link] [Link]
Router(dhcp-config)# default-router [Link]
Router(dhcp-config)# dns-server [Link]
Router(dhcp-config)# exit
The excluded address range protects important static IPs such as the router, server, printer, or
access point.
6. Configure NAT Overload / PAT
NAT allows many LAN devices to access the internet using the router’s outside IP address.
Step 1: Create ACL for LAN network
Router(config)# access-list 1 permit [Link] [Link]
Step 2: Mark LAN interface as NAT inside
Router(config)# interface gigabitEthernet 0/0
Router(config-if)# e
Router(config-if)# exit
Step 3: Mark WAN interface as NAT outside
Router(config)# interface gigabitEthernet 0/1
Router(config-if)# ip nat outside
Router(config-if)# exit
Step 4: Enable NAT overload
Router(config)# ip nat inside source list 1 interface gigabitEthernet 0/1
overload
7. Save Configuration
Router(config)# end
Router# write memory
or
Router# copy running-config startup-config
8. PC Configuration
On each PC:
1. Open the PC network settings.
2. Select DHCP.
3. The PC should receive an IP address like:
IP Address: 192.168.10.x
Subnet Mask: [Link]
Default Gateway: [Link]
DNS Server: [Link]
9. Verification Commands
Check router interfaces
Router# show ip interface brief
Expected result:
GigabitEthernet0/0 [Link] up up
GigabitEthernet0/1 [Link] up up
Check DHCP bindings
Router# show ip dhcp binding
This shows IP addresses assigned to PCs.
Check routing table
Router# show ip route
You should see:
S* [Link]/0 [1/0] via [Link]
C [Link]/24 is directly connected
C [Link]/24 is directly connected
Check NAT translations
Router# show ip nat translations
Check NAT statistics
Router# show ip nat statistics
10. Testing Connectivity
From PC1, test router gateway
ping [Link]
If successful, PC-to-router LAN connection is working.
From router, test ISP gateway
Router# ping [Link]
If successful, router-to-ISP connection is working.
From PC1, test outside network
ping [Link]
If successful, NAT and routing are working.
Test DNS
ping [Link]
If IP ping works but domain ping fails, the issue is DNS.
11. Full Router Configuration Example
enable
configure terminal
hostname R1
interface gigabitEthernet 0/0
description LAN connection to switch
ip address [Link] [Link]
ip nat inside
no shutdown
exit
interface gigabitEthernet 0/1
description WAN connection to ISP
ip address [Link] [Link]
ip nat outside
no shutdown
exit
ip dhcp excluded-address [Link] [Link]
ip dhcp pool LAN
network [Link] [Link]
default-router [Link]
dns-server [Link]
exit
access-list 1 permit [Link] [Link]
ip nat inside source list 1 interface gigabitEthernet 0/1 overload
ip route [Link] [Link] [Link]
end
write memory
12. Troubleshooting Guide
Problem Possible Cause Solution
DHCP not configured or Check show ip dhcp binding and show
PC does not get IP address
interface down ip interface brief
PC cannot ping Cable, switch port, or router Check cable and make sure G0/0 is
[Link] LAN issue up/up
Router cannot ping
WAN interface issue Check G0/1 IP, cable, and ISP gateway
[Link]
PC can ping router but not Missing default route or
Check show ip route and NAT config
internet NAT
PC can ping [Link] but not
DNS issue Check DHCP DNS server setting
[Link]
Wrong inside/outside Verify ip nat inside on G0/0 and ip
NAT not working
interfaces nat outside on G0/1
13. Final Connection Checklist
Before testing, confirm:
[ ] Router G0/0 connected to switch
[ ] Router G0/1 connected to ISP gateway
[ ] PCs connected to switch
[ ] G0/0 has IP [Link]/24
[ ] G0/1 has IP [Link]/24
[ ] DHCP pool configured
[ ] NAT inside configured on G0/0
[ ] NAT outside configured on G0/1
[ ] Default route points to [Link]
[ ] PCs receive DHCP addresses
[ ] PC can ping [Link]
[ ] PC can ping [Link]
This architecture gives you a working LAN with DHCP, internet access through NAT/PAT, and a
default route to the ISP.
Network Configuration & Troubleshooting
1. What is Network Configuration?
Network configuration is the process of setting up network devices such as routers, switches,
firewalls, servers, and computers so they can communicate with each other and access network
resources.
Common Network Configuration Tasks
Assigning IP addresses
Configuring subnet masks
Setting default gateways
Configuring DNS servers
Creating VLANs
Configuring routing protocols
Setting up DHCP
Configuring NAT (Network Address Translation)
Implementing security policies and ACLs
Example Configuration
Parameter Value
IP Address [Link]
Subnet Mask [Link]
Default Gateway [Link]
DNS Server [Link]
2. What is Network Troubleshooting?
Network troubleshooting is the systematic process of identifying, analyzing, and resolving network
issues that affect connectivity, performance, or security.
Common Network Problems
No Internet access
IP address conflicts
Slow network performance
DNS resolution failures
VLAN communication issues
Routing problems
DHCP failures
Physical cable faults
Firewall blocking traffic
Network Troubleshooting Methodology
Step 1: Identify the Problem
Gather information:
What is not working?
When did the issue start?
Is it affecting one user or many users?
Were any changes recently made?
Example:
Users cannot access the Moodle LMS server.
Step 2: Check Physical Connectivity
Verify:
Network cables
Switch port status
Router interfaces
Power status
Cisco Commands:
show interfaces status
show ip interface brief
Expected Output:
GigabitEthernet0/0 up up
GigabitEthernet0/1 up up
Step 3: Verify IP Configuration
Windows:
ipconfig /all
Linux:
ip addr
Cisco:
show ip interface brief
Check:
IP Address
Subnet Mask
Default Gateway
DNS Server
Step 4: Test Connectivity
Ping Test
ping [Link]
Purpose:
Verify Layer 3 connectivity.
Results:
Reply from [Link]
or
Request Timed Out
Traceroute Test
Windows:
tracert [Link]
Linux/Cisco:
traceroute [Link]
Purpose:
Identify where traffic stops.
Step 5: Verify DNS Resolution
Test:
nslookup [Link]
Expected:
Server: [Link]
Name: [Link]
Address: 142.250.x.x
Step 6: Check Routing
Cisco Commands:
show ip route
Verify:
Connected routes
Static routes
Default route
Example:
S* [Link]/0 via [Link]
Step 7: Verify DHCP
Cisco Commands:
show ip dhcp binding
show ip dhcp pool
Check:
Available addresses
Assigned addresses
DHCP conflicts
Step 8: Check VLAN Configuration
Cisco Commands:
show vlan brief
show interfaces trunk
Verify:
Correct VLAN assignment
Trunk links operational
Step 9: Verify NAT
Cisco Commands:
show ip nat translations
show ip nat statistics
Check:
Internal IP translation
Public IP mapping
Cisco Troubleshooting Commands Cheat Sheet
Command Purpose
show running-config View current configuration
show startup-config View saved configuration
show ip interface brief Check interface status
show interfaces Detailed interface information
show ip route Routing table
show arp ARP table
show vlan brief VLAN information
show interfaces trunk Trunk status
show mac address-table MAC table
show ip dhcp binding DHCP leases
show ip nat translations NAT entries
Command Purpose
ping Connectivity test
traceroute Path analysis
debug ip packet Advanced troubleshooting
OSI-Based Troubleshooting Approach
Layer 1 – Physical
Check:
Power
Cable
Port LEDs
Fiber modules
Layer 2 – Data Link
Check:
VLAN configuration
MAC address table
Trunk links
STP status
Commands:
show mac address-table
show spanning-tree
Layer 3 – Network
Check:
IP addresses
Routing
NAT
ACLs
Commands:
show ip route
show access-lists
Layer 4-7 – Transport/Application
Check:
DNS
HTTP/HTTPS
Application services
Firewalls
Commands:
telnet server_ip 80
nslookup [Link]
Real-World Example
Problem
Students cannot access Moodle.
Troubleshooting Steps
1. Ping Moodle Server
ping [Link]
2. Verify Server Status
show ip interface brief
3. Check VLAN
show vlan brief
4. Verify Routing
show ip route
5. Verify Firewall Rules
6. Check DNS
nslookup [Link]
Resolution
Incorrect default gateway configured on Moodle server.
Gateway corrected to:
[Link]
Connectivity restored.
Best Practices
Document all network changes.
Use consistent IP addressing schemes.
Back up device configurations regularly.
Monitor bandwidth and device health.
Implement network redundancy.
Test changes in a lab environment before production deployment.
Follow a structured troubleshooting methodology (OSI or Top-Down).
Key Principle: Troubleshoot from the simplest causes first (cables, interfaces, IP settings) before
moving to complex issues (routing, NAT, firewall, applications).
===================================
Network Configuration & Troubleshooting
1. Network Configuration
Network configuration is the process of setting up network devices (routers, switches, firewalls,
servers, and PCs) so they can communicate correctly.
Basic Configuration Tasks
Configure IP Address on a Cisco Router
Router> enable
Router# configure terminal
Router(config)# interface gigabitEthernet 0/0
Router(config-if)# ip address [Link] [Link]
Router(config-if)# no shutdown
Router(config-if)# exit
Router(config)# end
Router# write memory
Configure Default Route
Router(config)# ip route [Link] [Link] [Link]
Configure DHCP Server
Router(config)# ip dhcp pool LAN
Router(dhcp-config)# network [Link] [Link]
Router(dhcp-config)# default-router [Link]
Router(dhcp-config)# dns-server [Link]
Configure NAT Overload (PAT)
Router(config)# access-list 1 permit [Link] [Link]
Router(config)# interface g0/0
Router(config-if)# ip nat inside
Router(config)# interface g0/1
Router(config-if)# ip nat outside
Router(config)# ip nat inside source list 1 interface g0/1 overload
2. Network Troubleshooting Methodology
Step 1: Identify the Problem
Ask:
What is not working?
One user or all users?
LAN issue or Internet issue?
When did it start?
Step 2: Gather Information
Check:
IP Configuration
Windows:
ipconfig /all
Linux:
ip addr
Cisco:
show ip interface brief
Step 3: Test Connectivity
Ping Tests
Localhost
ping [Link]
Default Gateway
ping [Link]
Internet IP
ping [Link]
DNS Resolution
ping [Link]
Results:
Test Meaning
Localhost fails TCP/IP problem
Gateway fails LAN problem
Internet IP fails Routing/NAT issue
DNS name fails DNS issue
Step 4: Trace the Path
Windows:
tracert [Link]
Linux:
traceroute [Link]
Step 5: Check Router
show ip route
show interfaces
show running-config
show ip nat translations
show ip nat statistics
Step 6: Check Switch
show interfaces status
show vlan brief
show mac address-table
show spanning-tree
3. Common Network Problems
Problem 1: Interface Down
Check:
show ip interface brief
Fix:
interface g0/0
no shutdown
Problem 2: Wrong IP Address
Check:
ipconfig
Correct:
IP Address
Subnet Mask
Default Gateway
Problem 3: VLAN Mismatch
Check:
show vlan brief
Assign VLAN:
interface fa0/1
switchport mode access
switchport access vlan 10
Problem 4: DHCP Not Working
Check:
show ip dhcp binding
show ip dhcp pool
Verify:
DHCP pool exists
Network statement correct
Interface up
Problem 5: NAT Not Working
Check:
show ip nat translations
show ip nat statistics
Verify:
Inside/Outside interfaces configured
ACL permits LAN subnet
Overload command configured
4. Troubleshooting Commands Cheat Sheet
Router
show running-config
show startup-config
show ip route
show ip interface brief
show interfaces
show version
Switch
show vlan brief
show interfaces status
show mac address-table
show spanning-tree
PC
ipconfig /all
ping
tracert
nslookup
arp -a
Example Troubleshooting Scenario
Problem: Users cannot access the Internet.
Checklist
1. Verify PC IP
ipconfig
2. Ping Gateway
ping [Link]
3. Check Router Interface
show ip interface brief
4. Verify Route
show ip route
5. Verify NAT
show ip nat translations
6. Test Internet
ping [Link]
7. Check DNS
nslookup [Link]
Following this sequence isolates whether the issue is Layer 1 (cabling), Layer 2 (switching/VLAN),
Layer 3 (routing), NAT, or DNS.