Link to home
Start Free TrialLog in
Avatar of admpc
admpc

asked on

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

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
domain-name levyarch.com
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
names
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 10.0.0.0 255.255.255.0 10.1.1.0 255.255.255.0
pager lines 24
mtu outside 1500
mtu inside 1500
ip address outside xx.xxx.xxx.xxx 255.255.255.248
ip address inside 10.0.0.1 255.255.255.0
ip audit info action alarm
ip audit attack action alarm
ip local pool vpn_ip 10.1.1.200-10.1.1.205
pdm location 192.168.1.0 255.255.255.0 inside
pdm location 192.168.1.16 255.255.255.252 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.0.0 0.0.0.0 0 0
route outside 0.0.0.0 0.0.0.0 xx.xxx.xxx.xxx 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 uauth 0:05:00 absolute
aaa-server TACACS+ protocol tacacs+
aaa-server RADIUS protocol radius
aaa-server LOCAL protocol local
http server enable
http 10.0.0.0 255.255.255.0 inside
http 192.168.1.0 255.255.255.0 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 10.0.0.2
vpngroup levyVPN default-domain 10.com
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
Cryptochecksum:08c8c33c0d5bcc25c7856a8234d1391c
: end
ASKER CERTIFIED SOLUTION
Avatar of calvinetter
calvinetter
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
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.

cheers