Can't speak to remote network

I have an internal PIX deployed. The untrusted side is
The trusted side is

There is another network on the untrusted side ( which the users need access too. If I ping from the outside interface, there is connectivity. If I ping from the inside interface, there is not connectivity. Logs do not show any ACls denying anything.  From the hosts side, they can ping anything on, but not


PIX Version 6.3(5)
interface ethernet0 auto
interface ethernet1 auto
nameif ethernet0 outside security0
nameif ethernet1 inside security100
fixup protocol dns maximum-length 512
fixup protocol ftp 21
fixup protocol h323 h225 1720
fixup protocol h323 ras 1718-1719
fixup protocol http 80
fixup protocol ils 389
fixup protocol rsh 514
fixup protocol rtsp 554
fixup protocol sip 5060
fixup protocol sip udp 5060
fixup protocol skinny 2000
fixup protocol smtp 25
fixup protocol sqlnet 1521
fixup protocol tftp 69
object-group network untrusted
object-group network from-sl
object-group network to-sl
access-list outside-to-inside permit icmp any any
access-list outside-to-inside permit ip object-group untrusted object-group to-sl
access-list outside-to-inside deny ip any any log
access-list in-to-out permit ip object-group from-sl object-group untrusted
access-list in-to-out deny ip any any log
access-list nonat permit ip object-group from-sl object-group untrusted
pager lines 24
logging on
logging timestamp
logging console critical
logging buffered informational
logging trap emergencies
logging history informational
logging device-id string FWALL
logging host inside
mtu scada 1500
mtu inside 1500
ip address scada
ip address inside
ip audit info action alarm
ip audit attack action alarm
pdm logging informational 100
pdm history enable
arp timeout 14400
nat (inside) 0 access-list nonat
access-group outside-to-inside in interface outside
access-group in-to-out in interface inside
router ospf 1
  network area 100
  network area 3
  area 3 virtual-link
  redistribute static subnets
route inside 1
route outside 1
timeout xlate 0:05:00
timeout conn 1:00:00 half-closed 0:10:00 udp 0:02:00 rpc 0:10:00 h225 1:00:00
timeout h323 0:05:00 mgcp 0:05:00 sip 0:30:00 sip_media 0:02:00
timeout sip-disconnect 0:02:00 sip-invite 0:03:00
timeout uauth 0:05:00 absolute
aaa-server TACACS+ protocol tacacs+
aaa-server TACACS+ max-failed-attempts 3
aaa-server TACACS+ deadtime 10
aaa-server RADIUS protocol radius
aaa-server RADIUS max-failed-attempts 3
aaa-server RADIUS deadtime 10
aaa-server LOCAL protocol local
aaa authentication ssh console LOCAL
snmp-server host inside
no snmp-server contact
no snmp-server enable traps
floodguard enable
telnet inside
telnet timeout 5
ssh outside
ssh inside
ssh timeout 5
management-access inside
console timeout 0
dhcpd lease 3600
dhcpd ping_timeout 750
terminal width 80
: end

Open in new window

Who is Participating?
Lots of pieces to this thanks for the additional info.

What you need to do to fix this if for the router at the head of the to know how to get to 17.16.31/24 the way to get there is through

This statement "" mean that it thinks to get to any class B 172.16 address it needs to go to, which is fine as long as points 172.16 to

Good Luck,

atlas_shudderedSr. Network EngineerCommented:
What does a trace look like to the .2 network?  How far is it getting?  From what you have posted, it looks like you are probably getting a nat translation failure to the .2 network.
You probably have a routing problem.

You have a route that states to get to go to which I assume is some sort of router. In that router you need a route that states to get to go to

You most likely have the DG of the PC's on the network to go to the router. But you have the PC's on the network pointing to the PIX.

That should fix the problem.

Become an IT Security Management Expert

In today’s fast-paced, digitally transformed world of business, the need to protect network data and ensure cloud privacy has never been greater. With a B.S. in Network Operations and Security, you can get the credentials it takes to become an IT security management expert.

WERAracerAuthor Commented:
what about pointing the remote routers to has a route in it that says "to get to, go to"

Wouldn't that make more sense?

Can't they don't know how to get to it. You can only put the next hop in a routing statement and the next hop would be which is the asa and is directly connected.


WERAracerAuthor Commented:
well and are connected via Frame Relay. I'm not sure if that matters or not. The intermittent routers between these two sites have a statement that says
WERAracerAuthor Commented:
sorry, I should have stated that and are two separate networks with a 24bit mask!
WERAracerAuthor Commented:
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.