rlogin

[John Goetz]

Trying to rlogin or remsh to another server and its asking for password. The .rhosts file is setup correctly. I can rlogin ok out of the server that I am trying to rlogin into. Not sure what else to look at.

[Dave Hutton]

in your .rhosts do have just the short named used? or long name?

Quite a few times I see when I go from one server to another and have issues with this its because when I do a who -u it shows
host.domain.com where I just have short name in the .rhosts file.

[Mel Burslan]

also make sure your .rhosts has permissions of 400

[Luk Vandenbussche]

Hi,

Try with rlogin ip-adress instead of the name. Just to check that your name resolution works fine

[AwadheshPandey · Accepted solution]

useful link for you, edit ur /etc/host.equiv file.

http://www.informatik.uni-frankfurt.de/doc/man/hpux/rlogin.1.html

Awadhesh

[john kingsley]

If you have more than one network adapter in the box, and the other adapter(s) have differnent hostnames associated with them, make sure the other hostnames are listed in the rhost file.

[Rick Garland]

How is the system name being reported, long name or short name?

You may want to include both in the .rhosts

[Doug O'Leary]

Hey;

From a system that is supposed to be allowed rlogin acccess, telnet to the trusting system, then execute "who -R". Ensure the hostname reported via that command is listed in the ~/.rhosts file.

Now to get on my soap box: You really shouldn't use rlogin/remsh except in very short case by case basis. If you need to have passwordless login, switch to ssh with public key authentication. It's a bit of a learning curve, but two factor authentication will always trump the rather significant security hole that trusted hosts entails.

HTH;

Doug