<?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 Authenticate against external windowsdb member server in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/authenticate-against-external-windowsdb-member-server/m-p/389868#M435370</link>
    <description>&lt;P&gt;I would like to know if anyone has been able to get the ACS appliance version to authenticate users against a Windows Member Server not a DC (no AD). &lt;/P&gt;</description>
    <pubDate>Sun, 10 Mar 2019 21:00:36 GMT</pubDate>
    <dc:creator>mike.iacovacci</dc:creator>
    <dc:date>2019-03-10T21:00:36Z</dc:date>
    <item>
      <title>Authenticate against external windowsdb member server</title>
      <link>https://community.cisco.com/t5/network-access-control/authenticate-against-external-windowsdb-member-server/m-p/389868#M435370</link>
      <description>&lt;P&gt;I would like to know if anyone has been able to get the ACS appliance version to authenticate users against a Windows Member Server not a DC (no AD). &lt;/P&gt;</description>
      <pubDate>Sun, 10 Mar 2019 21:00:36 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/authenticate-against-external-windowsdb-member-server/m-p/389868#M435370</guid>
      <dc:creator>mike.iacovacci</dc:creator>
      <dc:date>2019-03-10T21:00:36Z</dc:date>
    </item>
    <item>
      <title>Re: Authenticate against external windowsdb member server</title>
      <link>https://community.cisco.com/t5/network-access-control/authenticate-against-external-windowsdb-member-server/m-p/389869#M435374</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Sure, but it can take a little bit of configuring, especially if you want to authenticate users in other trusted domains that the member server is not actually a member of.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Read the following and it should give you a good insight into what's needed:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;    &lt;A class="jive-link-custom" href="http://www.cisco.com/univercd/cc/td/doc/product/access/acs_soft/csacs4nt/acs33/install/inst02.htm#wp981718" target="_blank"&gt;http://www.cisco.com/univercd/cc/td/doc/product/access/acs_soft/csacs4nt/acs33/install/inst02.htm#wp981718&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Specifically steps 5, 6 and 7 should get you going.  I've never had to do Step 2 personally.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 10 Feb 2005 04:01:14 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/authenticate-against-external-windowsdb-member-server/m-p/389869#M435374</guid>
      <dc:creator>gfullage</dc:creator>
      <dc:date>2005-02-10T04:01:14Z</dc:date>
    </item>
    <item>
      <title>Re: Authenticate against external windowsdb member server</title>
      <link>https://community.cisco.com/t5/network-access-control/authenticate-against-external-windowsdb-member-server/m-p/389870#M435391</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The steps seem to be for running Cisco ACS on a Windows Member Server. I have a Cisco ACS Engine, and want to check a member servers local user database (no AD domain) for user/group on ACS. I noticed that ACS supports "AD", but what about the regular local user db. I am trying to avoid creating a domain to manage the users.  &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 10 Feb 2005 13:16:38 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/authenticate-against-external-windowsdb-member-server/m-p/389870#M435391</guid>
      <dc:creator>mike.iacovacci</dc:creator>
      <dc:date>2005-02-10T13:16:38Z</dc:date>
    </item>
    <item>
      <title>Re: Authenticate against external windowsdb member server</title>
      <link>https://community.cisco.com/t5/network-access-control/authenticate-against-external-windowsdb-member-server/m-p/389871#M435417</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;My bad, sorry.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When using the appliance you need to use the Remote Agent for Windows, the appliance will then talk to this agent to authenticate users in its SAM or AD database.  You need this since the Appliance is not part of any domain, so it needs to pass off the usernames/passwords to a Windows server that can authenticate users.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can read about it here:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="http://www.cisco.com/univercd/cc/td/doc/product/access/acs_soft/csacsapp/raig/rawi.htm" target="_blank"&gt;http://www.cisco.com/univercd/cc/td/doc/product/access/acs_soft/csacsapp/raig/rawi.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Basically install it on the member server and you should be good to go, it will automatically use the local SAM database to check for usernames/passwords.    This is actually easier to set up than if you were trying to authenticate to a domain, since there's really nothing for you to do other than install the agent.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 10 Feb 2005 23:30:34 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/authenticate-against-external-windowsdb-member-server/m-p/389871#M435417</guid>
      <dc:creator>gfullage</dc:creator>
      <dc:date>2005-02-10T23:30:34Z</dc:date>
    </item>
  </channel>
</rss>

