Help please - Cisco PIX 510 & VPN

Aug 08, 2006 1 Replies

Hello there,



I need help for setting up VPN. I have very basic knowlege of networking and I have used GUI to configure basic routing and VPN (using VPN client).



By using the following configuration, I am able to connect using VPN client accessing computer inside the network e.g I can ping, use remote desktop etc. However, once connected I do not know how can I configure my client to redirect all traffic to VPN tunnel (including DNS requests).



If I would use split-tunneling, then I can surf using client but cannot access my other computer on insider interface. My expectation is:


  1. Use VPN so that I can see my computer on inside interface
  2. Use VPN tunnel to re-route all traffic through the host (VPN / external interface)
  3. Do not use local DNS (from ISP on the client e.g. wireless access) but transfer any DNS requests also though VPN tunnel.

I appreciate if someone can help me.



Thank you. Best regards.


: Saved : Written by enable_15 at 19:45:25.452 MDT Tue Aug 8 2006 PIX Version 6.3(5) interface ethernet0 auto interface ethernet1 100full nameif ethernet0 outside security0 nameif ethernet1 inside security100 enable password was-----here encrypted passwd goes---here--- encrypted hostname pix domain-name domainname.com clock timezone MST -7 clock summer-time MDT recurring 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.1.0



255.255.255.224 access-list outside_cryptomap_dyn_20 permit ip any 192.168.1.0
255.255.255.224 pager lines 24 mtu outside 1500 mtu inside 1500 ip address outside dhcp setroute ip address inside 192.168.1.1 255.255.255.0 ip audit info action alarm ip audit attack action alarm ip local pool vpn-dhcp 192.168.1.10-192.168.1.19 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 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 sip-disconnect 0:02:00 sip-invite 0:03: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 http server enable http 192.168.1.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-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 LOCAL 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 homevpn address-pool vpn-dhcp vpngroup homevpn dns-server 64.59.135.143 64.59.135.145 vpngroup homevpn default-domain vpn.domainname.com vpngroup homevpn idle-time 1800 vpngroup homevpn password ******** telnet timeout 5 ssh timeout 5 console timeout 0 dhcpd address 192.168.1.50-192.168.1.99 inside dhcpd dns 64.59.135.143 64.59.135.145 dhcpd lease 3600 dhcpd ping_timeout 750 dhcpd domain domainname.com dhcpd auto_config outside dhcpd enable inside username remoteuser password goes---here--- encrypted privilege 15 terminal width 80 Cryptochecksum:value---goes --- here pix#

To answer your expectations (hopefully)

  1. I assume this part is working for you since you said you can do this.
  2. This should be happening already since you don't have a split-tunnel-policy setup.
  3. Your host should be using the DNS server that is configured for the tunnel. You set it up to be 64.59.135.143, then 64.59.135.145. If it fails to reach those DNS servers it may fall back to the local LAN DNS, however it should not be able to reach that DNS host either since you don't have split tunneling setup.

Try removing this line: crypto dynamic-map outside_dyn_map 20 match address outside_cryptomap_dyn_20

I believe what you have done is setup an encryption domain that only includes 192.168.1.0 255.255.255.224, which means this will be the only traffic allowed through the tunnel.

Hopefully that will take care of the problem for you. If that doesn't fix your DNS issue, it could be because of the binding order your client is using. The binding order for your VPN connection should be at the top of the list in the Advanced Settings dialog box of the Network and Dial-up Connections tool. For more information on the binding order, check out this KB article:

formatting link
Good Luck, Kevin

snipped-for-privacy@afzalbaig.com wrote:

Join the Discussion

Have something to add? Share your thoughts — no account required.

Didn't find your answer?

Ask the community — no account required