<?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: Cannot login ACS3.0 at local machine in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/cannot-login-acs3-0-at-local-machine/m-p/137560#M1060965</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;OK, I had to try this, you piqued my curiosity.  Sure enough, if you set both the start and end ports to 2002 you lock yourself out.  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;To get back in, you need to change the registry settings.  Open regedit and find the key:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;HKLM/Software/Cisco/CiscoAAAv3.x/CSAdmin/Config&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Under here there's a Start Port and End Port value, change these to something other than both 2002 (0x7d2).  Stop/start the CSAdmin service via Control Panel and you should be able to get back in.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 11 Feb 2003 01:58:48 GMT</pubDate>
    <dc:creator>gfullage</dc:creator>
    <dc:date>2003-02-11T01:58:48Z</dc:date>
    <item>
      <title>Cannot login ACS3.0 at local machine</title>
      <link>https://community.cisco.com/t5/network-security/cannot-login-acs3-0-at-local-machine/m-p/137558#M1060963</link>
      <description>&lt;P&gt;I cannot login ACS3.0 (both local and remote) after i limit the administrative session use port 2002 only. 'Can not login to CiscoSecure ACS for Windows 2000/NT, all Administration ports are currently in use. ' is the messge shown. Anyone can help on this? Thanks.&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 06:32:54 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/cannot-login-acs3-0-at-local-machine/m-p/137558#M1060963</guid>
      <dc:creator>Ka Ming Jack Fok</dc:creator>
      <dc:date>2020-02-21T06:32:54Z</dc:date>
    </item>
    <item>
      <title>Re: Cannot login ACS3.0 at local machine</title>
      <link>https://community.cisco.com/t5/network-security/cannot-login-acs3-0-at-local-machine/m-p/137559#M1060964</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;ACS listens constantly on port 2002 for new login connections, then after you login, it changes that session to a different port, usually a random one but as you know, you can set it up to change to certain ports.  It still monitors port 2002 for new connections.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What you've done is tell ACS that it can only change to port 2002, but that port is already in use by the ACS admin service as it waits for new logins to come in.  I don't believe there's any way around this, nor am I sure how you can fix it.  I'm not game to try it on mine cause I think you've probably locked yourself out (sorry about that).  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you can get back in, you'll need to set it up to use port 2001 or something like that, something different to 2002 anyway.  Keep in mind also though, that if you make say, the start and end ports 3000 to 3000, you'll only be able to get one admin session at a time going.  When the 2nd session tries to login it'll be redirected to port 3000 but that will be in use by the 1st admin session and you'll get an error.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 11 Feb 2003 01:52:13 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/cannot-login-acs3-0-at-local-machine/m-p/137559#M1060964</guid>
      <dc:creator>gfullage</dc:creator>
      <dc:date>2003-02-11T01:52:13Z</dc:date>
    </item>
    <item>
      <title>Re: Cannot login ACS3.0 at local machine</title>
      <link>https://community.cisco.com/t5/network-security/cannot-login-acs3-0-at-local-machine/m-p/137560#M1060965</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;OK, I had to try this, you piqued my curiosity.  Sure enough, if you set both the start and end ports to 2002 you lock yourself out.  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;To get back in, you need to change the registry settings.  Open regedit and find the key:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;HKLM/Software/Cisco/CiscoAAAv3.x/CSAdmin/Config&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Under here there's a Start Port and End Port value, change these to something other than both 2002 (0x7d2).  Stop/start the CSAdmin service via Control Panel and you should be able to get back in.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 11 Feb 2003 01:58:48 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/cannot-login-acs3-0-at-local-machine/m-p/137560#M1060965</guid>
      <dc:creator>gfullage</dc:creator>
      <dc:date>2003-02-11T01:58:48Z</dc:date>
    </item>
    <item>
      <title>Re: Cannot login ACS3.0 at local machine</title>
      <link>https://community.cisco.com/t5/network-security/cannot-login-acs3-0-at-local-machine/m-p/137561#M1060966</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks your kindly help, it really helps a lot.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 14 Feb 2003 06:47:26 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/cannot-login-acs3-0-at-local-machine/m-p/137561#M1060966</guid>
      <dc:creator>Ka Ming Jack Fok</dc:creator>
      <dc:date>2003-02-14T06:47:26Z</dc:date>
    </item>
  </channel>
</rss>

