Greetings, and welcome to Seeseenayy.
Packet Tracer Details: This packet tracer asks us to configure Static NAT on a router.
Below you will find a download of the completed packet tracer file. It is recommended that you read the tutorial or so.
Tutorial/Walk-Through
Follow these steps to configure static NAT:
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.
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.
---
First, you must set the NAT configuration for the server's inside and outside/global IP:
R1 Configuration
R1>enable
R1#conf t
R1(config)#ip nat inside source static 172.16.16.1 64.100.50.1
Then, designate your interfaces as inside or outside. After this you should be at 100%
R1(config)#int s0/0/0
R1(config-if)#ip nat outside
R1(config-if)#exit
R1(config)#int g0/0
R1(config-if)#ip nat inside
Packet Tracer Details: This packet tracer asks us to configure Static NAT on a router.
Below you will find a download of the completed packet tracer file. It is recommended that you read the tutorial or so.
Download(s)
Tutorial/Walk-Through
Follow these steps to configure static NAT:
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.
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.
---
First, you must set the NAT configuration for the server's inside and outside/global IP:
R1 Configuration
R1>enable
R1#conf t
R1(config)#ip nat inside source static 172.16.16.1 64.100.50.1
Then, designate your interfaces as inside or outside. After this you should be at 100%
R1(config)#int s0/0/0
R1(config-if)#ip nat outside
R1(config-if)#exit
R1(config)#int g0/0
R1(config-if)#ip nat inside
0 comments:
Post a Comment