<?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: Authentication with Windows 2003 server in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/authentication-with-windows-2003-server/m-p/612479#M421406</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I think it might have to be installed on the domain controller but I'm not sure about that. I've never seen a best practice on the subject, but I can't think of any reasons why it would be better to have it on a separate server. If you have a secondary domain controller, you can install it there as well with duplicate configuration. You can then have backup in case your primary fails.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 08 Mar 2007 13:47:53 GMT</pubDate>
    <dc:creator>acomiskey</dc:creator>
    <dc:date>2007-03-08T13:47:53Z</dc:date>
    <item>
      <title>Authentication with Windows 2003 server</title>
      <link>https://community.cisco.com/t5/network-access-control/authentication-with-windows-2003-server/m-p/612476#M421403</link>
      <description>&lt;P&gt;Hi there,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am looking for achieve this task. I would like to know How I could authenticate users accesing by my wireless network? I mean in windows 2003 server. They must type their username and password. I want to restricted users which are not on the list to access by my wireless network. I know that in windows 2000 I could use radius server. Could I use it here?. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Also, I guess that I have to allow these "new users" in AD.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am looking forward to read helpfull information here and of course I will give it a rate (points)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any ideas are welcome.&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Wladimir&lt;/P&gt;</description>
      <pubDate>Sun, 10 Mar 2019 22:01:44 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/authentication-with-windows-2003-server/m-p/612476#M421403</guid>
      <dc:creator>wladimirpausin</dc:creator>
      <dc:date>2019-03-10T22:01:44Z</dc:date>
    </item>
    <item>
      <title>Re: Authentication with Windows 2003 server</title>
      <link>https://community.cisco.com/t5/network-access-control/authentication-with-windows-2003-server/m-p/612477#M421404</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Same thing for 2003, it is called IAS (Internet Authentication Service).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="http://www.microsoft.com/technet/network/ias/default.mspx" target="_blank"&gt;http://www.microsoft.com/technet/network/ias/default.mspx&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Basically you will set up IAS with a RADIUS Client which would be your wireless access point(s). Then you will set up a remote access policy which will define how connections are authorized or rejected (windows groups, protocols etc.). Don't forget to register IAS with active directory.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 07 Mar 2007 20:06:31 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/authentication-with-windows-2003-server/m-p/612477#M421404</guid>
      <dc:creator>acomiskey</dc:creator>
      <dc:date>2007-03-07T20:06:31Z</dc:date>
    </item>
    <item>
      <title>Re: Authentication with Windows 2003 server</title>
      <link>https://community.cisco.com/t5/network-access-control/authentication-with-windows-2003-server/m-p/612478#M421405</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;ok thanks for the answer. The link is very useful.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Now, I don't know which is the best practice to install IAS server. Do you think it could be install in Domain Controler or another server?. What do you recomend me?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Wladimir&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 08 Mar 2007 09:28:26 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/authentication-with-windows-2003-server/m-p/612478#M421405</guid>
      <dc:creator>wladimirpausin</dc:creator>
      <dc:date>2007-03-08T09:28:26Z</dc:date>
    </item>
    <item>
      <title>Re: Authentication with Windows 2003 server</title>
      <link>https://community.cisco.com/t5/network-access-control/authentication-with-windows-2003-server/m-p/612479#M421406</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I think it might have to be installed on the domain controller but I'm not sure about that. I've never seen a best practice on the subject, but I can't think of any reasons why it would be better to have it on a separate server. If you have a secondary domain controller, you can install it there as well with duplicate configuration. You can then have backup in case your primary fails.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 08 Mar 2007 13:47:53 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/authentication-with-windows-2003-server/m-p/612479#M421406</guid>
      <dc:creator>acomiskey</dc:creator>
      <dc:date>2007-03-08T13:47:53Z</dc:date>
    </item>
  </channel>
</rss>

