Tech Support > Computer Hardware > Routers > PIX sa VPN server to 2 windows clients
PIX sa VPN server to 2 windows clients
Posted by Carl Jones on July 7th, 2004


Hi all,

I'm posting this message on behalf of a friend who can't get on the
internet atm.

They have a cisco PIX 501, all working fine and dandy, it's setup to
accept VPN clients over PPTP, again seems to work fine.

1 machine can connect to it through a cisco 800 series router (me)
without any problems, and the other machine can connect through some
other adsl router fine, both using windows XP's VPN client. This is
working fine and no problem.

Both clients can then ping the internal IP of the PIX, happy as larry.

However, the 2 clients cannot reach each other at all and this is the
problem, I've pasted his config here, is there anything obvious he's
missing?

Client 1 has IP 192.168.0.0 range 255.255.255.0 on his lan and client
2 has 192.168.128.0. and 255.255.255.0 on his LAN.

Here is the config, any advice gratefully appreciated on getting the 2
clients to talk to each other over the VPN, repalced public IP with
<masked> as he didnt want them posted


Building configuration...
: Saved
:
PIX Version 6.3(3)
interface ethernet0 auto
interface ethernet1 100full
nameif ethernet0 outside security0
nameif ethernet1 inside security100
enable password <masked> encrypted
passwd <masked> encrypted
hostname <masked>
domain-name <masked>
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
names
access-list inside_outbound_nat0_acl permit ip any 192.168.253.96
255.255.255.240
pager lines 24
mtu outside 1500
mtu inside 1500
ip address outside <masked> 255.255.255.248
ip address inside 192.168.253.1 255.255.255.0
ip audit info action alarm
ip audit attack action alarm
ip local pool VPN 192.168.253.101-192.168.253.110
pdm location 192.168.253.96 255.255.255.240 outside
pdm location 192.168.253.96 255.255.255.240 inside
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
route outside 0.0.0.0 0.0.0.0 <masked> 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.168.253.0 255.255.255.0 inside
no snmp-server location
no snmp-server contact
snmp-server community public
no snmp-server enable traps
floodguard enable
sysopt connection permit-pptp
crypto ipsec transform-set TRANS_ESP_3DES_MD5 esp-3des esp-md5-hmac
crypto ipsec transform-set TRANS_ESP_3DES_MD5 mode transport
crypto ipsec transform-set ESP-3DES-MD5 esp-3des esp-md5-hmac
crypto ipsec transform-set ESP-DES-MD5 esp-des esp-md5-hmac
crypto dynamic-map outside_dyn_map 20 set transform-set
TRANS_ESP_3DES_MD5
telnet timeout 5
ssh timeout 5
console timeout 0
vpdn group PPTP-VPDN-GROUP accept dialin pptp
vpdn group PPTP-VPDN-GROUP ppp authentication mschap
vpdn group PPTP-VPDN-GROUP ppp encryption mppe auto
vpdn group PPTP-VPDN-GROUP client configuration address local VPN
vpdn group PPTP-VPDN-GROUP pptp echo 60
vpdn group PPTP-VPDN-GROUP client authentication local
vpdn username optinium password *********
vpdn username voodoo password *********
vpdn enable outside
dhcpd address 192.168.253.50-192.168.253.100 inside
dhcpd lease 3600
dhcpd ping_timeout 750
dhcpd auto_config outside
terminal width 80
Cryptochecksum:1bc73b1807c8a0b0026f240f0a9de0a4
: end
[OK]

Posted by jhuys on July 7th, 2004


This is a pix issue.
PIX doesn't allow that incoming packet gets routed outside to the same
interface on which that packet arrived to pix. And you have that situation,
all vpn clients are on public/outside interface of pix. Packet from one
client arrives at outside intf, and after decryption, it should be routed to
other vpn client that resides also on outside interface. Packet is dropped.

hth,
j


"Carl Jones" <belial239@gmail.com> wrote in message
news:29174ebe.0407070343.402fdbe6@posting.google.c om...