Intranet VPN

[tek777]

My authentication via XAUTH now works, but I cannot access the lan. I tried doing a split tunneling, it allowed me to surf the internet, but it seems I cannot do anything else, (access servers).

My Lan 10.10.0.0
My IP Pool 192.168.100.x
My XAUTH Server 10.10.0.x

I must be missing something, please help

Building configuration...
: Saved
:
PIX Version 6.3(3)
interface ethernet0 auto
interface ethernet1 auto
nameif ethernet0 outside security0
nameif ethernet1 inside security100
enable password .
hostname pixfirewall
domain-name m13-group.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
names
access-list inside_outbound_nat0_acl permit ip any 192.168.100.0 255.255.255.224
access-list outside_cryptomap_dyn_20 permit ip any 192.168.100.0 255.255.255.224
pager lines 24
mtu outside 1500
mtu inside 1500
ip address outside x.x.86.211 255.255.255.240
ip address inside 10.10.0.200 255.0.0.0
ip audit info action alarm
ip audit attack action alarm
ip local pool m3vpnpool 192.168.100.10-192.168.100.30
pdm location 10.10.0.8 255.255.255.255 inside
pdm location 10.10.0.6 255.255.255.255 inside
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 X.X.86.209 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
aaa-server m3aaa protocol radius
aaa-server m3aaa (inside) host 10.0.0.6 33333 timeout 5
http server enable
http 10.10.0.8 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 ESP-3DES-MD5 esp-3des esp-md5-hmac
crypto dynamic-map outside_dyn_map 20 match address outside_cryptomap_dyn_20
crypto dynamic-map outside_dyn_map 20 set transform-set ESP-3DES-MD5
crypto map outside_map 65535 ipsec-isakmp dynamic outside_dyn_map
crypto map outside_map client authentication m3aaa
crypto map outside_map interface outside
isakmp enable outside
isakmp policy 20 authentication pre-share
isakmp policy 20 encryption 3des
isakmp policy 20 hash md5
isakmp policy 20 group 2
isakmp policy 20 lifetime 86400
vpngroup m3vpn address-pool m3vpnpool
vpngroup m3vpn dns-server 10.10.0.4 10.10.0.6
vpngroup m3vpn wins-server 10.10.0.6
vpngroup m3vpn default-domain phl.m3-group.com
vpngroup m3vpn idle-time 1800
vpngroup m3vpn password
telnet 10.10.0.0 255.0.0.0 inside
telnet timeout 5
ssh timeout 5
console timeout 0
terminal width 80
Cryptochecksum:
: end
[OK]

 

[themut]

First of all don't use the keyword any on the ACL, sometimes it screws things up. Use 10.0.0.0/8 instead. Then remove the command:

crypto dynamic-map outside_dyn_map 20 match address outside_cryptomap_dyn_20

and add the following command:

vpngroup m3vpn split-tunnel outside_cryptomap_dyn_20

Clear the SAs and try to establish the tunnel again. Hope it helps!

 

[tek777]

Well, that did not fix it, althoght I put your entries in, and I am sure they helped! I opened up a TAC case for this because I am doing something odd in my scenerio. We are replacing our current firewall with Cisco. (our checkpoint 2000). Here is the setup, TAC said i need to add a permant route to firewall 2, but I think that would be silly to do on every server in my network.

Checkpoint 10.10.0.1
Cisco 10.10.0.200

they told me to try to check the routing done on the networks behind the PIX.

So i gotta add this route on all the machines

route add 192.168.100.0 mask 255.255.255.0 10.0.0.200 -p

here is another cool command they had me run to track ICMP

deb ic t

and

sh cry isa sa
sh cry ips sa

 

[themut]

Well it depends on your network layout but instead of adding the entry on every host I would use 10.10.0.200 as the default gateway on all hosts.

 

[tek777]

well, the problem is, that this is a live network, with users. If I change the gateway to point to the new device, the old users will have issues. I understand now what TAC is saying put static routes on the servers showing what to do with 192 addresses. THe problem is I cant take down the old firewall yet, on the same note, I dont want to put the new firewall without testing it. I will do the routes on the servers, its not a big deal. After I am ready to make the full cutover, then I will change the gateway. Thanks Again!

 

[tek777]

I added the routes, that did not solve the problem. Maybe it is something with DNS or Wins.