<?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 PÄ±x's telnet problem in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/p%C3%A4-x-s-telnet-problem/m-p/891436#M959971</link>
    <description>&lt;P&gt;Ä± didn't connect pÄ±x clÄ±.It always give error about telnet problem.What is the source in this problem.&lt;/P&gt;</description>
    <pubDate>Mon, 11 Mar 2019 11:35:35 GMT</pubDate>
    <dc:creator>dilek.horasan</dc:creator>
    <dc:date>2019-03-11T11:35:35Z</dc:date>
    <item>
      <title>PÄ±x's telnet problem</title>
      <link>https://community.cisco.com/t5/network-security/p%C3%A4-x-s-telnet-problem/m-p/891436#M959971</link>
      <description>&lt;P&gt;Ä± didn't connect pÄ±x clÄ±.It always give error about telnet problem.What is the source in this problem.&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 11:35:35 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/p%C3%A4-x-s-telnet-problem/m-p/891436#M959971</guid>
      <dc:creator>dilek.horasan</dc:creator>
      <dc:date>2019-03-11T11:35:35Z</dc:date>
    </item>
    <item>
      <title>Re: PÄ±x's telnet problem</title>
      <link>https://community.cisco.com/t5/network-security/p%C3%A4-x-s-telnet-problem/m-p/891437#M959972</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Would you please tell us the error log you have? You want to connect to PIX via telnet?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 27 Nov 2007 10:30:26 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/p%C3%A4-x-s-telnet-problem/m-p/891437#M959972</guid>
      <dc:creator>Alan Huseyin Kayahan</dc:creator>
      <dc:date>2007-11-27T10:30:26Z</dc:date>
    </item>
    <item>
      <title>Re: PÄ±x's telnet problem</title>
      <link>https://community.cisco.com/t5/network-security/p%C3%A4-x-s-telnet-problem/m-p/891438#M959973</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;you need to tell the pix which hosts/networks are allowed to telnet to the pix.  for example if you want just your ip address to telnet, and your ip is 192.168.1.100 you issue "telnet 192.168.1.100 255.255.255.255 inside"  If you are running version 7.0+ you also need "management-access inside"&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 27 Nov 2007 19:19:24 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/p%C3%A4-x-s-telnet-problem/m-p/891438#M959973</guid>
      <dc:creator>jserevitch</dc:creator>
      <dc:date>2007-11-27T19:19:24Z</dc:date>
    </item>
    <item>
      <title>Re: PÄ±x's telnet problem</title>
      <link>https://community.cisco.com/t5/network-security/p%C3%A4-x-s-telnet-problem/m-p/891439#M959974</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I would not configure telnet, but ssh for remote access. The above post is also on point. You can do that with ssh.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 29 Nov 2007 01:19:25 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/p%C3%A4-x-s-telnet-problem/m-p/891439#M959974</guid>
      <dc:creator>viper1284</dc:creator>
      <dc:date>2007-11-29T01:19:25Z</dc:date>
    </item>
  </channel>
</rss>

