VPN client cannot access inside network resources.

We can connect to the VPN using the Cisco VPN client. But when we try to ping inside addresses they do not respond. The machines with the assigned IP addresses are up and we can ping them from the pix506e.

Here's a copy of the current running config

tchpix506e# show run
: Saved
:
PIX Version 6.3(4)
interface ethernet0 auto
interface ethernet1 auto
nameif ethernet0 outside security0
nameif ethernet1 inside security100
hostname tchpix506e
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 ils 389
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
pager lines 24
mtu outside 1500
mtu inside 1500
ip address outside xxx.xxx.xxx.35 255.255.255.0
ip address inside 192.168.1.254 255.255.255.0
ip audit info action alarm
ip audit attack action alarm
ip local pool vpnpool1 192.168.1.1-192.168.1.253
ip local pool vpnpool2 192.168.2.1-192.168.2.10
pdm history enable
arp timeout 14400
route outside 0.0.0.0 0.0.0.0 xxx.xxx.xxx.1 1
route inside 192.168.2.0 255.255.255.0 128.2.0.114 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 TACACS+ max-failed-attempts 3
aaa-server TACACS+ deadtime 10
aaa-server RADIUS protocol radius
aaa-server RADIUS max-failed-attempts 3
aaa-server RADIUS deadtime 10
aaa-server LOCAL protocol local
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 trmset1 esp-aes-256 esp-sha-hmac
crypto dynamic-map map2 10 set transform-set trmset1
crypto map map1 10 ipsec-isakmp dynamic map2
crypto map map1 interface outside
isakmp enable outside
isakmp identity address
isakmp policy 10 authentication pre-share
isakmp policy 10 encryption aes-256
isakmp policy 10 hash sha
isakmp policy 10 group 2
isakmp policy 10 lifetime 86400
vpngroup tch address-pool vpnpool1
vpngroup tch idle-time 1800
vpngroup tch password ********
vpngroup pim address-pool vpnpool2
vpngroup pim idle-time 1800
vpngroup pim password ********
telnet timeout 5
console timeout 0
terminal width 80
Cryptochecksum:00000000000000000000000000000000
: end
tchpix506e# exit
bjbennettAsked:
Who is Participating?
 
rsivanandanConnect With a Mentor Commented:
You inside interface ip address has changed????? I don't understand.

>>access-list 102 permit ip 128.2.0.0 255.255.0.0 192.168.1.0 255.255.255.0

needs to have this as well;

access-list 102 permit ip 128.2.0.0 255.255.0.0 192.168.2.0 255.255.255.0

this isn't required >>access-list 102 permit ip 128.2.0.0 255.255.0.0 128.2.0.0 255.255.0.0

