<?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: Failed Attempts in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/failed-attempts/m-p/264120#M433774</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I have seen this error when terminal servers are used to connect to router con and aux ports.  The banner was comming from the terminal server.  I had to turn off the banner and exec on the terminal server port that was connected to the routers to fix the problem.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 19 Aug 2004 17:55:30 GMT</pubDate>
    <dc:creator>MARK BAKER</dc:creator>
    <dc:date>2004-08-19T17:55:30Z</dc:date>
    <item>
      <title>Failed Attempts</title>
      <link>https://community.cisco.com/t5/network-access-control/failed-attempts/m-p/264119#M433770</link>
      <description>&lt;P&gt;Hi, I have a number of routers that are constantly creating failed authentication attempts in our ACS logs. Sometime the username is a part of the router banner or a part of a console message that is in the log file. We have secured CON and AUX ports with TACACS and I think console messages are somehow being sent to CON and AUX ports. These messages are appearing as failed attempts on the ACS log as the username is not known. Is this a common error? The below is a part of the router config.   &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;line con 0&lt;/P&gt;&lt;P&gt; session-timeout 30&lt;/P&gt;&lt;P&gt; exec-timeout 15 0&lt;/P&gt;&lt;P&gt; password &amp;lt;removed&amp;gt;&lt;/P&gt;&lt;P&gt; login authentication CON_0&lt;/P&gt;&lt;P&gt;line aux 0&lt;/P&gt;&lt;P&gt; exec-timeout 15 0&lt;/P&gt;&lt;P&gt; login authentication AUX_0&lt;/P&gt;&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Sun, 10 Mar 2019 20:45:28 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/failed-attempts/m-p/264119#M433770</guid>
      <dc:creator>mark.edwards</dc:creator>
      <dc:date>2019-03-10T20:45:28Z</dc:date>
    </item>
    <item>
      <title>Re: Failed Attempts</title>
      <link>https://community.cisco.com/t5/network-access-control/failed-attempts/m-p/264120#M433774</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I have seen this error when terminal servers are used to connect to router con and aux ports.  The banner was comming from the terminal server.  I had to turn off the banner and exec on the terminal server port that was connected to the routers to fix the problem.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 19 Aug 2004 17:55:30 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/failed-attempts/m-p/264120#M433774</guid>
      <dc:creator>MARK BAKER</dc:creator>
      <dc:date>2004-08-19T17:55:30Z</dc:date>
    </item>
  </channel>
</rss>

