rcp : login failed

[j773303]

A: rcp test.txt B:/tmp
login failed

I have alreay configue .rhosts
of B machine. Does anyone know how to verify it?

[Stefan Farrelly]

A simple test is as user X on server A do;
remsh B -l uptime

and if .rhosts is setup correctly it will return uptime info.

Things to check if it doesnt work;
1. .rhosts on serverB has permissions 400
2. serverA is defined in .rhosts on serverB with full domain name (so that nslookup serverA resolves properly)
3. When you try a remsh or rcp you use the userid on serverB you setup the .rhosts for;
eg. on serverA do> rcp test.txt @:/tmp/test.txt
4. Is the format of your .rhosts file correct ? to test it temporarily change it to;
serverA +
(which allows all users from serverA to login)

[T G Manikandan]

If you are doing rcp using root then your command looks fine.

If you are rcping between normal users then the format should be like

$rcp ruser1@rhost1:path1 ruser2@rhost2:path2

[V. Nyga]

Hi,

from 'man rcp':
The rcp routine is confused by any output generated by commands in a .cshrc file on the remote host.

User is defined at both machines?

Volkmar

[V. V. Ravi Kumar_1]

hi,
check /etc/hosts for proper entries on both the machines.

try giving ip address in place of hostname.

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.

Regards

[j773303]

I have try the suggestion from above, but the rcp still
can't work well, rcp in A machine is still failed, but in B machine is OK, both the setting are the same.
Any way to troubleshoot this?
Is it possible due to the rcp PATCH?

[Steven E. Protter]

The .rhosts files can't be exactly the same.

.rhosts lists who is allowed to log in and from what hostname or ip address.

Lets say we have machA and machB machines

user schmobagel is allowed to use the INSECURE r-protocols.

in the /home/schmobagel/.rhosts file on machA it says:

schmobagel machB

on machB it says

schmobagel machA

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

Check it out..

SEP