<?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: rcp : login failed in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/rcp-login-failed/m-p/2972632#M120717</link>
    <description>&lt;BR /&gt;A simple test is as user X on server A do;&lt;BR /&gt;remsh B -l &lt;USERZ on="" serverb=""&gt; uptime&lt;BR /&gt;&lt;BR /&gt;and if .rhosts is setup correctly it will return uptime info.&lt;BR /&gt;&lt;BR /&gt;Things to check if it doesnt work;&lt;BR /&gt;1. .rhosts on serverB has permissions 400&lt;BR /&gt;2. serverA is defined in .rhosts on serverB with full domain name (so that nslookup serverA resolves properly)&lt;BR /&gt;3. When you try a remsh or rcp you use the userid on serverB you setup the .rhosts for;&lt;BR /&gt;eg. on serverA do&amp;gt; rcp test.txt &lt;USERID&gt;@&lt;SERVERB&gt;:/tmp/test.txt&lt;BR /&gt;4. Is the format of your .rhosts file correct ? to test it temporarily change it to;&lt;BR /&gt;serverA +&lt;BR /&gt;(which allows all users from serverA to login)&lt;BR /&gt;&lt;/SERVERB&gt;&lt;/USERID&gt;&lt;/USERZ&gt;</description>
    <pubDate>Wed, 14 May 2003 06:25:58 GMT</pubDate>
    <dc:creator>Stefan Farrelly</dc:creator>
    <dc:date>2003-05-14T06:25:58Z</dc:date>
    <item>
      <title>rcp : login failed</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/rcp-login-failed/m-p/2972631#M120716</link>
      <description>A: rcp test.txt B:/tmp&lt;BR /&gt;login failed&lt;BR /&gt;&lt;BR /&gt;I have alreay configue .rhosts&lt;BR /&gt;of B machine. Does anyone know how to verify it?</description>
      <pubDate>Wed, 14 May 2003 06:11:18 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/rcp-login-failed/m-p/2972631#M120716</guid>
      <dc:creator>j773303</dc:creator>
      <dc:date>2003-05-14T06:11:18Z</dc:date>
    </item>
    <item>
      <title>Re: rcp : login failed</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/rcp-login-failed/m-p/2972632#M120717</link>
      <description>&lt;BR /&gt;A simple test is as user X on server A do;&lt;BR /&gt;remsh B -l &lt;USERZ on="" serverb=""&gt; uptime&lt;BR /&gt;&lt;BR /&gt;and if .rhosts is setup correctly it will return uptime info.&lt;BR /&gt;&lt;BR /&gt;Things to check if it doesnt work;&lt;BR /&gt;1. .rhosts on serverB has permissions 400&lt;BR /&gt;2. serverA is defined in .rhosts on serverB with full domain name (so that nslookup serverA resolves properly)&lt;BR /&gt;3. When you try a remsh or rcp you use the userid on serverB you setup the .rhosts for;&lt;BR /&gt;eg. on serverA do&amp;gt; rcp test.txt &lt;USERID&gt;@&lt;SERVERB&gt;:/tmp/test.txt&lt;BR /&gt;4. Is the format of your .rhosts file correct ? to test it temporarily change it to;&lt;BR /&gt;serverA +&lt;BR /&gt;(which allows all users from serverA to login)&lt;BR /&gt;&lt;/SERVERB&gt;&lt;/USERID&gt;&lt;/USERZ&gt;</description>
      <pubDate>Wed, 14 May 2003 06:25:58 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/rcp-login-failed/m-p/2972632#M120717</guid>
      <dc:creator>Stefan Farrelly</dc:creator>
      <dc:date>2003-05-14T06:25:58Z</dc:date>
    </item>
    <item>
      <title>Re: rcp : login failed</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/rcp-login-failed/m-p/2972633#M120718</link>
      <description>If you are doing rcp using root then your command looks fine.&lt;BR /&gt;&lt;BR /&gt;If you are rcping between normal users then the format should be like&lt;BR /&gt;&lt;BR /&gt;$rcp ruser1@rhost1:path1 ruser2@rhost2:path2</description>
      <pubDate>Wed, 14 May 2003 06:30:29 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/rcp-login-failed/m-p/2972633#M120718</guid>
      <dc:creator>T G Manikandan</dc:creator>
      <dc:date>2003-05-14T06:30:29Z</dc:date>
    </item>
    <item>
      <title>Re: rcp : login failed</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/rcp-login-failed/m-p/2972634#M120719</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;from 'man rcp':&lt;BR /&gt;The rcp routine is confused by any output generated by commands in a .cshrc file on the remote host.&lt;BR /&gt;&lt;BR /&gt;User is defined at both machines?&lt;BR /&gt;&lt;BR /&gt;Volkmar</description>
      <pubDate>Wed, 14 May 2003 06:40:12 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/rcp-login-failed/m-p/2972634#M120719</guid>
      <dc:creator>V. Nyga</dc:creator>
      <dc:date>2003-05-14T06:40:12Z</dc:date>
    </item>
    <item>
      <title>Re: rcp : login failed</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/rcp-login-failed/m-p/2972635#M120720</link>
      <description>hi,&lt;BR /&gt;check /etc/hosts for proper entries on both the machines.&lt;BR /&gt;&lt;BR /&gt;try giving ip address in place of hostname. &lt;BR /&gt;&lt;BR /&gt;if both machines are trusted, the users must be added through SAM, for whom u are doing rcp. adding a user from the command line is giving problem in case of rlogin and rcp in a trusted system.&lt;BR /&gt;&lt;BR /&gt;Regards</description>
      <pubDate>Wed, 14 May 2003 06:45:40 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/rcp-login-failed/m-p/2972635#M120720</guid>
      <dc:creator>V. V. Ravi Kumar_1</dc:creator>
      <dc:date>2003-05-14T06:45:40Z</dc:date>
    </item>
    <item>
      <title>Re: rcp : login failed</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/rcp-login-failed/m-p/2972636#M120721</link>
      <description>I have try the suggestion from above, but the rcp still&lt;BR /&gt;can't work well, rcp in A machine is still failed, but in B machine is OK, both the setting are the same. &lt;BR /&gt;Any way to troubleshoot this?&lt;BR /&gt;Is it possible due to the rcp PATCH?</description>
      <pubDate>Wed, 14 May 2003 23:54:44 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/rcp-login-failed/m-p/2972636#M120721</guid>
      <dc:creator>j773303</dc:creator>
      <dc:date>2003-05-14T23:54:44Z</dc:date>
    </item>
    <item>
      <title>Re: rcp : login failed</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/rcp-login-failed/m-p/2972637#M120722</link>
      <description>The .rhosts files can't be exactly the same.&lt;BR /&gt;&lt;BR /&gt;.rhosts lists who is allowed to log in and from what hostname or ip address.&lt;BR /&gt;&lt;BR /&gt;Lets say we have machA and machB machines&lt;BR /&gt;&lt;BR /&gt;user schmobagel is allowed to use the INSECURE r-protocols.&lt;BR /&gt;&lt;BR /&gt;in the /home/schmobagel/.rhosts file on machA it says:&lt;BR /&gt;&lt;BR /&gt;schmobagel machB&lt;BR /&gt;&lt;BR /&gt;on machB it says&lt;BR /&gt;&lt;BR /&gt;schmobagel machA&lt;BR /&gt;&lt;BR /&gt;This access can be blocked by /etc/hosts.equiv entries which invalidate the .rhosts file, or blocking configuration in the file /var/adm/inetd.sec&lt;BR /&gt;&lt;BR /&gt;Check it out..&lt;BR /&gt;&lt;BR /&gt;SEP</description>
      <pubDate>Thu, 15 May 2003 00:07:01 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/rcp-login-failed/m-p/2972637#M120722</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2003-05-15T00:07:01Z</dc:date>
    </item>
  </channel>
</rss>

