<?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 Reverse telnet with AAA in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/reverse-telnet-with-aaa/m-p/45639#M288</link>
    <description>&lt;P&gt;We have a 2611 router used as a access server for some SUN servers. The 2611 async interface connect with the SUN server's console port. Using the reverse telnet the Admin can connect with the SUN server's console. Problem happened after I configured the AAA for authentication. We noticed a lot of login failed attempt on TACACS server log file. That's the SUN server's console port send out some kind of system information and the 2611 treat it as the user login information. Then it cuase this kind of failed attampt on TACACS server. Is there any way we can get rid of this failed attempt informations except disable the AAA on 2611.&lt;/P&gt;</description>
    <pubDate>Fri, 21 Feb 2020 18:04:45 GMT</pubDate>
    <dc:creator>yang.h</dc:creator>
    <dc:date>2020-02-21T18:04:45Z</dc:date>
    <item>
      <title>Reverse telnet with AAA</title>
      <link>https://community.cisco.com/t5/network-access-control/reverse-telnet-with-aaa/m-p/45639#M288</link>
      <description>&lt;P&gt;We have a 2611 router used as a access server for some SUN servers. The 2611 async interface connect with the SUN server's console port. Using the reverse telnet the Admin can connect with the SUN server's console. Problem happened after I configured the AAA for authentication. We noticed a lot of login failed attempt on TACACS server log file. That's the SUN server's console port send out some kind of system information and the 2611 treat it as the user login information. Then it cuase this kind of failed attampt on TACACS server. Is there any way we can get rid of this failed attempt informations except disable the AAA on 2611.&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 18:04:45 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/reverse-telnet-with-aaa/m-p/45639#M288</guid>
      <dc:creator>yang.h</dc:creator>
      <dc:date>2020-02-21T18:04:45Z</dc:date>
    </item>
    <item>
      <title>Re: Reverse telnet with AAA</title>
      <link>https://community.cisco.com/t5/network-access-control/reverse-telnet-with-aaa/m-p/45640#M289</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Try placing this command on the line of the 2611 with issues:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;no exec&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 29 Oct 2002 17:12:57 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/reverse-telnet-with-aaa/m-p/45640#M289</guid>
      <dc:creator>4brown</dc:creator>
      <dc:date>2002-10-29T17:12:57Z</dc:date>
    </item>
    <item>
      <title>Re: Reverse telnet with AAA</title>
      <link>https://community.cisco.com/t5/network-access-control/reverse-telnet-with-aaa/m-p/45641#M290</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Looks it's working. Thanks a lot.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 29 Oct 2002 17:36:38 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/reverse-telnet-with-aaa/m-p/45641#M290</guid>
      <dc:creator>yang.h</dc:creator>
      <dc:date>2002-10-29T17:36:38Z</dc:date>
    </item>
  </channel>
</rss>

