<?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 connection refused message when remotely connecting in Operating System - Tru64 Unix</title>
    <link>https://community.hpe.com/t5/operating-system-tru64-unix/connection-refused-message-when-remotely-connecting/m-p/3528090#M12380</link>
    <description>Hi, I have three Alpha workstations running Tru64 and have a problem connecting to the workstation I have configured as the master. I am getting the connection refused message every time I try to remotely connect from the other 2 workstations to the master through rsh, rlogin, ftp, etc. But when I go from the master to the other 2 worksataions I have no problem. I can ping to the master ok. Does anyone know what could be the problem. This problem has only occured, it was working fine for over a year.</description>
    <pubDate>Tue, 19 Apr 2005 14:07:39 GMT</pubDate>
    <dc:creator>RICHARD DONAGHY</dc:creator>
    <dc:date>2005-04-19T14:07:39Z</dc:date>
    <item>
      <title>connection refused message when remotely connecting</title>
      <link>https://community.hpe.com/t5/operating-system-tru64-unix/connection-refused-message-when-remotely-connecting/m-p/3528090#M12380</link>
      <description>Hi, I have three Alpha workstations running Tru64 and have a problem connecting to the workstation I have configured as the master. I am getting the connection refused message every time I try to remotely connect from the other 2 workstations to the master through rsh, rlogin, ftp, etc. But when I go from the master to the other 2 worksataions I have no problem. I can ping to the master ok. Does anyone know what could be the problem. This problem has only occured, it was working fine for over a year.</description>
      <pubDate>Tue, 19 Apr 2005 14:07:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-tru64-unix/connection-refused-message-when-remotely-connecting/m-p/3528090#M12380</guid>
      <dc:creator>RICHARD DONAGHY</dc:creator>
      <dc:date>2005-04-19T14:07:39Z</dc:date>
    </item>
    <item>
      <title>Re: connection refused message when remotely connecting</title>
      <link>https://community.hpe.com/t5/operating-system-tru64-unix/connection-refused-message-when-remotely-connecting/m-p/3528091#M12381</link>
      <description>The master system is:&lt;BR /&gt;&lt;BR /&gt;- not running the inetd daemon&lt;BR /&gt;&lt;BR /&gt;Examine the output of the "ps -ef" command for the "inetd" process.  If not found, then start inetd by "/sbin/init.d/inetd".  If it starts properly (recheck with the output of the "ps -ef" command), then it may be that the symlink /sbin/rc3.d/S55inetd (that links to /sbin/init.d/inetd) is missing.&lt;BR /&gt;&lt;BR /&gt;- the inetd daemon is not properly configured&lt;BR /&gt;&lt;BR /&gt;Examine the /etc/inetd.conf file on the master and one of the other workstations to check for differences.&lt;BR /&gt;</description>
      <pubDate>Tue, 19 Apr 2005 15:34:05 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-tru64-unix/connection-refused-message-when-remotely-connecting/m-p/3528091#M12381</guid>
      <dc:creator>Stuart Fuller_2</dc:creator>
      <dc:date>2005-04-19T15:34:05Z</dc:date>
    </item>
  </channel>
</rss>

