Problem with NAT When Adding New Network to Firewall
Posted on 2014-04-15
I just set up a new interface on our ASA 5505 firewall (with security plus) to join another new network. I gave the firewall interface an IP address on the new network and am using a NAT to translate a workstation from the existing network to the new network.
I have set up the NAT, routing, etc. and I can ping devices on the new network fine. On the new network, I can ping up to the firewall interface. However, I cannot ping the workstation.
10.45.0.248 = Workstation (existing network)
10.8.47.20 = Firewall Interface (new network)
10.8.47.21 = Workstation NAT (new network) 10.8.47.21 -> 10.45.0.248
If I run a traceroute to 10.8.47.20, I can follow all the routers up to the firewall interface. When I traceroute 10.8.47.21, the route stops at the router (new network) just prior to the firewall interface.
From my inside server (on existing network), I can ping the new workstation (on new network) fine.
From the workstation, I cannot ping the inside server. I can ping up to the firewall interface. When I try to ping the outside address NAT address on the workstation, I dont see any traffic hitting the firewall at all. I see it right away when I ping the firewall interface.
Is it possible that somehow the new network cannot find the NAT address 10.8.47.21?