[CCNAv6 S2] 9.3.1.4 Packet Tracer - Verifying and Troubleshooting NAT Configurations



Packet Tracer – Verifying and Troubleshooting NAT Configurations
Addressing Table

Objectives

Part 1: Isolate Problems

Part 2: Troubleshoot NAT Configuration

Part 3: Verify Connectivity

Scenario

A contractor restored an old configuration to a new router running NAT. But, the network has changed and a new subnet was added after the old configuration was backed up. It is your job to get the network working again.

Part 1:     Isolate Problems
Ping Server1 from PC1, PC2, L1, L2, and R2. Record the success of each ping. Ping any other machines as needed.

Part 2:     Troubleshoot NAT Configuration
Step 1:     View the NAT translations on R2.

If NAT is working, there should be table entries.

Step 2:     Show the running configuration of R2.

The NAT inside port should align with the private address, while the NAT outside port should align with the public address.

Step 3:     Correct the Interfaces.

Assign the ip nat inside and ip nat outside commands to the correct ports.

Step 4:     Ping Server1 from PC1, PC2, L1, L2, and R2.

Record the success of each ping. Ping any other machines as needed.

Step 5:     View the NAT translations on R2.

If NAT is working, there should be table entries.

Step 6:     Show Access-list 101 on R2.

The wildcard mask should encompass both the 10.4.10.0 network and the 10.4.11.0 network.

Step 7:     Correct the Access-list.

Delete access-list 101 and replace it with a similar list that is also one statement in length. The only difference should be the wildcard.

Part 3:     Verify Connectivity
Step 1:     Verify connectivity to Server1.

Record the success of each ping. All hosts should be able to ping Server1, R1, and R2. Troubleshoot if the pings are not successful.

Step 2:     View the NAT translations on R2.

NAT should display many table entries.



 Configuration R2:

enable
configure terminal
interface Serial0/0/0
 no ip nat inside
 ip nat outside
interface Serial0/0/1
 no ip nat outside
 ip nat inside
 exit
no access-list 101 permit ip 10.4.10.0 0.0.0.255 any
access-list 101 permit ip 10.4.10.0 0.0.1.255 any
end
write memory
!


END !~!


Nhận xét

Đăng nhận xét

Bài đăng phổ biến từ blog này

[CCNAv6 S4] 8.2.4.14 Packet Tracer - Troubleshooting Enterprise Networks 3

Hình ảnh
Packet Tracer – Troubleshooting Enterprise Networks 3 Addressing Table Background This activity uses a variety of technologies you have encountered during your CCNA studies, including routing, port security, EtherChannel, DHCP, NAT, PPP, and Frame Relay. Your task is to review the requirements, isolate and resolve any issues, and then document the steps you took to verify the requirements. Note: This activity begins with a partial score. Requirements DHCP ·         R1 is the DHCP server for the R1 LAN. Switching Technologies ·         Port security is configured to only allow PC1 to access S1's F0/3 interface. All violations should disable the interface. ·         Link aggregation using EtherChannel is configured on S2, S3, and S4. Routing ·         All routers are configured with OSPF process ID 1 and no routing updates should be sent across interfaces that do n...
Đọc thêm

[CCNAv6 S2] 2.2.2.4 Packet Tracer - Configuring IPv4 Static and Default Routes

Hình ảnh
Packet Tracer - Configuring IPv4 Static and Default Routes Addressing Table Objectives Part 1: Examine the Network and Evaluate the Need for Static Routing Part 2: Configure Static and Default Routes Part 3: Verify Connectivity Background In this activity, you will configure static and default routes. A static route is a route that is entered manually by the network administrator to create a reliable and safe route. There are four different static routes that are used in this activity: a recursive static route, a directly attached static route, a fully specified static route, and a default route. Part 1:     Examine the Network and Evaluate the Need for Static Routing a.     Looking at the topology diagram, how many networks are there in total? b.    How many networks are directly connected to R1, R2, and R3? c.     How many static routes are required by each router to reach networks that are not directly ...
Đọc thêm

[CCNAv6 S2] 7.3.2.4 Packet Tracer - Troubleshooting Standard IPv4 ACLs

Hình ảnh
Packet Tracer – Troubleshooting Standard IPv4 ACLs Addressing Table Objectives Part 1: Troubleshoot ACL Issue 1 Part 2: Troubleshoot ACL Issue 2 Part 3: Troubleshoot ACL Issue 3 Scenario This network is meant to have the following three policies implemented: ·         Hosts from the 192.168.0.0/24 network are unable to access network 10.0.0.0/8. ·         L3 can’t access any devices in network 192.168.0.0/24. ·         L3 can’t access Server1 or Server2. L3 should only access Server3. ·         Hosts from the 172.16.0.0/16 network have full access to Server1, Server2 and Server3. Note: All FTP usernames and passwords are “cisco”. No other restrictions should be in place. Unfortunately, the rules that have been implemented are not working correctly. Your task is to find and fix the errors related to the access lists on R1. Part 1:     Troublesh...
Đọc thêm