Cisco VPN Client Connects but can't access network

[ensorg]

Hi,

I have a cisco pix 501 firewall. I have configured a Remote access VPN using the wizard in the PDM. When I attempted to connect the client connects sucessfully but I cannot ping anything on the remote network.

I have a Netgear router on 192.168.0.1 this is set so the DMZ is the pix outside interface - 192.168.0.12. The remote network is 192.84.7.0

Can anybody see something wrong with the config below?

Many Thanks

Building configuration...
: Saved
:
PIX Version 6.3(1)
interface ethernet0 auto
interface ethernet1 100full
nameif ethernet0 outside security0
nameif ethernet1 inside security100
enable password ******** encrypted
passwd ********* encrypted
hostname tmaxbangor
domain-name tmaxbangor.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 any 192.84.7.192 255.255.255.192
access-list outside_cryptomap_dyn_20 permit ip any 192.84.7.192 255.255.255.192
pager lines 24
logging on
mtu outside 1500
mtu inside 1500
ip address outside 192.168.0.12 255.255.255.0
ip address inside 192.84.7.99 255.255.255.0
ip audit info action alarm
ip audit attack action alarm
ip local pool kectmxpool 192.84.7.200-192.84.7.225
pdm location 192.84.7.0 255.255.255.0 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 192.84.7.0 255.255.255.0 0 0
route outside 0.0.0.0 0.0.0.0 192.168.0.1 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 192.84.7.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-DES-MD5 esp-des esp-md5-hmac
crypto dynamic-map outside_dyn_map 20 match address outside_cryptomap_dyn_20
crypto dynamic-map outside_dyn_map 20 set transform-set ESP-DES-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 des
isakmp policy 20 hash md5
isakmp policy 20 group 2
isakmp policy 20 lifetime 86400
vpngroup kectmxpix address-pool kectmxpool
vpngroup kectmxpix idle-time 1800
vpngroup kectmxpix password ********
telnet timeout 5
ssh timeout 5
console timeout 0
dhcpd address 192.84.7.100-192.84.7.227 inside
dhcpd lease 3600
dhcpd ping_timeout 750
dhcpd auto_config outside
terminal width 80
: end
[OK]

 

[Supergrrover]

Your VPN pool of addresses needs to not be in the same network as your internal network.

ip address inside 192.84.7.99 255.255.255.0
ip local pool kectmxpool 192.84.7.200-192.84.7.225

Just change it (with the ACLs as well) and everything else looks like it should come up.


Brent
Systems Engineer / Consultant
CCNP, CCSP

 

[ensorg]

Hi Brent,

Do you mean I should have my pool of address as something like 192.168.1.x?

If I do this would I still be able to access network resources on 192.84.7.x?

Thanks

 

[Supergrrover]

Yes, although I would avoid the 192.168.x.0 networks (they tend to be the default for home routers.)

The ASA/PIX sets an temporary ACL for these so you will be able to access your internal network.


Brent
Systems Engineer / Consultant
CCNP, CCSP