<?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 Pix 525 collission on eth0, eth1, problematic inbound smtp in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/pix-525-collission-on-eth0-eth1-problematic-inbound-smtp/m-p/391113#M558857</link>
    <description>&lt;P&gt;Hello there;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We have a Pix 525 @ corp headquarters which serves as a firewall &amp;amp; VPN endpoint for several branch offices.  We've had this config for 1+ years.  Lately, we seem to be missing some email traffic destined to our email server, and telneting to our email server on port 25 fails coming from certain subnets, but works for others.  We are telneting to the server IP, not dns name.  There seems to be no rhyme or reason to this in terms of some subnets working versus not.  Also, I've noticed the number of collision on eth0 &amp;amp; eth1 increasing.  I'm wondering if we have a hardware problem, or routing, ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;</description>
    <pubDate>Fri, 21 Feb 2020 08:06:44 GMT</pubDate>
    <dc:creator>jonathan.green</dc:creator>
    <dc:date>2020-02-21T08:06:44Z</dc:date>
    <item>
      <title>Pix 525 collission on eth0, eth1, problematic inbound smtp</title>
      <link>https://community.cisco.com/t5/network-security/pix-525-collission-on-eth0-eth1-problematic-inbound-smtp/m-p/391113#M558857</link>
      <description>&lt;P&gt;Hello there;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We have a Pix 525 @ corp headquarters which serves as a firewall &amp;amp; VPN endpoint for several branch offices.  We've had this config for 1+ years.  Lately, we seem to be missing some email traffic destined to our email server, and telneting to our email server on port 25 fails coming from certain subnets, but works for others.  We are telneting to the server IP, not dns name.  There seems to be no rhyme or reason to this in terms of some subnets working versus not.  Also, I've noticed the number of collision on eth0 &amp;amp; eth1 increasing.  I'm wondering if we have a hardware problem, or routing, ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 08:06:44 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-525-collission-on-eth0-eth1-problematic-inbound-smtp/m-p/391113#M558857</guid>
      <dc:creator>jonathan.green</dc:creator>
      <dc:date>2020-02-21T08:06:44Z</dc:date>
    </item>
    <item>
      <title>Re: Pix 525 collission on eth0, eth1, problematic inbound smtp</title>
      <link>https://community.cisco.com/t5/network-security/pix-525-collission-on-eth0-eth1-problematic-inbound-smtp/m-p/391114#M558858</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Collision are normal in Half-Duplex configurations. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Have you checked the setup of your PIX Interfaces and also the setup of the Switch. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Set Both to 100MB Full-Duplex and the Collisions should disappear.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Check:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;show interface&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>Wed, 27 Apr 2005 23:18:19 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-525-collission-on-eth0-eth1-problematic-inbound-smtp/m-p/391114#M558858</guid>
      <dc:creator>Patrick Iseli</dc:creator>
      <dc:date>2005-04-27T23:18:19Z</dc:date>
    </item>
  </channel>
</rss>

