<?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: RSH problem in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/rsh-problem/m-p/4389144#M41950</link>
    <description>&lt;!--!*#--&gt;&amp;gt; $:&amp;gt; rsh 192.168.25.5&lt;BR /&gt;&lt;BR /&gt;Of course, the first test would be to add a&lt;BR /&gt;remote_command.  For example:&lt;BR /&gt;&lt;BR /&gt;      rsh 192.168.25.5 show default</description>
    <pubDate>Fri, 27 Mar 2009 12:22:24 GMT</pubDate>
    <dc:creator>Steven Schweda</dc:creator>
    <dc:date>2009-03-27T12:22:24Z</dc:date>
    <item>
      <title>RSH problem</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/rsh-problem/m-p/4389138#M41944</link>
      <description>I receive this error when I issue RSH :&lt;BR /&gt;&lt;BR /&gt;$:&amp;gt;  rsh 192.168.25.5&lt;BR /&gt;%RSH-E-SERVNOTAVAIL, Remote service is not currently available&lt;BR /&gt;-SYSTEM-F-REJECT, connect to network object rejected&lt;BR /&gt;&lt;BR /&gt;The service is enabled,nor sure if it is blocked somewhere in the network.Please suggest.&lt;BR /&gt;&lt;BR /&gt;TCPIP&amp;gt; sh serv rsh&lt;BR /&gt;&lt;BR /&gt;Service             Port  Proto    Process          Address            State&lt;BR /&gt;&lt;BR /&gt;RSH                  514  TCP      TCPIP$RSH        0.0.0.0             Enabled&lt;BR /&gt;TCPIP&amp;gt; sh serv rsh/fu&lt;BR /&gt;&lt;BR /&gt;Service: RSH&lt;BR /&gt;                           State:     Enabled&lt;BR /&gt;Port:              514     Protocol:  TCP             Address:  0.0.0.0&lt;BR /&gt;Inactivity:          5     User_name: not defined     Process:  TCPIP$RSH&lt;BR /&gt;Limit:               3     Active:        0           Peak:         0&lt;BR /&gt;&lt;BR /&gt;File:         TCPIP$SYSTEM:TCPIP$RSH_RUN.COM&lt;BR /&gt;Flags:        Case Listen Proxy Rexe IPv6&lt;BR /&gt;&lt;BR /&gt;Socket Opts:  Rcheck Scheck&lt;BR /&gt; Receive:            0     Send:               0&lt;BR /&gt;&lt;BR /&gt;Log Opts:     Acpt Actv Dactv Conn Error Exit Mdfy Rjct TimO Addr&lt;BR /&gt; File:        not defined&lt;BR /&gt;&lt;BR /&gt;Separators:&lt;BR /&gt; Port:   0    User_name: 0    Password:  0    Command:  0&lt;BR /&gt;&lt;BR /&gt;Security&lt;BR /&gt; Reject msg:  not defined&lt;BR /&gt; Accept host: visel.rtco.com&lt;BR /&gt; Accept netw: 0.0.0.0&lt;BR /&gt;TCPIP&amp;gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Thanks&lt;BR /&gt;</description>
      <pubDate>Fri, 27 Mar 2009 08:24:08 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/rsh-problem/m-p/4389138#M41944</guid>
      <dc:creator>Mulder_1</dc:creator>
      <dc:date>2009-03-27T08:24:08Z</dc:date>
    </item>
    <item>
      <title>Re: RSH problem</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/rsh-problem/m-p/4389139#M41945</link>
      <description>Is the TCPIP show service done at the target host 192.168.25.5 ?&lt;BR /&gt;Is the accept host visel.rtco.com the one You trying the rsh command ?&lt;BR /&gt;&lt;BR /&gt;The accept command is blocking all but the specified host.&lt;BR /&gt;</description>
      <pubDate>Fri, 27 Mar 2009 09:06:45 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/rsh-problem/m-p/4389139#M41945</guid>
      <dc:creator>Joseph Huber_1</dc:creator>
      <dc:date>2009-03-27T09:06:45Z</dc:date>
    </item>
    <item>
      <title>Re: RSH problem</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/rsh-problem/m-p/4389140#M41946</link>
      <description>&amp;gt;&amp;gt; The accept command &lt;BR /&gt; meant: the accept host entry ,</description>
      <pubDate>Fri, 27 Mar 2009 10:59:53 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/rsh-problem/m-p/4389140#M41946</guid>
      <dc:creator>Joseph Huber_1</dc:creator>
      <dc:date>2009-03-27T10:59:53Z</dc:date>
    </item>
    <item>
      <title>Re: RSH problem</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/rsh-problem/m-p/4389141#M41947</link>
      <description>The target is having the same info :&lt;BR /&gt;&lt;BR /&gt;TCPIP&amp;gt; sh serv rsh&lt;BR /&gt;&lt;BR /&gt;Service Port Proto Process Address State&lt;BR /&gt;&lt;BR /&gt;RSH 514 TCP TCPIP$RSH 0.0.0.0 Enabled&lt;BR /&gt;TCPIP&amp;gt; sh serv rsh/fu&lt;BR /&gt;&lt;BR /&gt;Service: RSH&lt;BR /&gt;State: Enabled&lt;BR /&gt;Port: 514 Protocol: TCP Address: 0.0.0.0&lt;BR /&gt;Inactivity: 5 User_name: not defined Process: TCPIP$RSH&lt;BR /&gt;Limit: 3 Active: 0 Peak: 0&lt;BR /&gt;&lt;BR /&gt;File: TCPIP$SYSTEM:TCPIP$RSH_RUN.COM&lt;BR /&gt;Flags: Case Listen Proxy Rexe IPv6&lt;BR /&gt;&lt;BR /&gt;Socket Opts: Rcheck Scheck&lt;BR /&gt;Receive: 0 Send: 0&lt;BR /&gt;&lt;BR /&gt;Log Opts: Acpt Actv Dactv Conn Error Exit Mdfy Rjct TimO Addr&lt;BR /&gt;File: not defined&lt;BR /&gt;&lt;BR /&gt;Separators:&lt;BR /&gt;Port: 0 User_name: 0 Password: 0 Command: 0&lt;BR /&gt;&lt;BR /&gt;Security&lt;BR /&gt;Reject msg: not defined&lt;BR /&gt;Accept host: visel.rtco.com&lt;BR /&gt;Accept netw: 0.0.0.0&lt;BR /&gt;TCPIP&amp;gt;&lt;BR /&gt;&lt;BR /&gt;Thanks</description>
      <pubDate>Fri, 27 Mar 2009 11:30:28 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/rsh-problem/m-p/4389141#M41947</guid>
      <dc:creator>Mulder_1</dc:creator>
      <dc:date>2009-03-27T11:30:28Z</dc:date>
    </item>
    <item>
      <title>Re: RSH problem</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/rsh-problem/m-p/4389142#M41948</link>
      <description>Yes, and my question was also:&lt;BR /&gt; is visel.rtco.com the source (requester) of the rsh command ?&lt;BR /&gt;If NOT, then the accept host entry is the reason  why it rejects the connection.</description>
      <pubDate>Fri, 27 Mar 2009 12:14:27 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/rsh-problem/m-p/4389142#M41948</guid>
      <dc:creator>Joseph Huber_1</dc:creator>
      <dc:date>2009-03-27T12:14:27Z</dc:date>
    </item>
    <item>
      <title>Re: RSH problem</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/rsh-problem/m-p/4389143#M41949</link>
      <description>&lt;!--!*#--&gt;&amp;gt; TCPIP&amp;gt; sh serv rsh&lt;BR /&gt;&lt;BR /&gt;What about "rlogin"?  An RSH command with no&lt;BR /&gt;remote_command on the line uses the RLOGIN&lt;BR /&gt;service, not RSH.&lt;BR /&gt;&lt;BR /&gt;alp $ help rsh&lt;BR /&gt;&lt;BR /&gt;RSH&lt;BR /&gt;&lt;BR /&gt;[...]&lt;BR /&gt;     When using the RSH command, consider the following:&lt;BR /&gt;&lt;BR /&gt;     o  If you omit a command for remote execution, RSH initiates a&lt;BR /&gt;        remote login session (see the RLOGIN command).&lt;BR /&gt;[...]&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;I believe that "-SYSTEM-F-REJECT" here is&lt;BR /&gt;equivalent to the UNIX "Connection refused",&lt;BR /&gt;that is, there's no server there.</description>
      <pubDate>Fri, 27 Mar 2009 12:16:29 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/rsh-problem/m-p/4389143#M41949</guid>
      <dc:creator>Steven Schweda</dc:creator>
      <dc:date>2009-03-27T12:16:29Z</dc:date>
    </item>
    <item>
      <title>Re: RSH problem</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/rsh-problem/m-p/4389144#M41950</link>
      <description>&lt;!--!*#--&gt;&amp;gt; $:&amp;gt; rsh 192.168.25.5&lt;BR /&gt;&lt;BR /&gt;Of course, the first test would be to add a&lt;BR /&gt;remote_command.  For example:&lt;BR /&gt;&lt;BR /&gt;      rsh 192.168.25.5 show default</description>
      <pubDate>Fri, 27 Mar 2009 12:22:24 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/rsh-problem/m-p/4389144#M41950</guid>
      <dc:creator>Steven Schweda</dc:creator>
      <dc:date>2009-03-27T12:22:24Z</dc:date>
    </item>
  </channel>
</rss>

