Improve company productivity with a Business Account.Sign Up

  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 393
  • Last Modified:

PIX VPN conected but no access

I setup the VPN on my PIX firewall.  It is setup for radius server on the inside.  I have one PAT port and one static Nat port.  I VPN into either and it lets me connect perfectly, but no access to anything.  It is like I am not connected at all.  The PIX is setup site-to-site with 2 other locations, and I am just trying to make this a remote access server.  Any help!!  I don't see any problems with my access list, but maybe I am blind.


: Saved
: Written by enable_15 at 11:55:12.971 EST Mon Nov 20 2006
PIX Version 6.3(5)
interface ethernet0 auto
interface ethernet1 100full
nameif ethernet0 outside security0
nameif ethernet1 inside security100
enable password ****** encrypted
passwd *********encrypted
hostname pixfirewall
clock timezone EST -5
clock summer-time EDT recurring
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 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
access-list 160 permit ip
access-list allow_ping permit icmp any any echo-reply
access-list allow_ping permit icmp any any time-exceeded
access-list allow_ping permit icmp any any unreachable
access-list 170 permit ip
access-list 150 permit ip
access-list 150 permit ip
access-list 150 permit ip any
access-list 100 permit tcp any host eq www
access-list 100 permit tcp any host eq https
access-list outside_cryptomap_dyn_20 permit ip any
no pager
logging on
logging monitor debugging
logging buffered debugging
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 cl-pool mask
pdm location inside
pdm location inside
pdm location outside
pdm location outside
pdm location outside
pdm location outside
pdm location inside
pdm location outside
pdm location outside
pdm logging informational 100
pdm history enable
arp timeout 14400
global (outside) 1 interface
nat (inside) 0 access-list 150
nat (inside) 1 0 0
static (inside,outside) netmask 0 0
access-group 100 in interface outside
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 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 5
aaa-server RADIUS deadtime 30
aaa-server RADIUS (inside) host **** timeout 30
aaa-server LOCAL protocol local
http server enable
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
sysopt connection permit-l2tp
crypto ipsec transform-set gb-set esp-aes-256 esp-md5-hmac
crypto ipsec transform-set is-set esp-3des esp-sha-hmac
crypto ipsec transform-set cl-set esp-3des esp-sha-hmac
crypto ipsec security-association lifetime seconds 3600
crypto dynamic-map outside_dyn_map 20 match address
crypto dynamic-map outside_dyn_map 20 set transform-set is-set
crypto map gb-map 1 ipsec-isakmp
crypto map gb-map 1 match address 160
crypto map gb-map 1 set peer
crypto map gb-map 1 set transform-set gb-set
crypto map gb-map 2 ipsec-isakmp
crypto map gb-map 2 match address 170
crypto map gb-map 2 set peer
crypto map gb-map 2 set transform-set is-set
crypto map gb-map 65535 ipsec-isakmp dynamic outside_dyn_map
crypto map gb-map interface outside
isakmp enable outside
isakmp key ********** address
isakmp key ********* address
isakmp key ******** address netmask
isakmp identity address
isakmp policy 1 authentication pre-share
isakmp policy 1 encryption aes-256
isakmp policy 1 hash md5
isakmp policy 1 group 2
isakmp policy 1 lifetime 5400
isakmp policy 2 authentication pre-share
isakmp policy 2 encryption 3des
isakmp policy 2 hash sha
isakmp policy 2 group 2
isakmp policy 2 lifetime 5400
isakmp policy 3 authentication pre-share
isakmp policy 3 encryption 3des
isakmp policy 3 hash sha
isakmp policy 3 group 2
isakmp policy 3 lifetime 86400
telnet inside
telnet timeout 15
ssh timeout 60
console timeout 0
vpdn group PPTP-VPDN-GROUP accept dialin pptp
vpdn group PPTP-VPDN-GROUP ppp authentication mschap
vpdn group PPTP-VPDN-GROUP ppp encryption mppe 40
vpdn group PPTP-VPDN-GROUP client configuration address local cl-pool
vpdn group PPTP-VPDN-GROUP client configuration dns
vpdn group PPTP-VPDN-GROUP client configuration wins
vpdn group PPTP-VPDN-GROUP client authentication aaa RADIUS
vpdn group PPTP-VPDN-GROUP client accounting RADIUS
vpdn group PPTP-VPDN-GROUP pptp echo 60  
vpdn enable outside
vpdn enable inside
dhcpd address inside
dhcpd dns
dhcpd wins
dhcpd lease 3600
dhcpd ping_timeout 750
dhcpd domain domain.local
dhcpd auto_config outside
dhcpd enable inside
username ****** password ******* encrypted privilege 15
terminal width 80
: end

1 Solution
Cisco does not recommend that the IP pool for the VPN overlaps or is on the same subnet as that of the internal network. I would recommend that you change your IP pool to something other than Once you create a new IP pool, add an access-list entry to acl 150 for the new pool.


ip local pool pptp_pool mask
access-list 150 permit ip 255.255.255
 Agree w/ stressedout2004 - if your 'ip local pool' overlaps any of the subnets that the PIX knows about, then you'll hit a routing loop, as you've already seen.  The client VPN pool also mustn't overlap any of the remote LANs on the other side of the site-site VPN links, nor the IP range of the LAN where the remote VPN client PC resides on, or again you'll hit a routing loop.

  You should also add this to your config:
isakmp nat-traversal

  I also hope you're not trying to access any of the remote site-site LANs (eg 192.168.1.x) directly from the remote VPN client - even if your client VPN pool doesn't overlap anything, you won't be able to get from the remote VPN client & across the site-site VPN link to the other sites.  PIX 6.x series won't let you do this "U-turn" (aka hairpinning), since traffic would have to enter & exit the same interface in order to get out to the other VPN site.  Only PIX 7.x series supports hairpinning, & 7.x is only supported on PIX 515 or above.
   A workaround would be to connect to a local PC/server on the 192.168.70.x subnet, then from there you'd be able to get over the site-site VPN links.

  Once you've made your changes to the client VPN pool, run this:
clear xlate
crypto map gb-map interface outside   <- important to re-apply VPN settings anytime you change the VPN config

stressedout2004 - WELCOME BACK!
Building an Effective Phishing Protection Program

Join Director of Product Management Todd OBoyle on April 26th as he covers the key elements of a phishing protection program. Whether you’re an old hat at phishing education or considering starting a program -- we'll discuss critical components that should be in any program.

I've been terribly busy : (
Are you still with us, Tabitha?
Do you need more information? We're here to help but only if you come back and dialog with us...

tabitha87Author Commented:
Yes, I am still here.  I tryied the different IP subnet, but not the other ones.  I will work on that by this weekend.
OK, thanks!
Are you still working on this? Can you close out this question before the cleanup crew gets around to it?
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

Featured Post

NEW Internet Security Report Now Available!

WatchGuard’s Threat Lab is a group of dedicated threat researchers committed to helping you stay ahead of the bad guys by providing in-depth analysis of the top security threats to your network.  Check out this quarters report on the threats that shook the industry in Q4 2017.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now