<?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: TELNET &amp;amp; TCPIP$TELNETSYM in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/telnet-amp-tcpip-telnetsym/m-p/4459772#M58438</link>
    <description>hi,&lt;BR /&gt;&lt;BR /&gt; AFAIK it is completely independent with it's own startup/shutdown procedures and logicals.&lt;BR /&gt;&lt;BR /&gt;hth</description>
    <pubDate>Tue, 14 Jul 2009 22:31:58 GMT</pubDate>
    <dc:creator>marsh_1</dc:creator>
    <dc:date>2009-07-14T22:31:58Z</dc:date>
    <item>
      <title>TELNET &amp; TCPIP$TELNETSYM</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/telnet-amp-tcpip-telnetsym/m-p/4459771#M58437</link>
      <description>I am switching all of interactive access from telnet to SSH; however, we have print queues that are based on the telnet symbiont.  I'd like to disable telnet completely to force everyone to utilize SSH.  Is TCPIP$TELNETSYM self contained or does it need telnet enabled to function.  Thanks,  Rene</description>
      <pubDate>Tue, 14 Jul 2009 21:01:36 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/telnet-amp-tcpip-telnetsym/m-p/4459771#M58437</guid>
      <dc:creator>Rene Rodrigue</dc:creator>
      <dc:date>2009-07-14T21:01:36Z</dc:date>
    </item>
    <item>
      <title>Re: TELNET &amp; TCPIP$TELNETSYM</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/telnet-amp-tcpip-telnetsym/m-p/4459772#M58438</link>
      <description>hi,&lt;BR /&gt;&lt;BR /&gt; AFAIK it is completely independent with it's own startup/shutdown procedures and logicals.&lt;BR /&gt;&lt;BR /&gt;hth</description>
      <pubDate>Tue, 14 Jul 2009 22:31:58 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/telnet-amp-tcpip-telnetsym/m-p/4459772#M58438</guid>
      <dc:creator>marsh_1</dc:creator>
      <dc:date>2009-07-14T22:31:58Z</dc:date>
    </item>
    <item>
      <title>Re: TELNET &amp; TCPIP$TELNETSYM</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/telnet-amp-tcpip-telnetsym/m-p/4459773#M58439</link>
      <description>It's self contained and NOT part of telnet access per se.  The telnet symbiont has startup and shutdown procedures all of its own, although it mainly relies upon these to install images (I think).&lt;BR /&gt;It uses a reverse telnet connection to the printer but this is so that it can just squirt (technical term!) the data down the link, not so that it can accept incoming data, other than printer status information etc.&lt;BR /&gt;There are other methods of printing (e.g. LPR/LPD) but this depends upon what your printer will actually accept - not all printers and print servers accept all protocols and not all firewalls are set to pass everything either.&lt;BR /&gt;&lt;BR /&gt;Steve</description>
      <pubDate>Wed, 15 Jul 2009 02:06:25 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/telnet-amp-tcpip-telnetsym/m-p/4459773#M58439</guid>
      <dc:creator>Steve Reece_3</dc:creator>
      <dc:date>2009-07-15T02:06:25Z</dc:date>
    </item>
    <item>
      <title>Re: TELNET &amp; TCPIP$TELNETSYM</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/telnet-amp-tcpip-telnetsym/m-p/4459774#M58440</link>
      <description>Thanks!!! Rene</description>
      <pubDate>Wed, 15 Jul 2009 12:08:48 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/telnet-amp-tcpip-telnetsym/m-p/4459774#M58440</guid>
      <dc:creator>Rene Rodrigue</dc:creator>
      <dc:date>2009-07-15T12:08:48Z</dc:date>
    </item>
  </channel>
</rss>

