Improve company productivity with a Business Account.Sign Up


Problem accessing internal network after successful VPN connection on Cisco PIX 501

Posted on 2006-11-17
Medium Priority
Last Modified: 2010-04-12
I am new to this but was hoping that somebody could help me here. Basically I have configured a PIX 501 for use with the Cisco VPN 4.6 client. The client connects fine but the problem is that I cannot access the internal network or even ping anything. This should be a straight forward config with 1 network and no NAT. I have attached the config if anybody would be so kind as to steer me in the correct direction.

PIX Version 6.3(1)
interface ethernet0 auto
interface ethernet1 100full
nameif ethernet0 outside security0
nameif ethernet1 inside security100
enable password FwtGInQ5D56C1ULH encrypted
passwd 2KFQnbNIdI.2KYOU encrypted
hostname levypix
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
access-list inside_outbound_nat0_acl permit ip interface inside
interface outside
access-list outside_cryptomap_dyn_20 permit ip interface inside
interface outside
access-list 108 permit ip
pager lines 24
mtu outside 1500
mtu inside 1500
ip address outside
ip address inside
ip audit info action alarm
ip audit attack action alarm
ip local pool vpn_ip
pdm location inside
pdm location outside
pdm logging informational 100
pdm history enable
arp timeout 14400
global (outside) 1 interface
nat (inside) 0 access-list inside_outbound_nat0_acl
nat (inside) 1 0 0
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
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 inside
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
crypto ipsec transform-set ESP-3DES-MD5 esp-3des esp-md5-hmac
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 map outside_map 65535 ipsec-isakmp dynamic outside_dyn_map
crypto map outside_map interface outside
isakmp enable outside
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 levyVPN address-pool vpn_ip
vpngroup levyVPN dns-server
vpngroup levyVPN default-domain
vpngroup levyVPN idle-time 1800
vpngroup levyVPN password xxxxxx
telnet timeout 5
ssh timeout 5
console timeout 0
dhcpd auto_config outside
username admin password n0Hm746wziOmH8fi encrypted privilege 15
terminal width 80
: end
Question by:admpc
  • 2
LVL 20

Accepted Solution

calvinetter earned 500 total points
ID: 17970585
Ye gods! 6.3(1)?  If your PIX has current SmartNet support on it, upgrade to 6.3(5) ASAP!  6.3(1) has a ton of bugs in it (plus some security bugs), & actually requires a reboot for silly things like VPN, NAT table, etc to be reset or take effect.  If an upgrade is possible, you'll be very glad you did it.  Ok, moving on...

   Run these commands in this order:
access-list inside_outbound_nat0_acl permit ip
no access-list inside_outbound_nat0_acl permit ip interface inside interface outside
no access-list outside_cryptomap_dyn_20 permit ip interface inside interface outside
isakmp nat-traversal
wr mem
reload  <- *must* reboot the PIX!

>crypto ipsec transform-set ESP-3DES-MD5 esp-3des esp-md5-hmac
>crypto ipsec transform-set ESP-3DES-MD5 esp-3des esp-md5-hmac
   Is this a typo? Surely your config doesn't have 2 identical transform-set lines?  Or I'm seeing double...

LVL 20

Expert Comment

ID: 17970594
Note that the subnet behind the PIX (10.0.0.x) is a very common subnet...  If your VPN client will be connecting from various networks, you'll hit a routing loop when the local LAN that the VPN client is coming from is also on the 10.0.0.x range (or if any of the local subnets are in this range).  Hmm, 10.1.1.x might be common enough to occasionally cause problems as well.   Just some gotchas to watch out for.


Featured Post

Free Tool: Subnet Calculator

The subnet calculator helps you design networks by taking an IP address and network mask and returning information such as network, broadcast address, and host range.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

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.

Join & Write a Comment

I've had to do a bit of research to setup my VPN connection so that Clients can access Windows Server 2008 network shares.  I have a Cisco ASA 5510 firewall.  I found an article which was extremely useful: It had a solution if you use ASDM to config…
Will you be ready when the clock on GDPR compliance runs out? Is GDPR even something you need to worry about? Find out more about the upcoming regulation changes and download our comprehensive GDPR checklist today !
After creating this article (, I decided to make a video (no audio) to show you how to configure the routers and run some trace routes and pings between the 7 sites…
Windows 10 is mostly good. However the one thing that annoys me is how many clicks you have to do to dial a VPN connection. You have to go to settings from the start menu, (2 clicks), Network and Internet (1 click), Click VPN (another click) then fi…

606 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question