Unable to Connect VPN client 3.6.3

[wcadmin]

Hi,

I am currently trying to set up VPN access on my pix 506e running 6.2os. I configured the box using the PDM wizard. I am uable to make a connection using Cisco VPN client 3.6.3.
On the client side I get a peer not responding message. On the pix I think the most significant debug message I am getting is as follows:

ISAKMP encryption... What? 7.

my config is posted below.

Thanks in advance for any help provided.

PIX Version 6.2(2)
nameif ethernet0 outside security0
nameif ethernet1 inside security100
enable password xxxx encrypted
passwd xxxxx encrypted
hostname pixfirewall
domain-name mydomain.com
clock timezone EST -5
clock summer-time EDT recurring
fixup protocol ftp 21
fixup protocol http 80
fixup protocol h323 h225 1720
fixup protocol h323 ras 1718-1719
fixup protocol ils 389
fixup protocol rsh 514
fixup protocol rtsp 554
fixup protocol smtp 25
fixup protocol sqlnet 1521
fixup protocol sip 5060
fixup protocol skinny 2000
names
access-list acl_out permit ip any any
access-list inside_access_in permit tcp any any
access-list inside_access_in permit ip any any
access-list inside_access_in permit udp any any
access-list inside_outbound_nat0_acl permit ip any 192.169.1.64 255.255.255.240
access-list outside_cryptomap_dyn_20 permit ip any 192.169.1.64 255.255.255.240
pager lines 24
logging on
logging buffered debugging
logging history debugging
interface ethernet0 auto
interface ethernet1 auto
mtu outside 1500
mtu inside 1500
ip address outside pppoe setroute
ip address inside 192.169.1.1 255.255.255.0
ip audit info action alarm
ip audit attack action alarm
ip local pool vpniprange 192.169.1.70-192.169.1.75
pdm logging debugging 512
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
access-group acl_out in interface outside
access-group inside_access_in in interface inside
rip inside default version 1
timeout xlate 3:00:00
timeout conn 1:00:00 half-closed 0:10:00 udp 0:02:00 rpc 0:10:00 h323 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 0.0.0.0 0.0.0.0 outside
http 0.0.0.0 0.0.0.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
no sysopt route dnat
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 mdladmin address-pool vpniprange
vpngroup mdladmin idle-time 1800
vpngroup mdladmin password ********
telnet timeout 5
ssh timeout 5
vpdn group pppoe-verizon request dialout pppoe
vpdn group pppoe-verizon localname vze3s3nr
vpdn group pppoe-verizon ppp authentication pap
vpdn username vze3s3nr password *********
dhcpd address 192.169.1.10-192.169.1.50 inside
dhcpd dns 151.203.0.84 151.203.0.85
dhcpd lease 2073600
dhcpd ping_timeout 750
dhcpd enable inside
terminal width 80

 

[yizhar]

HI.

> ip address inside 192.169.1.1 255.255.255.0
> ip local pool vpniprange 192.169.1.70-192.169.1.75
This is wrong.
You must use a different non-existing subnet for VPN clients, for example 192.168.111.X

Bye

Yizhar Hurwitz

http://come.to/yizhar

http://teachers.sivan.co.il/yizhar

 

[yizhar]

HI.

Please check that:

1) You are using the correct group name and password:
vpngroup mdladmin password ********

2) The VPN client and the pix can ping each other before establishing the VPN tunnel.

Bye
Yizhar Hurwitz

http://come.to/yizhar

http://teachers.sivan.co.il/yizhar

 

[gbiello]

Some things I noticed:
1) You're using DES. I could not get 3.6.3 to work with DES, only 3DES.

2) You're using PPPoE. Do you know what the outside IP address it catches is?

3) Your VPN section differs a bit from mine. Here is what I have, that I know works:

crypto ipsec transform-set myset esp-des esp-sha-hmac
crypto dynamic-map mydynmap 10 set transform-set myset
crypto map newmap 10 ipsec-isakmp dynamic mydynmap
crypto map newmap client configuration address initiate
crypto map newmap client configuration address respond
crypto map newmap interface outside
isakmp enable outside
isakmp key ******** address 0.0.0.0 netmask 0.0.0.0
isakmp identity address
isakmp policy 10 authentication pre-share
isakmp policy 10 encryption des
isakmp policy 10 hash sha
isakmp policy 10 group 2
isakmp policy 10 lifetime 86400

Try using that as a template.

hope this helps,
-gbiello

 

[gbiello]

...The 3.5.2 client worked with DES.

 

[themikehyde]

How would you modify this to allow domain authentication?

 

[gbiello]

...not sure you can. With 2K/XP client you browse and get prompted to login to domain.

-gbiello

 

[wcadmin]

I made the ip range changes and checked all the other areas commented on and I am still getting the same results...

I noticed a couple of other post on the board with users configuring VPN using the PDM and it not working. Has anyone ever been able to get this to work starting with the base PDM config? Just curious.

Also, any additional suggestion are greatly appreciated.

Thanks much,

w

 

[themikehyde]

I tried setup as described in

http://www.cisco.com/en/US/products...s_configuration_example09186a00800b6099.shtml

I get a prompting for username and password, but it keeps saying hash authentication failed in the client log. The log on the IAS server was not showing anything. Maybe its a setup on the IAS server?
Mike

 

[wcadmin]

It looks like this might infact come down to an authentication problem. I seem to be getting closer but have not yet solved it. I am trying to work through the various authentication options. Can anyone tell me if when using pre-share is any other authentication setup required other than maintaining the group/password pair on the client and the PIX?

Thanks in advance,

w