<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: A strange problem - pix 501 in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/a-strange-problem-pix-501/m-p/422257#M558599</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Seems like you have some routing problems.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The VPN Clients should use a separate Network Range that is diffrent from the inside network. As the netmask is choosen by the Class of network it is best to use a Class C network.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For example: 192.168.1.0 / 24 for the inside network&lt;/P&gt;&lt;P&gt;and 192.168.2.0 /24 for the VPN Pool. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Probably a few of this commands as "isakmp nat-traversal" will not work as this was added in the PIX OS 6.3.x code.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Config example:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-list NONAT permit ip Internalnet ISubnet VPN-Pool 255.255.255.0&lt;/P&gt;&lt;P&gt;nat (inside) 0 access-list NONAT&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-list DYN-VPN-ACL permit ip Internalnet ISubnet VPN-Pool 255.255.255.0&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;aaa-server LOCAL protocol local&lt;/P&gt;&lt;P&gt;aaa authentication secure-http-client&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;sysopt connection permit-ipsec&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;crypto ipsec transform-set TRANS esp-3des esp-md5-hmac&lt;/P&gt;&lt;P&gt;crypto dynamic-map outside_dyn_map 20 match address DYN-VPN-ACL&lt;/P&gt;&lt;P&gt;crypto dynamic-map outside_dyn_map 20 set transform-set TRANS&lt;/P&gt;&lt;P&gt;crypto map REMOTE 65535 ipsec-isakmp dynamic outside_dyn_map&lt;/P&gt;&lt;P&gt;crypto map REMOTE client authentication LOCAL&lt;/P&gt;&lt;P&gt;crypto map REMOTE interface outside&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;isakmp enable outside&lt;/P&gt;&lt;P&gt;isakmp identity address&lt;/P&gt;&lt;P&gt;isakmp nat-traversal 20&lt;/P&gt;&lt;P&gt;isakmp policy 10 authentication pre-share&lt;/P&gt;&lt;P&gt;isakmp policy 10 encryption 3des&lt;/P&gt;&lt;P&gt;isakmp policy 10 hash md5&lt;/P&gt;&lt;P&gt;isakmp policy 10 group 2&lt;/P&gt;&lt;P&gt;isakmp policy 10 lifetime 86400&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ip local pool VPNPool x.y.z.1-x.y.z.254&lt;/P&gt;&lt;P&gt;vpngroup VPNGroup address-pool VPNPool&lt;/P&gt;&lt;P&gt;vpngroup VPNGroup dns-server dns2 dns1&lt;/P&gt;&lt;P&gt;vpngroup VPNGroup default-domain localdomain&lt;/P&gt;&lt;P&gt;vpngroup VPNGroup idle-time 1800&lt;/P&gt;&lt;P&gt;vpngroup VPNGroup password grouppassword&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;username vpnclient password vpnclient-password &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;sincerely&lt;/P&gt;&lt;P&gt;Patrick&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 06 May 2005 11:03:10 GMT</pubDate>
    <dc:creator>Patrick Iseli</dc:creator>
    <dc:date>2005-05-06T11:03:10Z</dc:date>
    <item>
      <title>A strange problem - pix 501</title>
      <link>https://community.cisco.com/t5/network-security/a-strange-problem-pix-501/m-p/422256#M558590</link>
      <description>&lt;P&gt;I connect with vpn client v 4.0.3f to the pix 501 v6.2, however I can access resources on the remote lan only after I initiate some kind of connection from the remote lan to the vpn client (a ping for example).Could the fact that I don't get any dhcp,dns or wins servers cause this problem?&lt;/P&gt;&lt;P&gt;(I've noticed that when I run ipconfig/all on the client pc I get only ip-sub-gateway, no dhcp,dns or wins servers are shown).The pix is not configured as dhcp server - I have an internal dhcp server&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 08:07:39 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/a-strange-problem-pix-501/m-p/422256#M558590</guid>
      <dc:creator>dagesh4</dc:creator>
      <dc:date>2020-02-21T08:07:39Z</dc:date>
    </item>
    <item>
      <title>Re: A strange problem - pix 501</title>
      <link>https://community.cisco.com/t5/network-security/a-strange-problem-pix-501/m-p/422257#M558599</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Seems like you have some routing problems.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The VPN Clients should use a separate Network Range that is diffrent from the inside network. As the netmask is choosen by the Class of network it is best to use a Class C network.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For example: 192.168.1.0 / 24 for the inside network&lt;/P&gt;&lt;P&gt;and 192.168.2.0 /24 for the VPN Pool. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Probably a few of this commands as "isakmp nat-traversal" will not work as this was added in the PIX OS 6.3.x code.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Config example:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-list NONAT permit ip Internalnet ISubnet VPN-Pool 255.255.255.0&lt;/P&gt;&lt;P&gt;nat (inside) 0 access-list NONAT&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-list DYN-VPN-ACL permit ip Internalnet ISubnet VPN-Pool 255.255.255.0&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;aaa-server LOCAL protocol local&lt;/P&gt;&lt;P&gt;aaa authentication secure-http-client&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;sysopt connection permit-ipsec&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;crypto ipsec transform-set TRANS esp-3des esp-md5-hmac&lt;/P&gt;&lt;P&gt;crypto dynamic-map outside_dyn_map 20 match address DYN-VPN-ACL&lt;/P&gt;&lt;P&gt;crypto dynamic-map outside_dyn_map 20 set transform-set TRANS&lt;/P&gt;&lt;P&gt;crypto map REMOTE 65535 ipsec-isakmp dynamic outside_dyn_map&lt;/P&gt;&lt;P&gt;crypto map REMOTE client authentication LOCAL&lt;/P&gt;&lt;P&gt;crypto map REMOTE interface outside&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;isakmp enable outside&lt;/P&gt;&lt;P&gt;isakmp identity address&lt;/P&gt;&lt;P&gt;isakmp nat-traversal 20&lt;/P&gt;&lt;P&gt;isakmp policy 10 authentication pre-share&lt;/P&gt;&lt;P&gt;isakmp policy 10 encryption 3des&lt;/P&gt;&lt;P&gt;isakmp policy 10 hash md5&lt;/P&gt;&lt;P&gt;isakmp policy 10 group 2&lt;/P&gt;&lt;P&gt;isakmp policy 10 lifetime 86400&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ip local pool VPNPool x.y.z.1-x.y.z.254&lt;/P&gt;&lt;P&gt;vpngroup VPNGroup address-pool VPNPool&lt;/P&gt;&lt;P&gt;vpngroup VPNGroup dns-server dns2 dns1&lt;/P&gt;&lt;P&gt;vpngroup VPNGroup default-domain localdomain&lt;/P&gt;&lt;P&gt;vpngroup VPNGroup idle-time 1800&lt;/P&gt;&lt;P&gt;vpngroup VPNGroup password grouppassword&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;username vpnclient password vpnclient-password &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;sincerely&lt;/P&gt;&lt;P&gt;Patrick&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 06 May 2005 11:03:10 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/a-strange-problem-pix-501/m-p/422257#M558599</guid>
      <dc:creator>Patrick Iseli</dc:creator>
      <dc:date>2005-05-06T11:03:10Z</dc:date>
    </item>
  </channel>
</rss>

