0

I have two systems, a Solaris and an Oracle Linux. I can rsh from OL to Solaris but not from Solaris to OL. I can also ssh from both machines.

I was reading this and I tried to create an rsh file in /etc/xinetd.d/ (which was initially empty) but it didn't work.

I also tried to restart xinetd service:

restart xinetd daemon

but I got the following:

Failed to issue method call: Unit xinetd.service failed to load: No such file or directory.

I tried some debugging when trying to connect from a remote system:

truss rsh -l root copernicus

The last seven lines are showing:

setsockopt(4, tcp, TCP_ANONPRIVBIND, 0xF9DACEB4, 4, SOV_DEFAULT) = 0
bind(4, 0xF9DACF20, 32, SOV_SOCKBSD)        = 0
getsockname(4, 0xF9DACF20, 0xF9DACEBC, SOV_DEFAULT) = 0
setsockopt(4, tcp, TCP_ANONPRIVBIND, 0xF9DACEB8, 4, SOV_DEFAULT) = 0
setsockopt(4, SOL_SOCKET, SO_EXCLBIND, 0xF9DACEB8, 4, SOV_DEFAULT) = 0
ioctl(4, FIOSETOWN, 0xF9DACFE8)         = 0
connect(4, 0xF9DAD100, 32, SOV_DEFAULT) (sleeping...)
030
  • 6,085
Michael
  • 121

1 Answers1

1

If you really, really, really must use rsh, which I do not recommend, you will need to install it.

For RHEL7-based systems, do the following:

  1. Install the rsh-server package.

    yum install rsh-server

  2. Restart the rsh daemon (I'm assuming here you don't need rlogin and/or rexec).

    systemctl restart rsh.socket

  3. (Optional) Set the daemon to auto-start.

    systemctl enable rsh.socket

But please, please, please don't use rsh - ssh is far superior.

mjturner
  • 502
  • 3
  • 9