Success!!, but 2 small problems remain. Thanks for all the help!

[ajinc]

Hello All,
First
Thank You to all that assited me with this issue.
I really appreciate the help, and "lack of help" in some instances, because it made me think a little more, and I came up with the fix I needed. Thanks again to all!

I have my pix working with split tunnelling now using the cisco client v4.6 "HOORAY"!!
I have jus t a few questions if someone knows the answers I thank them.

My final problems are:

1. I was using the Safenet client to connect to another vpn endpoint. When the PIX is on my network the client
cant'connect. The Safenet sight stated that I may have to open udp 500 esp 50, and ah 51 are my ACL's correct to do this?

2. Has anyone used the Safenet Softremote vpn client from CoSine communicatios, or know of a doc on the subject? It is very similiar to the cisco client v1. The vendors docs states that the client works with PIX v 5 and above, but I can't get this client to connect with the PIX.

3. Finally I attempted to use the acl

access-list inside_outbound_nat0_acl permit ip 192.169.2.0 255.255.255.0 10.10.10.0 255.255.255.0
access-list outside_cryptomap_dyn_10 permit ip 192.169.2.0 255.255.255.0 10.10.10.0 255.255.255.0

instead of

access-list inside_outbound_nat0_acl permit ip any 10.10.10.0 255.255.255.0
access-list outside_cryptomap_dyn_10 permit ip any 10.10.10.0 255.255.255.0


but when I do the cisco client gives me the error message "no valid key found"

Below is my config,any ideas on this are appreciated


PIX Version 6.3(3)
interface ethernet0 auto
interface ethernet1 100full
nameif ethernet0 outside security0
nameif ethernet1 inside security100
hostname pixfirewall
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 pptp 1723
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
names
access-list inside_outbound_nat0_acl permit ip any 10.10.10.0 255.255.255.0
access-list OUTSIDE_IN permit icmp any any
access-list OUTSIDE_IN permit udp any eq isakmp any
access-list OUTSIDE_IN permit esp any any
access-list OUTSIDE_IN permit ah any any
access-list outside_cryptomap_dyn_10 permit ip any 10.10.10.0 255.255.255.0
access-list split permit ip 192.169.2.0 255.255.255.0 10.10.10.0 255.255.255.0
pager lines 24
logging on
icmp permit any outside
mtu outside 1500
mtu inside 1500
ip address outside pppoe setroute
ip address inside 192.169.2.1 255.255.255.0
ip verify reverse-path interface outside
ip verify reverse-path interface inside
ip audit info action alarm
ip audit attack action alarm
ip local pool kgcpa 10.10.10.1-10.10.10.10
pdm location 192.169.2.0 255.255.255.0 inside
pdm location 10.10.10.0 255.255.255.0 inside
pdm location 10.10.10.0 255.255.255.255 inside
pdm location 10.10.10.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 0.0.0.0 0.0.0.0 0 0
access-group OUTSIDE_IN in interface outside
route inside 10.10.10.0 255.255.255.0 192.169.2.0 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.169.2.0 255.255.255.0 inside
http 10.10.10.0 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
sysopt connection permit-pptp
sysopt connection permit-l2tp
crypto ipsec transform-set ESP-3DES-MD5 esp-3des esp-md5-hmac
crypto dynamic-map outside_dyn_map 10 match address outside_cryptomap_dyn_10
crypto dynamic-map outside_dyn_map 10 set pfs group2
crypto dynamic-map outside_dyn_map 10 set transform-set ESP-3DES-MD5
crypto dynamic-map outside_dyn_map 10 set security-association lifetime seconds 86400 kilobytes 4608000
crypto map outside_map 65535 ipsec-isakmp dynamic outside_dyn_map
crypto map outside_map interface outside
isakmp enable outside
isakmp key ******** address 192.169.2.0 netmask 255.255.255.255
isakmp identity address
isakmp nat-traversal 20
isakmp policy 10 authentication pre-share
isakmp policy 10 encryption 3des
isakmp policy 10 hash md5
isakmp policy 10 group 2
isakmp policy 10 lifetime 86400
vpngroup kgcpaipsec address-pool kgcpa
vpngroup kgcpaipsec dns-server 192.169.2.2
vpngroup kgcpaipsec default-domain ajinc.local
vpngroup kgcpaipsec split-tunnel split
vpngroup kgcpaipsec pfs
vpngroup kgcpaipsec idle-time 1800
vpngroup kgcpaipsec max-time 86400
vpngroup kgcpaipsec password ********
telnet timeout 5
ssh timeout 5
management-access inside
console timeout 0
vpdn group pppoe_group request dialout pppoe
vpdn group pppoe_group localname vze2q563
vpdn group pppoe_group ppp authentication pap
vpdn username vze2q563 password *********
dhcpd address 192.169.2.10-192.169.2.41 inside
dhcpd dns 192.169.2.2
dhcpd lease 3600
dhcpd ping_timeout 750
dhcpd domain ajinc.local
dhcpd auto_config outside
dhcpd enable inside
terminal width 80

 

[dopehead]

Well, the cisco client 1.0 and 1.0a was actually an OEM safenet client, ie the likeness of the two. I do believe cisco stopped all support for this client quite a while back unfortunately. This error msg "no valid key found" is because the safenet client does not operate with the groupname/password concept, so it is looking for a pre-shared key for that peer in the config which it does not find, you might be able to put in an "isakmp key test1234 address 0.0.0.0 netmask 0.0.0.0" command and try test1234 as your key in the safenet client....might work.


Network Systems Engineer
CCNA/CQS/CCSP/Infosec

 

[ajinc]

Thanks for your time & knowledge,
Do you have any idea why the safenet client stops connecting to my dlink vpn end point when the PIX is on my network? I connect a verizon dsl modem to my pix, and the safenet client can't connect to my dlink endpoint, all other communications work. If I take the pix out, and use my verizon pppoe dialer to get internet connectivity then use my safenet client it connects fine. The pix is blocking someting, I can't figure out what. I thought I allowed udp port 500, port 50, and 51 for IPSEC traffic, but no joy. What log on the PIX would tell my why the inbound safenet client traffic is being blocked?
Thanks for any ideas.

 

[LloydSev]

firstly, this will not fix it, but i want to point out to you that ports 50 and 51 do not require being open for IPSec.

IPSec uses the following:

Port 500
Protocol 50
Protocol 51

Protocol /= Port

Computer/Network Technician
CCNA

 

[ajinc]

Thank you for that information.

Do you have any idea why my IPSec client won't connect to my end point when the pix is on my network?

TIA

 

[ajinc]

Concerning the above issue with the PIX stopping my safenet client from connecting. In the PIX log I see

DENY inbound (No xlate) udp src inside:192.169.2.10/500 dst inside:152.156.122.2/500
can some one explain why this info is being denied, and how to allow it .

Thanks for any ideas