PDM and Command line conflicts

[efector]

I have the config listed below. The stupid PDM wont access the config because apparently there are commands that the PDM doesnt like, but the CLI commands are valid and work. Can anyone tells me what the issue is???

Thanks in advance

PIX Version 6.3(3)
interface ethernet0 auto
interface ethernet1 auto
nameif ethernet0 outside security0
nameif ethernet1 inside security100
hostname pixfirewall
domain-name domain.com
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 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
fixup protocol tftp 69
names
access-list 100 permit icmp any any echo-reply
access-list 100 permit icmp any any time-exceeded
access-list 100 permit icmp any any unreachable
access-list 115 permit ip 192.168.99.0 255.255.255.0 66.77.17.192 255.255.255.192
access-list 115 deny ip 192.168.99.0 255.255.255.0 any
pager lines 24
mtu outside 1500
mtu inside 1500
ip address outside 62.118.136.217 255.255.255.224
ip address inside 192.168.99.1 255.255.255.0
ip audit info action alarm
ip audit attack action alarm
pdm location 192.168.99.45 255.255.255.255 inside
pdm history enable
arp timeout 14400
global (outside) 1 interface
nat (inside) 0 access-list 115
nat (inside) 1 0.0.0.0 0.0.0.0 0 0
access-group 100 in interface outside
route outside 0.0.0.0 0.0.0.0 62.118.136.217 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.99.45 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 myset esp-3des esp-sha-hmac
crypto map qwestmap 10 ipsec-isakmp
crypto map qwestmap 10 match address 115
crypto map qwestmap 10 set peer 62.118.137.217
crypto map qwestmap 10 set transform-set myset
crypto map qwestmap 10 set security-association lifetime seconds 3600 kilobytes 4608000
crypto map qwestmap interface outside
isakmp enable outside
isakmp key ******** address 62.118.137.217 netmask 255.255.255.248
isakmp identity address
isakmp policy 10 authentication pre-share
isakmp policy 10 encryption 3des
isakmp policy 10 hash sha
isakmp policy 10 group 2
isakmp policy 10 lifetime 10080
telnet timeout 5
ssh timeout 5
console timeout 0
terminal width 80

 

[chicocouk]

Yes, this is a common mistake. You are not supposed to use the same access list for the
"nat 0" command, and the "crypto map match" command. There is documentation to this effect on cisco's website, but it's a bit obscure, and not very obvious.

Your problem is these two lines;

crypto map qwestmap 10 match address 115
nat (inside) 0 access-list 115

They both use access-list number 115. The solution is to create an exact duplicate access list, and use one acl for the crypto map command, and the other for the nat (inside) 0 command

Ie, copy and paste the following into CLI on the pix;

access-list 116 permit ip 192.168.99.0 255.255.255.0 66.77.17.192 255.255.255.192
access-list 116 deny ip 192.168.99.0 255.255.255.0 any

no crypto map qwestmap 10 match address 115
crypto map qwestmap 10 match address 116

Then do a write mem, and try to connect with PDM.

That should sort it out.

All the best,

Chico


CCNA, MCSE, Cisco Firewall specialist, VPN specialist, wannabe CCSP