NAT issue on a 515 PIX

We are a flat 10.10.x.x network. We recently added the 10.118.x.x to our network and I can't get any of the 10.118 clients out to the internet. In fact, I can't even ping the PIX from the 10.118 network. 10.10 clients can get out to the internet fine.

Ip and subnet info for 10.10 is:


Ip subnet info for 10.118 is:


So the subnets we are using are 10.118.76 and 10.118.77 with a mask. All clients are using for their gateway. is a Cisco router that forwards all traffic to the PIX to get outside.

Here is my config:

Building configuration...
: Saved
PIX Version 6.3(1)
interface ethernet0 auto
interface ethernet1 auto
interface ethernet2 auto
nameif ethernet0 outside security0
nameif ethernet1 inside security100
nameif ethernet2 dmz security4
hostname Firewall
clock timezone CST -6
clock summer-time CDT recurring
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 pptp 1723
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
name WebServer
name FTPServer
name MailServer
object-group service FTP tcp
  port-object eq ftp
  port-object eq ftp-data
access-list outside_access_in permit tcp any interface outside eq www
access-list outside_access_in permit tcp any interface outside eq https
access-list outside_access_in permit tcp any interface outside object-group FTP
access-list outside_access_in permit tcp any interface outside eq smtp
access-list outside_access_in permit icmp any any
access-list inside_outbound_nat0_acl permit ip any
access-list inside_outbound_nat0_acl permit ip any host FTPServer
access-list outside_cryptomap_dyn_40 permit ip any
pager lines 24
mtu outside 1500
mtu inside 1500
mtu dmz 1500
ip address outside x.x.x.x
ip address inside
ip address dmz
ip audit info action alarm
ip audit attack action alarm
ip local pool vpn-pool
pdm location inside
pdm location WebServer inside
pdm location MailServer inside
pdm location FTPServer dmz
pdm location inside
pdm location inside
pdm location inside
pdm location outside
pdm location outside
pdm location FTPServer inside
pdm history enable
arp timeout 14400
global (outside) 10 interface
nat (inside) 0 access-list inside_outbound_nat0_acl
nat (inside) 10 0 0
static (inside,outside) tcp interface www WebServer www netmask 0 0
static (inside,outside) tcp interface https WebServer https netmask 0 0
static (inside,outside) tcp interface smtp MailServer smtp netmask 0 0
static (dmz,outside) tcp interface ftp FTPServer ftp netmask 0 0
access-group outside_access_in in interface outside
route outside x.x.x.x 1
route inside 1
timeout xlate 3:00: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 uauth 0:05:00 absolute
aaa-server TACACS+ protocol tacacs+
aaa-server RADIUS protocol radius
aaa-server LOCAL protocol local
http server enable
http outside
http inside
no snmp-server location
no snmp-server contact
snmp-server community public
no snmp-server enable traps
floodguard enable
sysopt connection permit-ipsec
sysopt connection permit-pptp
crypto ipsec transform-set ESP-3DES-MD5 esp-3des esp-md5-hmac
crypto dynamic-map outside_dyn_map 20 set transform-set ESP-3DES-MD5
crypto dynamic-map outside_dyn_map 40 match address outside_cryptomap_dyn_40
crypto dynamic-map outside_dyn_map 40 set transform-set ESP-3DES-MD5
crypto map outside_map 65535 ipsec-isakmp dynamic outside_dyn_map
crypto map outside_map interface outside
isakmp enable outside
isakmp nat-traversal 30
isakmp policy 20 authentication pre-share
isakmp policy 20 encryption 3des
isakmp policy 20 hash md5
isakmp policy 20 group 2
isakmp policy 20 lifetime 86400
vpngroup vpn-group address-pool
vpngroup vpn-group dns-server
vpngroup vpn-group wins-server
vpngroup vpn-group default-domain
vpngroup vpn-group idle-time 1800
telnet inside
telnet timeout 5
ssh timeout 5
management-access inside
console timeout 0
terminal width 80
: end

Any ideas?

LVL 23
Justin DurrantSr. Engineer - Windows Server/VirtualizationAsked:
Who is Participating?

Improve company productivity with a Business Account.Sign Up

lrmooreConnect With a Mentor Commented:
You simply need another route statement:

>route inside 1
This routes you to the subnet, so you need another route for the

  route inside 1

Same issue on this post, too, where the solution worked:
Justin DurrantSr. Engineer - Windows Server/VirtualizationAuthor Commented:
DOH! Thanks. :)  

I will try this tomorrow.

On another note, I am having trouble telnetting into another PIX (different then the one above) via VPN.

Telnet works great from the local LAN, but while connected to the VPN telnet to the router fails.

The local LAN is and the VPN assignable pool does fall in that range.

My telnet statement is as follows:

telnet inside

Any ideas?
Get Certified for a Job in Cybersecurity

Want an exciting career in an emerging field? Earn your MS in Cybersecurity and get certified in ethical hacking or computer forensic investigation. WGU’s MSCSIA degree program was designed to meet the most recent U.S. Department of Homeland Security (DHS) and NSA guidelines.  

You can't telnet to the PIX from the outside-VPN or not.
You can use SSH to the public IP address

ssh outside
Justin DurrantSr. Engineer - Windows Server/VirtualizationAuthor Commented:
i am not trying to telnet to the outside.. i get a local ip after the vpn is established, so telnetting should look like it's coming from the inside.
Nope. It doesn't work that way. Your telnet request comes from the outside interface. You cannot telnet to the inside interface from the outside interface. To clients on the inside network, yes, you appear as if you are local. To the PIX, however, you are not.
Hmmm.... PIX OS 6.3.x

Use the "management-access" command...

Remote Management Enhancements

This feature enables administrators to remotely manage firewalls over a VPN tunnel using the inside interface IP address of the remote PIX Firewall. In fact, administrators can define any PIX Firewall interface for management-access. This feature supports PDM, SSH, Telnet, SNMP, and so on, that requires a dynamic IP address. This feature significantly benefits broadband environments.

The management-access command is a new command added to the PIX Firewall Version 6.3 software. For a complete description of the command syntax for this new command, refer to the Cisco PIX Firewall Command Reference.

I knew you could use the PDM over a VPN, but I didn't realize that that telnet worked, too..
Reference link

I've been working with PIX for years, since 4.x version. New features added all the time, and always learning...

Thanks, Rubeck!
No, thank you.... lrmoore.

I've learned a lot of goldies from you, by reading a great deal of your posts on this site..... :-)


Justin DurrantSr. Engineer - Windows Server/VirtualizationAuthor Commented:
Yea I have that command in my config.. still doesn't work..

Also, adding that route fixed my other issue! Thanks!

Did you try this:

management-access inside
telnet inside

Glad you're working!

Justin DurrantSr. Engineer - Windows Server/VirtualizationAuthor Commented:
the telnet issue of in another pix.. i will check the code and get back to you if needed.

Still not sure why the route was needed though since the 10.118 route was already defined on the gateway router.
So now it appears that packets from 10.118 to the pix are being send back to the gateway router (, then back to the pix and out to the net.
I suppose I could update the default gateway for 10.118 to my internet router.. but oh well.. this works. Thanks for your help.
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.