<?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 Remote Agent Authentication with AD in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/remote-agent-authentication-with-ad/m-p/1132599#M379596</link>
    <description>&lt;P&gt;Hi..&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1. I'm deploying 802.1x on Wired environment and we are using ACS 4.2 with remote agent.&lt;/P&gt;&lt;P&gt;2. For redundancy purpose, i install 2 ACS SE and 2 Remote Agent.&lt;/P&gt;&lt;P&gt;3. The 1st Agent works perfectly with the AD. It can translate both machine and user authentication request.&lt;/P&gt;&lt;P&gt;4. The 2nd Remote agent can only with user authentication request. For machine authentication, it will try to pass the long "host/B4XRQ1S.XXX.COM" to the AD.&lt;/P&gt;&lt;P&gt;5. This is what the 2nd RA pass to the AD:- &lt;/P&gt;&lt;P&gt;Could not find machine host/B4XRQ1S.XXX.COM [2413,-2147016672]&lt;/P&gt;&lt;P&gt;host/B4XRQ1S.XXX.COM is not a valid machine name&lt;/P&gt;&lt;P&gt;6. With the 1st Remote Agent, it work perfectly. It will only pass the machine name :-&lt;/P&gt;&lt;P&gt;Attempting Windows authentication for user B4XRQ1S$&lt;/P&gt;&lt;P&gt;Windows authentication SUCCESSFUL (by XXXDC04)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Anyone has any idea what is happening. I checked and found both server has same configuration&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When 1 point the ACS SE to the 1st RA, it works perfectly. But when i point to the 2nd RA, it cannot authenticate the machine.&lt;/P&gt;</description>
    <pubDate>Sun, 10 Mar 2019 23:15:52 GMT</pubDate>
    <dc:creator>muhammadsafwan</dc:creator>
    <dc:date>2019-03-10T23:15:52Z</dc:date>
    <item>
      <title>Remote Agent Authentication with AD</title>
      <link>https://community.cisco.com/t5/network-access-control/remote-agent-authentication-with-ad/m-p/1132599#M379596</link>
      <description>&lt;P&gt;Hi..&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1. I'm deploying 802.1x on Wired environment and we are using ACS 4.2 with remote agent.&lt;/P&gt;&lt;P&gt;2. For redundancy purpose, i install 2 ACS SE and 2 Remote Agent.&lt;/P&gt;&lt;P&gt;3. The 1st Agent works perfectly with the AD. It can translate both machine and user authentication request.&lt;/P&gt;&lt;P&gt;4. The 2nd Remote agent can only with user authentication request. For machine authentication, it will try to pass the long "host/B4XRQ1S.XXX.COM" to the AD.&lt;/P&gt;&lt;P&gt;5. This is what the 2nd RA pass to the AD:- &lt;/P&gt;&lt;P&gt;Could not find machine host/B4XRQ1S.XXX.COM [2413,-2147016672]&lt;/P&gt;&lt;P&gt;host/B4XRQ1S.XXX.COM is not a valid machine name&lt;/P&gt;&lt;P&gt;6. With the 1st Remote Agent, it work perfectly. It will only pass the machine name :-&lt;/P&gt;&lt;P&gt;Attempting Windows authentication for user B4XRQ1S$&lt;/P&gt;&lt;P&gt;Windows authentication SUCCESSFUL (by XXXDC04)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Anyone has any idea what is happening. I checked and found both server has same configuration&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When 1 point the ACS SE to the 1st RA, it works perfectly. But when i point to the 2nd RA, it cannot authenticate the machine.&lt;/P&gt;</description>
      <pubDate>Sun, 10 Mar 2019 23:15:52 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/remote-agent-authentication-with-ad/m-p/1132599#M379596</guid>
      <dc:creator>muhammadsafwan</dc:creator>
      <dc:date>2019-03-10T23:15:52Z</dc:date>
    </item>
    <item>
      <title>Re: Remote Agent Authentication with AD</title>
      <link>https://community.cisco.com/t5/network-access-control/remote-agent-authentication-with-ad/m-p/1132600#M379604</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;There can be a number of things causing this, but most probably some issue with the second RA and the DC it's installed on. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I advise you to open a TAC case on this issue.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 05 Jan 2009 20:16:44 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/remote-agent-authentication-with-ad/m-p/1132600#M379604</guid>
      <dc:creator>jhillend</dc:creator>
      <dc:date>2009-01-05T20:16:44Z</dc:date>
    </item>
  </channel>
</rss>

