Getting desperate!!.. Need help with VPN access.

[exxor]

Hi!

I have been trying to configure VPN-Access on the new Cisco PIX 515E for over 1,5 week now..

The connect, group auth, user auth is going as it should.. I just cant get any traffic trou from the inside to the VPN-Client.

When I try to ping a host on the inside I just send package and get 0 packages in return.

I have looked at documentation at cisco until my eyes starts to bleed..

What am I missing here?

Inside: 192.168.100.0 ,255.255.255.0
Outside: 213.115.x.y ,255.255.255.0
VPN: 192.168.150.0 ,255.255.255.0

My config:

PIX Version 6.3(3)
interface ethernet0 auto
interface ethernet1 auto
interface ethernet2 auto
nameif ethernet0 outside security0
nameif ethernet1 inside security100
nameif ethernet2 dmz security50
enable password 8D9aro2ybKnXB6Wb encrypted
passwd 2KFQnbNIdI.2KYOU encrypted
hostname pix
domain-name viaduct.net
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
access-list nonat permit ip 192.168.100.0 255.255.255.0 192.168.150.0 255.255.255.0
access-list nonat permit ip 192.168.100.0 255.255.255.0 213.115.z.u 255.255.255.224
pager lines 24
logging on
logging console alerts
mtu outside 1500
mtu inside 1500
mtu dmz 1500
ip address outside 213.115.x.y 255.255.255.248
ip address inside 192.168.100.1 255.255.255.0
ip address dmz 213.115.z.u 255.255.255.224
ip audit info action alarm
ip audit attack action alarm
ip local pool vpnpool1 192.168.150.1-192.168.150.254
pdm location 192.168.100.20 255.255.255.255 inside
pdm logging debugging 100
pdm history enable
arp timeout 14400
global (outside) 10 interface
nat (inside) 0 access-list nonat
nat (inside) 10 0.0.0.0 0.0.0.0 0 0
route outside 0.0.0.0 0.0.0.0 213.115.x.y 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 192.168.100.20 255.255.255.255 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 trmset2 esp-des esp-md5-hmac
crypto dynamic-map map2 10 set transform-set trmset2
crypto map map1 10 ipsec-isakmp dynamic map2
crypto map map1 client configuration address respond
crypto map map1 client authentication LOCAL
crypto map map1 interface outside
isakmp enable outside
isakmp identity address
isakmp nat-traversal 10
isakmp policy 10 authentication pre-share
isakmp policy 10 encryption des
isakmp policy 10 hash md5
isakmp policy 10 group 2
isakmp policy 10 lifetime 86400
vpngroup viagrp address-pool vpnpool1
vpngroup viagrp dns-server 195.84.236.66
vpngroup viagrp default-domain viaduct.net
vpngroup viagrp idle-time 1800
vpngroup viagrp password ********
telnet timeout 5
ssh timeout 5
console timeout 0
username test password 7a819RfBiu3tdrYf encrypted privilege 15
terminal width 80
Cryptochecksum:cbbd12c11b8asdasdasd55697c22b3beb4f
: end

 

[LloydSev]

isakmp client configuration address-pool local vpnpool1 outside

Computer/Network Technician
CCNA

 

[rmcnutt]

If you have available host addresses left on the 100.0 network, try assigning a subset of that range in your vpnpool1 eg 192.168.100.200 - 192.168.100.250 then change your nonat access-list to
access-list nonat permit ip 192.168.100.0 255.255.255.0 192.168.100.0 255.255.255.0

 

[NetworkGhost]

When you ping from the client do a debug ICMP trace from the pix. It shows what the paket is doing when it hits the pix whether it is getting sent to the client, translating or what. This is good in troubleshooting where your packet is getting lost at and will most likely lead you to the cause.

 

[exxor]

Hi agin!

Seem like i solved my problem.. The configuration was correct and working, it was the client end that had trouble..

I tested the VPN-Client at three different sites (with different connections/firewalls) but it seems like all three blocked the IPSEC-Traffic...

No wonder I was going insane with the configuration..

Thanks for your answers anyway! =)