Ticket 14 NAT ACL
TROUBLE TICKET STATEMENT:
The implementation group has been using the test bed to do a ‘proof-of-concept’ that required both client 1 and client 2 to access the Web Server at 209.65.200.241. After several changed to interface status, network addressing, routing schemes and layer 2 connectivity, at trouble ticket has been opened indicating that client 1 cannot ping the 209.65.200.241 (internet Server).
The following information should be shown run by yourself to get:
#
Configuration on R1
ip nat inside source list nat_pool interface Serial0/0/0/1 overload!
ip access-list standard nat_pool
permit 10.1.0.0
!
interface Serial0/0/0/1
ip address 209.65.200.224 255.255.255.252
ip nat outside
!
interfaceSerial0/0/0/0.12
ip address 10.1.1.1 255.255.255.252
ip nat inside
ip ospf message-digest-key 1 md5 TSHOOT
ip ospd authentication message-digest
#
On Which device is the fault condition located?
A . R1
B . R2
C . R3
D . R4
E . DSW1
F . DSW2
G . ASW1
Answer: A
Explanation:
Clients 1 and 2 belong in the 10.2.0.0 subnet, as if you observe the NAT configuration you will notice that only 10.1.0.0 are specified in the NAT pool. Clients 1 and 2 are not being translated when they should be. The problem is with the NAT configuration on R1.
Leave a Reply