<?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: Tacacs issue in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/tacacs-issue/m-p/969299#M384947</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Glad to know that.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 16 Jul 2008 11:57:41 GMT</pubDate>
    <dc:creator>Jagdeep Gambhir</dc:creator>
    <dc:date>2008-07-16T11:57:41Z</dc:date>
    <item>
      <title>Tacacs issue</title>
      <link>https://community.cisco.com/t5/network-access-control/tacacs-issue/m-p/969296#M384944</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Can someone explain the issue below to me. &lt;/P&gt;&lt;P&gt;*Jul 15 16:40:16.677: TPLUS(0000023C)/0/WRITE: wrote entire 21 bytes request&lt;/P&gt;&lt;P&gt;*Jul 15 16:40:16.781: TPLUS(0000023C)/0/READ: socket event 1&lt;/P&gt;&lt;P&gt;*Jul 15 16:40:16.781: TPLUS(0000023C)/0/READ: read entire 12 header bytes (expect 6 bytes data)&lt;/P&gt;&lt;P&gt;*Jul 15 16:40:16.781: TPLUS(0000023C)/0/READ: socket event 1&lt;/P&gt;&lt;P&gt;*Jul 15 16:40:16.781: TPLUS(0000023C)/0/READ: read entire 18 bytes response&lt;/P&gt;&lt;P&gt;*Jul 15 16:40:16.781: T+: Version 192 (0xC0), type 1, seq 4, encryption 1&lt;/P&gt;&lt;P&gt;*Jul 15 16:40:16.781: T+: session_id 1607034059 (0x5FC964CB), dlen 6 (0x6)&lt;/P&gt;&lt;P&gt;*Jul 15 16:40:16.781: T+: AUTHEN/REPLY status:2 flags:0x0 msg_len:0, data_len:0&lt;/P&gt;&lt;P&gt;*Jul 15 16:40:16.781: T+: msg:&lt;/P&gt;&lt;P&gt;*Jul 15 16:40:16.781: T+: data:&lt;/P&gt;&lt;P&gt;*Jul 15 16:40:16.781: T+: End Packet&lt;/P&gt;&lt;P&gt;*Jul 15 16:40:16.785: TPLUS(0000023C)/0/63E21E64: Processing the reply packet&lt;/P&gt;&lt;P&gt;*Jul 15 16:40:16.785: TPLUS: Received authen response status FAIL (3)&lt;/P&gt;&lt;P&gt;*Jul 15 16:40:17.681: ISAKMP/xauth: reply attribute XAUTH_STATUS_V2 unexpected.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;it is the last line that seems to be catching me out. The user account is setup in my unix TACACS server the same as the rest. ( new to this unix based tacacs stuff).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hpe you can help&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Stephen&lt;/P&gt;</description>
      <pubDate>Sun, 10 Mar 2019 22:58:32 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/tacacs-issue/m-p/969296#M384944</guid>
      <dc:creator>stephen.stack</dc:creator>
      <dc:date>2019-03-10T22:58:32Z</dc:date>
    </item>
    <item>
      <title>Re: Tacacs issue</title>
      <link>https://community.cisco.com/t5/network-access-control/tacacs-issue/m-p/969297#M384945</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Stephen,&lt;/P&gt;&lt;P&gt;Can you test it with local authentication and see if that works.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Also let me know the IOS ver running on the router.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;~JG&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 15 Jul 2008 18:41:00 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/tacacs-issue/m-p/969297#M384945</guid>
      <dc:creator>Jagdeep Gambhir</dc:creator>
      <dc:date>2008-07-15T18:41:00Z</dc:date>
    </item>
    <item>
      <title>Re: Tacacs issue</title>
      <link>https://community.cisco.com/t5/network-access-control/tacacs-issue/m-p/969298#M384946</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi JG,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for quick response. It appears that i did not restart the tacacs process in the unix box properly, hence the change did not take effect. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It is all working now, thanks to my unix guru here.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks again&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Stephen&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 16 Jul 2008 07:45:06 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/tacacs-issue/m-p/969298#M384946</guid>
      <dc:creator>stephen.stack</dc:creator>
      <dc:date>2008-07-16T07:45:06Z</dc:date>
    </item>
    <item>
      <title>Re: Tacacs issue</title>
      <link>https://community.cisco.com/t5/network-access-control/tacacs-issue/m-p/969299#M384947</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Glad to know that.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 16 Jul 2008 11:57:41 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/tacacs-issue/m-p/969299#M384947</guid>
      <dc:creator>Jagdeep Gambhir</dc:creator>
      <dc:date>2008-07-16T11:57:41Z</dc:date>
    </item>
  </channel>
</rss>

