<?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: ASA generating 106001 syslog iD in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/asa-generating-106001-syslog-id/m-p/1253966#M828601</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Handsy,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please find the sample Log entry and access-list. On the log file the IP's which you see some of them are valid Yahoo,MSN, and Google Chat server IP's and some does not get resolved to any.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Kindly let me know if you need more info from my side.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Rajiv&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 06 Aug 2009 04:14:43 GMT</pubDate>
    <dc:creator>rdodderi</dc:creator>
    <dc:date>2009-08-06T04:14:43Z</dc:date>
    <item>
      <title>ASA generating 106001 syslog iD</title>
      <link>https://community.cisco.com/t5/network-security/asa-generating-106001-syslog-id/m-p/1253963#M828533</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I can see huge syslog generation with syslog ID 106001 and also random users across my network are facing Messenger's disconnection and reconnection.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 16:02:48 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-generating-106001-syslog-id/m-p/1253963#M828533</guid>
      <dc:creator>rdodderi</dc:creator>
      <dc:date>2019-03-11T16:02:48Z</dc:date>
    </item>
    <item>
      <title>Re: ASA generating 106001 syslog iD</title>
      <link>https://community.cisco.com/t5/network-security/asa-generating-106001-syslog-id/m-p/1253964#M828552</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Here's an explaination.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="http://www.cisco.com/en/US/docs/security/asa/asa72/system/message/logmsgs.html#wp1279735" target="_blank"&gt;http://www.cisco.com/en/US/docs/security/asa/asa72/system/message/logmsgs.html#wp1279735&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 05 Aug 2009 12:16:59 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-generating-106001-syslog-id/m-p/1253964#M828552</guid>
      <dc:creator>Collin Clark</dc:creator>
      <dc:date>2009-08-05T12:16:59Z</dc:date>
    </item>
    <item>
      <title>Re: ASA generating 106001 syslog iD</title>
      <link>https://community.cisco.com/t5/network-security/asa-generating-106001-syslog-id/m-p/1253965#M828573</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;More info required. Please paste an example log entry, and also the access-list entries that the users should be hitting for Messenger.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 05 Aug 2009 12:59:51 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-generating-106001-syslog-id/m-p/1253965#M828573</guid>
      <dc:creator>handsy</dc:creator>
      <dc:date>2009-08-05T12:59:51Z</dc:date>
    </item>
    <item>
      <title>Re: ASA generating 106001 syslog iD</title>
      <link>https://community.cisco.com/t5/network-security/asa-generating-106001-syslog-id/m-p/1253966#M828601</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Handsy,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please find the sample Log entry and access-list. On the log file the IP's which you see some of them are valid Yahoo,MSN, and Google Chat server IP's and some does not get resolved to any.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Kindly let me know if you need more info from my side.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Rajiv&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 06 Aug 2009 04:14:43 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-generating-106001-syslog-id/m-p/1253966#M828601</guid>
      <dc:creator>rdodderi</dc:creator>
      <dc:date>2009-08-06T04:14:43Z</dc:date>
    </item>
    <item>
      <title>Re: ASA generating 106001 syslog iD</title>
      <link>https://community.cisco.com/t5/network-security/asa-generating-106001-syslog-id/m-p/1253967#M828628</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I think the key to this problem is that an IP from inside your network, namely 220.x.x.123 is getting blocked on it's return, i.e. it's allowed out, but not back in.&lt;/P&gt;&lt;P&gt;Do you have an ACL entry to allow HTTP access to this IP? (I can't tell as you have xxxx'ed them out).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 06 Aug 2009 17:18:10 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-generating-106001-syslog-id/m-p/1253967#M828628</guid>
      <dc:creator>handsy</dc:creator>
      <dc:date>2009-08-06T17:18:10Z</dc:date>
    </item>
  </channel>
</rss>

