<?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: ACS 3.1 Software in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/acs-3-1-software/m-p/272042#M434869</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;ACS can do both.  If you have client devices that need to use both protocols you will need to have two entries for each in the network configuration, one for tacacs and one for radius.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can enable the varius tacacs and radius config options in the interface section of ACS.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 12 Feb 2004 15:20:00 GMT</pubDate>
    <dc:creator>d.parks</dc:creator>
    <dc:date>2004-02-12T15:20:00Z</dc:date>
    <item>
      <title>ACS 3.1 Software</title>
      <link>https://community.cisco.com/t5/network-access-control/acs-3-1-software/m-p/272040#M434866</link>
      <description>&lt;P&gt;Can ACS 3.1 software be configured to be both a Tacacs server and radius server at the same time? Or do I need two different physical server running tacacs and radius independantly?&lt;/P&gt;</description>
      <pubDate>Sun, 10 Mar 2019 14:39:47 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/acs-3-1-software/m-p/272040#M434866</guid>
      <dc:creator>craig.everitt</dc:creator>
      <dc:date>2019-03-10T14:39:47Z</dc:date>
    </item>
    <item>
      <title>Re: ACS 3.1 Software</title>
      <link>https://community.cisco.com/t5/network-access-control/acs-3-1-software/m-p/272041#M434868</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Craig:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Both can run on the same server.  I've used both on the same box to authenticate router/switch login (via tacacs) and to authenticate dial-out services (via radius).  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Rich&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 12 Feb 2004 15:16:39 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/acs-3-1-software/m-p/272041#M434868</guid>
      <dc:creator>r.crist</dc:creator>
      <dc:date>2004-02-12T15:16:39Z</dc:date>
    </item>
    <item>
      <title>Re: ACS 3.1 Software</title>
      <link>https://community.cisco.com/t5/network-access-control/acs-3-1-software/m-p/272042#M434869</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;ACS can do both.  If you have client devices that need to use both protocols you will need to have two entries for each in the network configuration, one for tacacs and one for radius.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can enable the varius tacacs and radius config options in the interface section of ACS.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 12 Feb 2004 15:20:00 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/acs-3-1-software/m-p/272042#M434869</guid>
      <dc:creator>d.parks</dc:creator>
      <dc:date>2004-02-12T15:20:00Z</dc:date>
    </item>
  </channel>
</rss>

