<?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: Inside Interface Addressing problem - PIX 506E in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/inside-interface-addressing-problem-pix-506e/m-p/293717#M593151</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks Jay - That was the resolution. I had evidently only tried that approach with the PDM and not CLI. Thanks Again!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;          Jack&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sun, 25 Apr 2004 07:11:47 GMT</pubDate>
    <dc:creator>JDShelley</dc:creator>
    <dc:date>2004-04-25T07:11:47Z</dc:date>
    <item>
      <title>Inside Interface Addressing problem - PIX 506E</title>
      <link>https://community.cisco.com/t5/network-security/inside-interface-addressing-problem-pix-506e/m-p/293715#M593139</link>
      <description>&lt;P&gt;I have encountered the following problem, I cannot get the PIX "inside" interface to accept the needed IP address of 10.0.0.250 255.255.255.0 on a network I inherited. I get the following message: "Interface address is not on same subnet as dhcp pool". I get this even when DHCP is disabled in the PIX config. In frustration I have even tried the mask at 255.0.0.0 and configuring DHCP to hand out 10.0.0.x address range IPs. When trying to set DHCP to the 10.x.x.x range I get a similar message: Pool addresses not on same subnet as "inside" interface. I have reset the PIX to default settings several times during theses attempts just to get back to a clean start point. Any help or feedback would be greatly appreciated.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;            Jack&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 07:21:40 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/inside-interface-addressing-problem-pix-506e/m-p/293715#M593139</guid>
      <dc:creator>JDShelley</dc:creator>
      <dc:date>2020-02-21T07:21:40Z</dc:date>
    </item>
    <item>
      <title>Re: Inside Interface Addressing problem - PIX 506E</title>
      <link>https://community.cisco.com/t5/network-security/inside-interface-addressing-problem-pix-506e/m-p/293716#M593146</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Jack,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You'll need to remove the dhcpd address range in order to change the IP address assigned to the interface serving as the DHCP server interface. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;To do this try:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;PIX(config)# no dhcpd address 192.168.1.10-192.168.1.50 inside &lt;/P&gt;&lt;P&gt;DHCPD disabled on inside interface because address pool is removed &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Now set your inside interface ip address,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;gt; PIX(config)# ip address inside &lt;IP_ADDRS&gt; &lt;MASK&gt;&lt;/MASK&gt;&lt;/IP_ADDRS&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Save with cmd - write mem.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this helps.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Jay&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 23 Apr 2004 14:52:36 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/inside-interface-addressing-problem-pix-506e/m-p/293716#M593146</guid>
      <dc:creator>jmia</dc:creator>
      <dc:date>2004-04-23T14:52:36Z</dc:date>
    </item>
    <item>
      <title>Re: Inside Interface Addressing problem - PIX 506E</title>
      <link>https://community.cisco.com/t5/network-security/inside-interface-addressing-problem-pix-506e/m-p/293717#M593151</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks Jay - That was the resolution. I had evidently only tried that approach with the PDM and not CLI. Thanks Again!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;          Jack&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 25 Apr 2004 07:11:47 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/inside-interface-addressing-problem-pix-506e/m-p/293717#M593151</guid>
      <dc:creator>JDShelley</dc:creator>
      <dc:date>2004-04-25T07:11:47Z</dc:date>
    </item>
  </channel>
</rss>

