On the client side, make sure that the rsh binary has execute permissions. Moreover, if you are not root user, make sure that you have the proper rights on that binary. Check the /etc/hosts file or the DNS configuration to make sure that the server name is properly resolved.
On the server side, make sure that the remote shell service is started. On my system running Mandrake 8.0, rsh is started "on-demand" using xinetd. Therefore, my /etc/xinetd.d/rsh file looks like this :
service shell { disable = no socket_type = stream wait = no user = root log_on_success += USERID log_on_failure += USERID server = /usr/sbin/in.rshd }
You may note the "disable" option that is set to "no". Restart the eXtended inet daemon after any changes in the file :
/etc/rc.d/init.d/xinetd restart
To check if it is running :
netstat -a | grep shell
Check the /etc/hosts file or the DNS configuration to make sure that the client name is properly resolved.
After doing all of these if it still doesn't work, check the /etc/hosts.allow and /etc/hosts.deny file for security aspects. Try with empty file (security disabled).
Hi Kodjo, I have changed rsh file on both system, restart xinetd but no luck. I do not have hosts.allow and hosts.deny file. Name resoultion work through /etc/hosts file. I can ping node from master and vice-versa.
As you may know, the set userID bit "s" makes the program execute as user root, even for non-root users. Programs having this bit set should be considered as security holes, unless they have been tested and tested and tested again.
