[CCNAv6 S2] 9.2.1.4 Packet Tracer - Configuring Static NAT



Packet Tracer – Configuring Static NAT
Objectives

Part 1: Test Access without NAT

Part 2: Configure Static NAT

Part 3: Test Access with NAT

Scenario

In IPv4 configured networks, clients and servers use private addressing. Before packets with private addressing can cross then Internet, they need to be translated to public addressing. Servers that are accessed from outside the organization are usually assigned both a public and a private static IP address. In this activity, you will configure static NAT so that outside devices can access and inside server at its public address.

Part 1:     Test Access without NAT
Step 1:     Attempt to connect to Server1 using Simulation Mode.

a.     From PC1 or L1, attempt to connect to the Server1 web page at 172.16.16.1. Use the Web Browser to browse Server1 at 172.16.16.1. The attempts should fail.

b.    From PC1, ping the R1 S0/0/0 interface. The ping should succeed.

Step 2:     View R1 routing table and running-config.

a.     View the running configuration of R1. Note that there are no commands referring to NAT.

b.    Verify that the routing table does not contain entries referring to the IP addresses used by PC1 and L1.

c.     Verify that NAT is not being used by R1.

R1# show ip nat translations
Part 2:     Configure Static NAT
Step 1:     Configure static NAT statements.

Refer to the Topology. Create a static NAT translation to map the Server1 inside address to its outside address.

Step 2:     Configure interfaces.

Configure the correct inside and outside interfaces.

Part 3:     Test Access with NAT
Step 1:     Verify connectivity to the Server1 web page.

a.     Open the command prompt on PC1 or L1, attempt to ping the public address for Server1. Pings should succeed.

b.    Verify that both PC1 and L1 can now access the Server1 web page.

Step 2:     View NAT translations.

Use the following commands to verify the static NAT configuration:

show running-config
show ip nat translations
show ip nat statistics




Configuration R1:

enable
configure terminal
ip nat inside source static 172.16.16.1 64.100.50.1
interface g0/0
 ip nat inside
interface s0/0/0
 ip nat outside
 end
write memory
!

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