please find below the details of my system.and outputs , these are the few things which i had done , but still , so please have look and waiting for some advice which can help me out from this problem.

rsh package installed
rsh-0.17-25.1
rsh-server-0.17-25.1

chkconfig --list rsh
rsh on

auth sufficient pam_rhosts_auth.so

append /etc/securetty with "rsh" in bottom of the file.
############
[root@veritas ~]# rlogin veritas2
veritas2: host unknown
Trying krb4 rlogin...
veritas2: host unknown
trying normal rlogin (/usr/bin/rlogin)
veritas2: Unknown host
##############
[root@veritas ~]# /usr/bin/rsh 192.168.20.129
192.168.20.129: No route to host
[root@veritas ~]# ping 192.168.20.129
PING 192.168.20.129 (192.168.20.129) 56(84) bytes of data.
64 bytes from 192.168.20.129: icmp_seq=0 ttl=64 time=0.630 ms
64 bytes from 192.168.20.129: icmp_seq=1 ttl=64 time=1.02 ms

--- 192.168.20.129 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1001ms
rtt min/avg/max/mdev = 0.630/0.825/1.020/0.195 ms, pipe 2
[root@veritas ~]# ssh root@192.168.20.129
root@192.168.20.129's password:
##########
$PATH
-bash: /usr/kerberos/sbin:/usr/kerberos/bin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/X11R6/bin:/root/bin:

Apart from usage of any r.* services being frowned upon this isn't a security issue so I've moved your thread to the Newbie forum.

... the "veritas2" host name does not resolve to an IP address, locally (/etc/hosts, host-based name server) or remotely (host-based forwarding name server, any remote name servers).


... but you can throw ICMP messages at it to show it's alive.


... and you can SSH to it.


... 'tcptraceroute 192.168.20.129 514' would have been more convenient because it shows the route that actual traffic takes between hosts, if the remote port is open and if you have ensured it is open if it's denied in /etc/hosts.deny and or the firewall.

maybe devs cut out support for rlogin because it is ancient and insecure. have you considered ssh with keys ?

also, at least with ssh, root login is disabled by default.

cat /etc/hosts output
192.168.20.128 veritas.test.com
192.168.20.129 veritas2.test.com

no entry is there in /etc/hosts.deny

For Veritas Cluster Is is mandatory to have rlogin enabled or it can also work with passwordless ssh ????

Great. You managed to check 2 out of 4 things.

To follow up on unSpawn's post: run iptables -L on the machine and see if rsh/rlogin is being blocked by the firewall.

I'd be shocked if Veritas did not work over passwordless SSH, but I've never used it so I don't really know.

not sure what a veritas cluster is (is it like beowolf ?) but if it is linux it probably has sshd turned on by default (which has nothing to do with rlogin).

what i know of rlogin was that it was a protocol used for logging in remotely to systems. then it was replaced by telnet which added the security of needing a password to login to remote systems. and then ssh replaced that by encrypting the channel and optionally replacing passwords with keys.

There's a good article here about why not to use rsh+friends, and how to replace them with the ssh equivalents http://www.informit.com/articles/art...p=169465&rll=1