<?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: Proxy Telnet or Virtul Telnet in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/proxy-telnet-or-virtul-telnet/m-p/271426#M434521</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;yes, we decided on virtual telnet with ACS authentication  and auhtorization.  Essentially, inbound telnet is challenged by PIX.  If successfull, they are passed on to an internal "telnet" server where they authenicate a second time with another set of credentials.  Then they can telnet within the network, cumbersome but they should the VPN anyway.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 26 Apr 2004 14:29:43 GMT</pubDate>
    <dc:creator>spbench</dc:creator>
    <dc:date>2004-04-26T14:29:43Z</dc:date>
    <item>
      <title>Proxy Telnet or Virtul Telnet</title>
      <link>https://community.cisco.com/t5/network-access-control/proxy-telnet-or-virtul-telnet/m-p/271424#M434519</link>
      <description>&lt;P&gt;I have a requirement to allow non-VPN users telnet access to a certain network.  After a little research I am unclear as to the difference between Virtual Telnet vs. Proxy Telnet.  Basically, I want to authenicate telnet comeing in from the internet to access certain IPs (these IPs will change on a per user basis).  Is it possible/feasible to set up TACACS+ or RADIUS with virtual or proxy telnet to allow this?  Any thoughts on which is better?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;TIA&lt;/P&gt;</description>
      <pubDate>Sun, 10 Mar 2019 14:45:36 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/proxy-telnet-or-virtul-telnet/m-p/271424#M434519</guid>
      <dc:creator>spbench</dc:creator>
      <dc:date>2019-03-10T14:45:36Z</dc:date>
    </item>
    <item>
      <title>Re: Proxy Telnet or Virtul Telnet</title>
      <link>https://community.cisco.com/t5/network-access-control/proxy-telnet-or-virtul-telnet/m-p/271425#M434520</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Any update on this ?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 24 Apr 2004 13:40:50 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/proxy-telnet-or-virtul-telnet/m-p/271425#M434520</guid>
      <dc:creator>benhur.p</dc:creator>
      <dc:date>2004-04-24T13:40:50Z</dc:date>
    </item>
    <item>
      <title>Re: Proxy Telnet or Virtul Telnet</title>
      <link>https://community.cisco.com/t5/network-access-control/proxy-telnet-or-virtul-telnet/m-p/271426#M434521</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;yes, we decided on virtual telnet with ACS authentication  and auhtorization.  Essentially, inbound telnet is challenged by PIX.  If successfull, they are passed on to an internal "telnet" server where they authenicate a second time with another set of credentials.  Then they can telnet within the network, cumbersome but they should the VPN anyway.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 26 Apr 2004 14:29:43 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/proxy-telnet-or-virtul-telnet/m-p/271426#M434521</guid>
      <dc:creator>spbench</dc:creator>
      <dc:date>2004-04-26T14:29:43Z</dc:date>
    </item>
  </channel>
</rss>

