PIng problem on a PIX 506

[javiedigital]

I have installed a PIX 506 version 6.2 with a DSL connection on a small LAN. All the workstations are able to surf the web but a few workstation cannot be pinged by the PIX. Any ideas?

 

[baddos]

Are they on the same subnet?

 

[jollity]

can i get the config of your PIX ? Can you post it here, if its ok with you.
Do you get DHCP address from your ISP ?
Thanks
Jollity

 

[javiedigital]

I have a static IP from our ISP.


PIX Version 6.1(4)
nameif ethernet0 outside security0
nameif ethernet1 inside security100
enable password dUL7AcdCk7dwtXhH encrypted
passwd 2KFQnbNIdI.2KYOU encrypted
hostname Pix506Efirewall
domain-name pacbell.net

fixup protocol ftp 21
fixup protocol http 80
fixup protocol h323 1720
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 110 permit ip 192.168.2.0 255.255.255.0 192.168.2.0 255.255.255.0

pager lines 24
interface ethernet0 auto
interface ethernet1 auto
mtu outside 1500
mtu inside 1500

ip address outside 67.119.49.X 255.255.255.224
ip address inside 192.168.2.1 255.255.255.0
ip audit info action alarm
ip audit attack action alarm
ip local pool vpnusers 192.168.2.50-192.168.55
pdm history enable
arp timeout 14400

global (outside) 1 interface
nat (inside) 0 access-list 110
nat (inside) 1 0.0.0.0 0.0.0.0 0 0
conduit permit icmp any any
conduit permit gre any any

~access-group 110 in interface outside
route outside 0.0.0.0 0.0.0.0 67.119.49.X

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 si
p 0:30:00 sip_media 0:02:00
timeout uauth 0:05:00 absolute
aaa-server TACACS+ protocol tacacs+
aaa-server RADIUS protocol radius
no snmp-server location
no snmp-server contact
snmp-server community public
no snmp-server enable traps
floodguard enable

sysopt connection permit-ipsec
syspot connection permit-pptp
no sysopt route dnat

crypto ipsec transform-set myset esp-des esp-md5-hmac
crypto dynamic-map dynmap 10 set transform-set myset
crypto map mymap 10 ipsec-isakmp dynamic dynmap
crypto map mymap client configuration address initiate
crypto map mymap client configuration address respond
crypto map mymap interface outside
crypto map mymap 10 set security-assiciation lifetime seconds 3600 kilobytes 4608000

isakmp enable outside
isakmp client configuration address-pool local VPN outside
isakmp key cisco address 0.0.0.0 netmask 0.0.0.0
isakmp client configuration address-pool local VPN outside
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

telnet 0.0.0.0 0.0.0.0 inside
telnet timeout 5
ssh timeout 5


vpngroup vpnUser1 address-pool vpnusers
vpngroup vpnUser1 dns-server 206.13.XX.XX 206.13.XX.XX
vpngroup vpnUser1 default-domain pacbell.net
vpngroup vpnUser1 idle-time 1800
vpngroup vpnUser1 password XXXX

dhcpd address 192.168.2.75-192.168.2.254 inside
dhcpd dns 206.13.XX.XX 206.13.XX.XX
dhcpd lease 3600
dhcpd ping_timeout 750
dhcpd domain pacbell.net
dhcpd enable inside

terminal width 80
Cryptochecksum:0c123c243184e40072fde64eb351211f

 

[yizhar]

HI.

> ip address inside 192.168.2.1 255.255.255.0
> ip local pool vpnusers 192.168.2.50-192.168.55
You should use a differnt range of addresses for VPN users, and then edit access-list accordinly. For example:
ip local pool vpnusers 192.168.11.50-192.168.11.55

There is also a typo mistake in the line:
> ip local pool vpnusers 192.168.2.50-192.168.55

Bye
Yizhar Hurwitz

http://come.to/yizhar

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