(Ticket 5: NAT ACL)
Scenario: The implementation group has been using the test bed to do a 'proof-of-concept' that requires both Client 1 and Client 2 to access the WEB Server at 209.65.200.241. After several changes to the network addressing, routing schemes, DHCP services, layer 2 connectivity, FHRP services, and, device security, a trouble ticket has been opened indicating that Client 1 cannot ping the 209.65.200.241 address.

Figure 1

Figure 2
Trouble Ticket Statement
Client 1 and Client 2 are not able to reach the WebServer at 209.65.200.241. Initial troubleshooting shows that DSW1, DSW2 and all the routers are able to reach the WebServer
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
The Fault Condition is related to which technology?