Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

VPN Client cant be pinged 1

Status
Not open for further replies.
May 12, 2003
29
0
0
US
Hello,

I have a remote employee that needs to VPN into our network. The remote employee can successfully connect to the VPN (Pix 506E) get assinged an internal ip and ping any device within the LAN but I cannot ping the VPN'ed employee's assigned address from within the LAN or the pix. Below is my pix config, any help would be appreciated.

PIX Version 6.3(3)
interface ethernet0 auto
interface ethernet1 auto
nameif ethernet0 outside security0
nameif ethernet1 inside security100
enable password xxxxxxxxxxxxxxx encrypted
passwd xxxxxxxxxxxxxxx encrypted
hostname Pix
domain-name Pix.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 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
access-list 101 permit ip any any
pager lines 24
mtu outside 1500
mtu inside 1500
ip address outside 207.x.x.x 255.255.x.x
ip address inside 192.168.1.1 255.255.254.0
ip audit info action alarm
ip audit attack action alarm
ip local pool ippool 192.168.1.50-192.168.1.130
pdm history enable
arp timeout 14400
nat (inside) 0 access-list 101
nat (inside) 1 0.0.0.0 0.0.0.0 0 0
route outside 0.0.0.0 0.0.0.0 207.47.x.x 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.1.222 255.255.255.254 inside
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-des esp-md5-hmac
crypto dynamic-map dynmap 10 set transform-set myset
crypto map mymap 10 ipsec-isakmp dynamic dynmap
crypto map mymap interface outside
isakmp enable outside
isakmp identity address
isakmp nat-traversal 20
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 vpn3000 address-pool ippool
vpngroup vpn3000 dns-server 216.237.x.x
vpngroup vpn3000 default-domain pix.com
vpngroup vpn3000 idle-time 1800
vpngroup vpn3000 password ********
vpngroup password idle-time 1800
telnet timeout 5
ssh timeout 5
console timeout 0
terminal width 80
 
Maybe your subnets do not match. Here is the comparison:

ip address inside 192.168.1.1 255.255.254.0
ip local pool ippool 192.168.1.50-192.168.1.130 (default /24)

Try entering this entry to specify the range:

ip local pool ippool 192.168.1.50-192.168.1.130 mask 255.255.254.0

You might have to remove and re-add the ippool entry in the vpngroup due to the fact ippool is being used.
 
ip address inside 192.168.1.1 255.255.254.0
ip local pool ippool 192.168.1.50-192.168.1.130

You need to have different non-overlapping networks for the internal and VPN pools.
Your vpn pool should also not be a normal network that home routers/firewalls use. Try 192.168.253.1-192.168.253.50.

Be sure the change your nat 0 access list.



Brent
Systems Engineer / Consultant
CCNP, CCSP
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top