PIX VPN routing to second network

[dhenry]

Summary:
I am trying to implement VPN on my Cisco 515E Pix. The VPN works great, I can ping any local computer, but not at any of our remote sites.

My network is somewhat set up like this:
internet
|
v
PIX 515E+VPN
192.168.1.1
|
v
192.168.1.254
192.168.50.254 secondary
Local Cisco1700
|
v
Frame Relay
|
v
Remote Cisco1700
192.168.3.254
|
V
192.168.3.222
Win2KServer

After the VPN is connected it is given an ip of 192.168.50.1. It can ping any computer on the 192.168.1.X network, but not on the 192.168.3.X (and vice-versa). If you cange the ip address of a workstation attached to the local network and give it an ip address of 192.168.50.250 (for example) it can ping the remote server, but now can not ping the computer connected with VPN. (From looking at the modem/VPN connection on the task bar of the VPN computer, the pings are reaching it, but it is not replying.)

Any guesses / experience with this?
Thanks for any help,
-Dave

PIX config below:

PIX Version 6.2(2)
nameif ethernet0 outside security0
nameif ethernet1 inside security100
enable password DEspzDnv5/GU14Q7 encrypted
passwd DEspzDnv5/GU14Q7 encrypted
hostname PIX
domain-name *****.ny.us
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
name 192.168.1.0 SL
name 192.168.4.0 TI
name 192.168.3.0 ML
name 192.168.50.0 vpn
access-list acl_out permit icmp any any
access-list 101 permit ip SL 255.255.255.0 192.168.2.0 255.255.255.0
access-list 101 permit ip SL 255.255.255.0 vpn 255.255.255.0
pager lines 24
logging on
logging timestamp
logging buffered alerts
logging trap alerts
logging history alerts
logging host inside 192.168.1.250
interface ethernet0 auto
interface ethernet1 auto
mtu outside 1500
mtu inside 1500
ip address outside 12.152.XXX.XXX 255.255.255.240
ip address inside 192.168.1.1 255.255.255.0
ip audit info action alarm
ip audit attack action alarm
ip local pool pptp-pool 192.168.50.100-192.168.50.200
no failover
failover timeout 0:00:00
failover poll 15
failover ip address outside 0.0.0.0
failover ip address inside 0.0.0.0
pdm location 192.168.1.250 255.255.255.255 inside
pdm location ML 255.255.255.0 inside
pdm location TI 255.255.255.0 inside
pdm location vpn 255.255.255.0 inside
pdm logging debugging 100
pdm history enable
arp timeout 14400
global (outside) 1 interface
nat (inside) 0 access-list 101
nat (inside) 1 0.0.0.0 0.0.0.0 0 0
access-group acl_out in interface outside
route outside 0.0.0.0 0.0.0.0 12.152.229.209 1
route inside ML 255.255.255.0 192.168.1.254 1
route inside TI 255.255.255.0 192.168.1.254 1
route inside vpn 255.255.255.0 192.168.50.254 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 192.168.1.250 255.255.255.255 inside
snmp-server host inside 192.168.1.250
no snmp-server location
no snmp-server contact
snmp-server community public
no snmp-server enable traps
floodguard enable
sysopt connection permit-pptp
no sysopt route dnat
telnet 192.168.1.250 255.255.255.255 inside
telnet timeout 5
ssh timeout 5
vpdn group 1 accept dialin pptp
vpdn group 1 ppp authentication mschap
vpdn group 1 ppp encryption mppe 128
vpdn group 1 client configuration address local pptp-pool
vpdn group 1 pptp echo 60
vpdn group 1 client authentication local
vpdn username XXXXXXX password *********
vpdn enable outside
terminal width 80
Cryptochecksum:c0cfa2473267f7217d374bef389ae667

 

[dhenry]

I fixed it.

I needed to add the other two networks to access-list 101