Cisco PIX 506e with multiple internal networks

Unanswered Question
May 26th, 2007

My configuration is not very complex, yet I'm not achieving the results I want.

Our 506e connects on the outside to a T1. On the inside interface, it plugs directly into a switch. Also plugged into the switch is another router which connects to another network. The IP's are as follows:

PIX Internal:

Router (Network A side):

Router (Network B side):

At present, Network A ( is able to access the internet through the PIX just fine. Network A is also able to communicate just fine with Network B. However, Network B is unable to access the internet (which it must do so via the PIX in Network A).

I'm not sure where to look, what to try, etc. Any hints to the direction I should look would be great.

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Amit Singh Sat, 05/26/2007 - 22:34


Its kinda hard to predict the topology that you have by expalantion, a brief topology diagram will help undertanding it clear.

Where and how is router B connected on the PIX.Does the router B also located on inside interface of the PIX.If yes, Have you tried adding a default route on router B towards the Pix inside interface. like

ip route

Also, try adding the reverse routes on the PIX for the ip subnets located on router B.


-amit singh

Jon Marshall Sun, 05/27/2007 - 02:39


I agree with Amit in that the most likely culprit is that the pix does not know how to get to the 192.168.1.x network.

Can you ping any 192.168.1.x addresses from the pix ?

If not try this on the pix

pix(config)# route inside



rick.olson Sun, 05/27/2007 - 08:25

I can indeed ping one of the servers on the 192.168.1.x network (it's 1.100) from the PIX. I can also, from that 1.100 server, ping the LAN side of the PIX. However beyond that it won't go.

When I try to go to a website, the status bar on the brower will say "Connecting to site x.x.x.x" but it will not go.

As for the topology, perhaps I can explain it a bit better.

We're implementing an MPLS network using AdTran routers at each site. For now, we're only working on two sites (site A and site B). Site A is our main site (192.168.4.x) and Site B is our remote site (192.168.1.x). The AdTran router at Site A is, and the PIX is 4.1.

At first I thought perhaps the AdTran router at Site A needed a routing entry for the PIX. Right now traffic comes in and it appears as if it hits one of our Windows Server 2003 machines that has RRAS installed (the only thing this RRAS machine is doing is creating a static route to the 192.168.1.x network).

I hope this helps....thanks for your suggestions so far.

Amit Singh Sun, 05/27/2007 - 08:41

I would like to check few things here :

1. What is the gateway set on the hosts that are on Site B.

2.What happens when you try to " tracert " from one of the PC in Site B.

3. Check if you have allowed the 192.168.1.x network on the PIX. i.e you are natting that address range on the PIX to access the interrnet.

4. Finally config from both the PIX and Site B routers would help.

HTH,Please rate if it does.

-amit singh

rick.olson Sun, 05/27/2007 - 09:30

Site B hosts are set for as their gateway (the AdTran router at the site). When we try a tracert from site B it hits the WAN side of the Site B router, the WAN side of the Site A router and then stops. It doesn't seem to even reach the PIX device, yet I can ping the PIX device from Site B just fine.

I don't have much experience using the command line for the PIX...all of my configurations have been using the PDM GUI. On the "Hosts/Networks" configuration screen for the "inside" interface I've added a Network object for the network. I've defined a static route of with metric of 2. For the NAT screen, I chose to use the same settings that the network uses which are: Address Pool ID of 1, and a Dynamic NAT using the WAN side of the PIX as the address.

NAT sort of confuses me, so I'm not quite sure if I've established the correct settings or not for it.

I should also mention that the AdTran routers for both Site A and Site B came pre-configured by Qwest.

Amit Singh Sun, 05/27/2007 - 09:38


Your router config's and routing part of PIX seems to be fine. As you are reaching the PIX and vice-versa. I think we need to check the PIX config finally. If you can get to the PIX CLI, please take the output of the PIX config and paste it here. Do the config

Config t

Show config


-amit singh


This Discussion