<?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 windows database authentication broken after upgrade in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/windows-database-authentication-broken-after-upgrade/m-p/740077#M420856</link>
    <description>&lt;P&gt;We upgraded from ACS 3.3 to 4.0 and it broke our authentication which is pointed to our Windows DC. The failed attempts log only shows "Internal error" when trying to authenticate. Anyone experience this?&lt;/P&gt;</description>
    <pubDate>Sun, 10 Mar 2019 22:08:06 GMT</pubDate>
    <dc:creator>mjsully</dc:creator>
    <dc:date>2019-03-10T22:08:06Z</dc:date>
    <item>
      <title>windows database authentication broken after upgrade</title>
      <link>https://community.cisco.com/t5/network-access-control/windows-database-authentication-broken-after-upgrade/m-p/740077#M420856</link>
      <description>&lt;P&gt;We upgraded from ACS 3.3 to 4.0 and it broke our authentication which is pointed to our Windows DC. The failed attempts log only shows "Internal error" when trying to authenticate. Anyone experience this?&lt;/P&gt;</description>
      <pubDate>Sun, 10 Mar 2019 22:08:06 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/windows-database-authentication-broken-after-upgrade/m-p/740077#M420856</guid>
      <dc:creator>mjsully</dc:creator>
      <dc:date>2019-03-10T22:08:06Z</dc:date>
    </item>
    <item>
      <title>Re: windows database authentication broken after upgrade</title>
      <link>https://community.cisco.com/t5/network-access-control/windows-database-authentication-broken-after-upgrade/m-p/740078#M420857</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I think the problem may be with Proxy distribution table config issue. Following link may help you&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="http://www.cisco.com/en/US/products/sw/secursw/ps2086/prod_release_note09186a008079fc44.html" target="_blank"&gt;http://www.cisco.com/en/US/products/sw/secursw/ps2086/prod_release_note09186a008079fc44.html&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 08 May 2007 15:48:36 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/windows-database-authentication-broken-after-upgrade/m-p/740078#M420857</guid>
      <dc:creator>irisrios</dc:creator>
      <dc:date>2007-05-08T15:48:36Z</dc:date>
    </item>
    <item>
      <title>Re: windows database authentication broken after upgrade</title>
      <link>https://community.cisco.com/t5/network-access-control/windows-database-authentication-broken-after-upgrade/m-p/740079#M420858</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I havent tried looking at the details for ver3 but maybe the remote agent needs to be upgraded to ver4 if it hasnt already?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 08 May 2007 20:19:25 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/windows-database-authentication-broken-after-upgrade/m-p/740079#M420858</guid>
      <dc:creator>jvr775</dc:creator>
      <dc:date>2007-05-08T20:19:25Z</dc:date>
    </item>
  </channel>
</rss>