After doing them, try to connect using the group 'pim' and see if you can ping the inside ip address (Not by names yet since you aren't giving the dns servers to the vpn clients).

See if that works, if not post back. I'm going to catch some sleep now, will look at it tomorrow morning my time :-)

Cheers,
Rajesh
0
 
bugsaifCommented:
you need this line in your config
 
      isakmp nat-traversal 20

Saif
0
 
rsivanandanCommented:
Which VPN group are you having the issue with ? By the way the pix config output is not complete. Post the complete output.


Cheers,
Rajesh
0
The Firewall Audit Checklist

Preparing for a firewall audit today is almost impossible.
AlgoSec, together with some of the largest global organizations and auditors, has created a checklist to follow when preparing for your firewall audit. Simplify risk mitigation while staying compliant all of the time!

 
bjbennettAuthor Commented:
Rajesh,

That is the complete output.. other than the password hashes I took out.

Saif,

That didn't work, although It wasn't in the config.
0
 
rsivanandanCommented:
With this configuration, you would be able to get out from your lan to internet itself, so you need these as well in there;

nat (inside) 1 0 0
Global (outside) 1 interface

and there needs to be one more line which prevents natting when the traffic goes from your internal network to the vpn network which would be of this form;

nat (inside) 0 access-list X

access-list X permit ip <Internal Network> <Subnet Mask> <VPN POOL> <Subnet Mask>

So it is incomplete.

Cheers,
Rajesh
0
 
bjbennettAuthor Commented:
Rajesh,

I've added the commands in you've said to

Here is another copy of the current config


: Saved
:
PIX Version 6.3(4)
interface ethernet0 auto
interface ethernet1 auto
nameif ethernet0 outside security0
hostname tchpix506e
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 ils 389
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 102 permit ip 128.2.0.0 255.255.0.0 192.168.1.0 255.255.255.0
access-list 102 permit ip 128.2.0.0 255.255.0.0 128.2.0.0 255.255.0.0
access-list ACL_1 permit udp any host 128.2.0.222 eq isakmp
access-list ACL_1 permit udp any host 128.2.0.222 eq 4500
access-list 103 permit ip 128.2.0.0 255.255.0.0 192.168.2.0 255.255.255.0
pager lines 24
mtu outside 1500
mtu inside 1500
ip address outside xxx.xxx.xxx.35 255.255.255.0
ip address inside 128.2.0.222 255.255.255.0
ip audit info action alarm
ip audit attack action alarm
ip local pool vpnpool1 192.168.1.1-192.168.1.253
ip local pool vpnpool2 192.168.2.1-192.168.2.10
pdm history enable
arp timeout 14400
global (outside) 1 interface
nat (inside) 0 access-list 103
nat (inside) 1 0.0.0.0 0.0.0.0 0 0
route outside 0.0.0.0 0.0.0.0 xxx.xxx.xxx.1 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 TACACS+ max-failed-attempts 3
aaa-server TACACS+ deadtime 10
aaa-server RADIUS protocol radius
aaa-server RADIUS max-failed-attempts 3
aaa-server RADIUS deadtime 10
aaa-server LOCAL protocol local
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 trmset1 esp-aes-256 esp-sha-hmac
crypto dynamic-map map2 10 set transform-set trmset1
crypto map map1 10 ipsec-isakmp dynamic map2
crypto map map1 interface outside
isakmp enable outside
isakmp identity address
isakmp nat-traversal 20
isakmp policy 10 authentication pre-share
isakmp policy 10 encryption aes-256
isakmp policy 10 hash sha
isakmp policy 10 group 2
isakmp policy 10 lifetime 86400
vpngroup tch address-pool vpnpool1
vpngroup tch split-tunnel 102
vpngroup tch idle-time 1800
vpngroup tch password ********
vpngroup pim address-pool vpnpool2
vpngroup pim split-tunnel 102
vpngroup pim idle-time 1800
vpngroup pim password ********
telnet timeout 5
ssh 129.71.197.0 255.255.255.0 outside
ssh timeout 60
console timeout 0
terminal width 80
Cryptochecksum:9e38c101aecf278ca379de3733a7ae62
: end
tchpix506e(config)#
0
 
bjbennettAuthor Commented:
Rajesh,

Sorry I'd changed the pim ip pool to not conflict with the inside addresses (if this is possible)

I've added the "access-list 102 permit ip 128.2.0.0 255.255.0.0 192.168.2.0 255.255.255.0"
But it still doesn't work. Prehaps I should've not changed the pim pool addresses?
0
 
bugsaifCommented:
since you have now configured access list 102, do this...
      no nat (inside) 0 access-list 103
      nat (inside) 0 access-list 102

and what IP are you tying to ping from the vpn client? try pinging 128.2.0.222

Saif
0
 
rsivanandanCommented:
Bjbennett,

  Your inside ip address on the pix box is different from the first post and second post, I hope your internal address range is 128.2.x.x (I am wondering because these ip addresses are public range).

 Now you're saying that you've changed the vpn pool not to conflict, can you clarify on your internel network ? whether it is 192.x.x.x or 128.x.x.x ???

Cheers,
Rajesh
0
 
bjbennettAuthor Commented:
Rajesh,
The internal network is both 128.x.x.x and 192.x.x.x , i want the one VPN client that can see and talk on to the 128.x.x.x and the other VPN client can see and talk to 192.x.x.x .
I hope this makes thing clear.
Bill
0
 
rsivanandanCommented:
Ok, in that case with the commands I gave you, first lets see if one of them talk to 128 first.

Cheers,
Rajesh
0
 
bjbennettAuthor Commented:
Rajesh,
I cannot ping 128.2.0.222 which is the inside interface.
0
 
rsivanandanCommented:
No, don't try with the inside interface, it is not allowed by default for security reasons on PIX firewall. Try to ping some other machine inside your network.

Cheers,
Rajesh
0
 
bjbennettAuthor Commented:
Rajesh,
Yeah I've tried that.. still doesn't work
We have a server with the ip of 128.2.0.114
0
 
bjbennettAuthor Commented:
Still not working, anyone with any ideas????
0
 
bugsaifCommented:
Can you post your configuration as it is right now and I'll try to give it a shot...
0
 
bjbennettAuthor Commented:
Bugsaif,

Here is the current config.

PIX Version 6.3(4)
interface ethernet0 auto
interface ethernet1 auto
nameif ethernet0 outside security0
nameif ethernet1 inside security100
enable password **** encrypted
passwd **** encrypted
hostname tchpix506e
domain-name tazecommhospital.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 ils 389
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 tftp 69
names
access-list 102 permit ip 128.2.0.0 255.255.0.0 192.168.1.0 255.255.255.0
access-list 102 permit ip 128.2.0.0 255.255.0.0 128.2.0.0 255.255.0.0
access-list 102 permit ip 128.2.0.0 255.255.0.0 129.168.2.0 255.255.255.0
access-list ACL_1 permit udp any host 128.2.0.222 eq isakmp
access-list ACL_1 permit udp any host 128.2.0.222 eq 4500
access-list 103 permit ip 128.2.0.0 255.255.0.0 192.168.2.0 255.255.255.0
pager lines 24
mtu outside 1500
mtu inside 1500
ip address outside xxx.xxx.xxx.35 255.255.255.0
ip address inside 128.2.0.222 255.255.255.0
ip audit info action alarm
ip audit attack action alarm
ip local pool vpnpool1 192.168.1.1-192.168.1.253
ip local pool vpnpool2 192.168.2.1-192.168.2.10
pdm history enable
arp timeout 14400
global (outside) 1 interface
nat (inside) 0 access-list 102
nat (inside) 1 0.0.0.0 0.0.0.0 0 0
route outside 0.0.0.0 0.0.0.0 xxx.xxx.xxx.1 1
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 TACACS+ max-failed-attempts 3
aaa-server TACACS+ deadtime 10
aaa-server RADIUS protocol radius
aaa-server RADIUS max-failed-attempts 3
aaa-server RADIUS deadtime 10
aaa-server LOCAL protocol local
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 trmset1 esp-aes-256 esp-sha-hmac
crypto dynamic-map map2 10 set transform-set trmset1
crypto map map1 10 ipsec-isakmp dynamic map2
crypto map map1 interface outside
isakmp enable outside
isakmp identity address
isakmp nat-traversal 20
isakmp identity address
isakmp nat-traversal 20
isakmp policy 10 authentication pre-share
isakmp policy 10 encryption aes-256
isakmp policy 10 hash sha
isakmp policy 10 group 2
isakmp policy 10 lifetime 86400
vpngroup tch address-pool vpnpool1
vpngroup tch split-tunnel 102
vpngroup tch idle-time 1800
vpngroup tch password ********
vpngroup pim address-pool vpnpool2
vpngroup pim split-tunnel 102
vpngroup pim idle-time 1800
vpngroup pim password ********
telnet timeout 5
ssh xxx.xxx.xxx.0 255.255.255.0 outside
ssh timeout 60
console timeout 0
terminal width 80
Cryptochecksum:a42a75dba1e55c08c1450b7cc1810fa9
: end
[OK]
0
 
bugsaifConnect With a Mentor Commented:
ok, lets make a few modifications and try again... you can make a note of these changes and put them back later... I'm just trying to narrow down where exactly the issue is...

        no access-list 102 permit ip 128.2.0.0 255.255.0.0 128.2.0.0 255.255.0.0
        no vpngroup tch split-tunnel 102
        no vpngroup pim split-tunnel 102
        no isakmp nat-traversal 20

first try pinging from your inside interface to an inside server/PC...
then try from the vpn client...
if it still won't work, we'll attempt something bolder... :)


0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.