<?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: FTD BAD, Something Else ???? in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/ftd-bad-something-else/m-p/4653965#M1092009</link>
    <description>&lt;P&gt;Just a follow up here that I had to re-image the firewall and issue went away.&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 20 Jul 2022 14:41:06 GMT</pubDate>
    <dc:creator>keithcclark71</dc:creator>
    <dc:date>2022-07-20T14:41:06Z</dc:date>
    <item>
      <title>FTD BAD, Something Else ????</title>
      <link>https://community.cisco.com/t5/network-security/ftd-bad-something-else/m-p/4649867#M1091821</link>
      <description>&lt;P&gt;Hey all i have a bizarre situation going on. When I put FTD in place and my laptop only in switch I can ping the FTD internal IP 192.168.3.1 . I pleg FTD into another switch I can still ping it. Now here is the kicker , when I plug in passthrough phones into the switch where PC's are on 192.168.3.0 network they work but as soon as I unplug the cable going from that passthrough phone to the pc and plug back in the FTD spazz's out and is no longer pingable and PC's behind phone spit out IP ADDRESS CONFLICT issue and then when trying to ping the FTD they say unreachable from a AUTO ASSIGNED IP ADDRESS. WTF is going on here?&amp;nbsp;&lt;/P&gt;&lt;P&gt;The interface itself is physically assigned the IP address from within FMC as 192.168.3.1/24. I know in the ASA's you had to specify Vlan then add interface to the VLAN. Do I need to do this or something in the FTD like add this particular interface to VLAN 1 or is this FTD bad??? This is craziest thing I have ever seen&lt;/P&gt;</description>
      <pubDate>Wed, 13 Jul 2022 20:43:09 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ftd-bad-something-else/m-p/4649867#M1091821</guid>
      <dc:creator>keithcclark71</dc:creator>
      <dc:date>2022-07-13T20:43:09Z</dc:date>
    </item>
    <item>
      <title>Re: FTD BAD, Something Else ????</title>
      <link>https://community.cisco.com/t5/network-security/ftd-bad-something-else/m-p/4651115#M1091865</link>
      <description>&lt;P&gt;Make sure where on the internet port have you connected with the POE switch cat5 or cat6 and use the same cable on the PC port where you are connecting the system.&lt;/P&gt;</description>
      <pubDate>Fri, 15 Jul 2022 11:00:37 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ftd-bad-something-else/m-p/4651115#M1091865</guid>
      <dc:creator>Jitendra Kumar</dc:creator>
      <dc:date>2022-07-15T11:00:37Z</dc:date>
    </item>
    <item>
      <title>Re: FTD BAD, Something Else ????</title>
      <link>https://community.cisco.com/t5/network-security/ftd-bad-something-else/m-p/4653965#M1092009</link>
      <description>&lt;P&gt;Just a follow up here that I had to re-image the firewall and issue went away.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 20 Jul 2022 14:41:06 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ftd-bad-something-else/m-p/4653965#M1092009</guid>
      <dc:creator>keithcclark71</dc:creator>
      <dc:date>2022-07-20T14:41:06Z</dc:date>
    </item>
  </channel>
</rss>

